Those who use remote PowerShell to connect to Exchange Online might consider switching to PowerShell within the Azure Cloud Shell. This can be a good choice for organizations that still use Exchange ActiveSync-based clients. In the meantime, they recommend using Outlook Mobile clients to connect with Exchange Online. They are working on improving OAuth 2.0 support for POP and IMAP, as well as background application support for Remote PowerShell MFA module. Microsoft admits that this will be a change that users will need to adapt to. Tips for moving beyond Basic Authentication smoothly (Although one might argue that “on-premises” is itself something that we should phase out.) It also does not affect SMTP AUTH for now, Microsoft will continue to support Basic Authentication for it in Exchange Online. Basic Auth Will Still Work in Some ScenariosĬompanies should note that this change only applies to Exchange Online–not on-premises versions of Exchange Server. With the recent announcement, Microsoft will start shifting this change from a recommendation to mandatory procedure.
When these factors are biometric, accounts are much more difficult to attack. Modern also means multi-factor: it requires two pieces of evidence to prove a user’s identity. Microsoft is committed to moving beyond this Basic Authentication to Modern Authentication, which uses OAuth 2.0 tokens and the Active Directory Authentication Library. Attackers can easily target accounts by applying guessable passwords across an organization, and computers can generate password guesses very quickly. The trouble is, this method is too basic for today’s cyberspace. Basic Authentication is another term for the usernames and passwords that we’re so used to typing in. The tech industry has already started talking about moving beyond passwords to increase security through better credential methods.
0 kommentar(er)
