![]() ![]() We continue to invest in Modern Authentication capabilities and will continue rolling out OAuth support for POP, IMAP, SMTP AUTH and Remote PowerShell. If you are unable to do so, you can work with the customer’s administrators, who will have to make a security decision to downgrade their organization’s security stance, to explicitly enable access to your application. The best way to avoid such failures in your application is to adopt Modern Authentication. ![]() This means that applications that are using Basic Authentication to connect to Exchange Online might face authentication failures when adopted by a customer who is new to Exchange Online or has not used Basic Authentication applications before. Starting in October 2020 we will also start to disable Basic Authentication in tenants that have no recorded usage. In the meantime, we will continue to disable Basic Authentication for newly created tenants by default. In response to the COVID-19 crisis and knowing that priorities have changed for many of our customers we have decided to postpone disabling Basic Authentication in Exchange Online for those customers still actively using it until the second half of 2021. We will provide a more precise date when we have a better understanding of the impact of the situation. This means that existing applications that are using Basic Authentication to connect to Exchange Online using one or more of the above API’s/protocols will continue to work for existing customers with active usage and developers now have additional time to migrate such apps to use Modern Authentication. ![]() Last year we announced end of support for Basic Authentication for Exchange Web Services (EWS), Exchange Active Sync (EAS), Post Office Protocol (POP), Internet Message Access Protocol (IMAP), and Remote PowerShell (RPS) in Exchange Online. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |