tpsetr.blogg.se

Microsoft had actually switched new tenants back then to its current security defaults.Īt present, there are "more than 30 million organizations" that use Microsoft's Azure AD security defaults, according to Alex Weinert, director of identity security at Microsoft, per the announcement. The coming security defaults will just be presented to organizations that used Azure AD before Oct.

This process will happen via the Microsoft Authenticator app. When the change starts happening for Azure AD tenancies, end users will have 14 days to register to use MFA. IT pros with global administrator privileges will be notified of the change beforehand via e-mail.

Microsoft is planning to kick off the process of turning on Azure AD baseline security for organizations not currently using those protections starting next month. Microsoft estimates that 99.9 percent of hacked accounts typically have lacked MFA. Basic authentication is subject to phishing and "password spray" attacks (the guessing of commonly used passwords). MFA is a secondary means of verifying user identities besides the basic user name-plus-password approach. On the latter front, Microsoft is planning to turn on security defaults for organizations that are using the Azure AD service but not using good security practices, such as multifactor authentication (MFA).

Also, Microsoft is planning to compel the activation of security baseline protections for organizations using the Azure AD service but not currently using the recommended protections. Microsoft is previewing the ability to allow IT pros to remove inactive user accounts for organizations that use the Azure AD identity and access management service. Microsoft announced a couple of Azure Active Directory security enhancements this week.