![]() ![]() Clients that currently support Hybrid Modern Auth are listed below. Verify that all of your email clients and apps support Modern Authentication.Verify that Hybrid Modern Authentication is enabled and successfully working in your Exchange Hybrid environment.So what do you need to do to configure this new feature? ![]() Windows authentication (NTLM and Kerberos).The following legacy authentication methods have historically been used to access Exchange servers, and it’s the removal of these were are interested in for the purposes of this feature and post. We’ve had to support multiple authentication methods over this time, to keep in sync with clients and to allow simple migration. What are ‘legacy’ authentication methods?Įxchange Server has been around for 23 years, so we’ve seen a lot of change over that time. This ensures only those clients that support Hybrid Modern Authentication can connect to Exchange Server. If your organization has no legacy email clients or doesn’t want to allow legacy email clients, you can use these new Authentication Policies in your Exchange Hybrid environment to disable legacy authentication requests. This feature is very similar to the functionality offered in Office 365 for Disabling Basic authentication.Īs you probably know, legacy authentication methods are less secure, are vulnerable to interception and are susceptible to brute-force and password spray attacks. This provides an important step down the path of removing legacy authentication mechanisms from Exchange Hybrid deployments. We are happy to announce our work to allow you to disable legacy authentication is available to you with the second cumulative update (CU2) for Exchange 2019. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |