Guests with Global Admin can not login to Azure Portal with Security Defaults Enabled, endless loop "Help us protect your account" after MFA completed

askpatrickw 26 Reputation points
2022-08-02T00:19:44.287+00:00

Guests with Global Admin can not login to Azure Portal tenants with Security Defaults Enabled. We see an endless loop "Help us protect your account" after MFA is completed via Microsoft Authenticator app successfully.

Guests who are not Global Admin can login to Azure Portal.

Since the MFA has completed, this "privileged access" should be allowed shouldn't it?

Microsoft Entra ID
Microsoft Entra ID
A Microsoft Entra identity service that provides identity management and access control capabilities. Replaces Azure Active Directory.
19,467 questions
{count} vote

Accepted answer
  1. jtcr 76 Reputation points
    2022-08-05T19:02:20.08+00:00

    @askpatrickw @Sandeep G-MSFT @Till Rebenich

    I am also experiencing this issue across a couple tenants. Not specifically for guests, but for tenants that do have security defaults enabled.

    I believe this is due to the change notated here: https://learn.microsoft.com/en-us/azure/active-directory/fundamentals/concept-fundamentals-security-defaults#authentication-methods

    228677-image.png

    The only thing that has worked has been to manually add the cell phone number as an Authentication Method. Either through Azure AD or within the particular users Security Info at My Sign-Ins.

    I hope this helps. I tried to force re-registration and all that, but wasn't able to resolve it without the manual add.

    Hopefully Microsoft can implement a fix soon.


1 additional answer

Sort by: Most helpful
  1. Sandeep G-MSFT 14,486 Reputation points Microsoft Employee
    2022-08-11T06:29:58.877+00:00

    @askpatrickw

    We have got a solution for this now.
    A code bug in the recent deployment at backend caused communication errors between two services that caused guest Global Admins to fail during additional auth method registration.

    Impacted people were all global admin users who din't have phone method MFA registered. Our product team tried to add a additional requirement in security defaults, which requires atleast one phone method to be registered as MFA for all global admins.

    There was some issue that happen during this code change at backend.
    Currently our PG team has rolled back the changes and everything is back to normal for now.

    Please confirm if your issue is also resolved.

    Please "Accept the answer" if the information helped you. This will help us and others in the community as well.