Managing external identities to enable secure access for partners, customers, and other non-employees
If another administrator is available, have a Privileged Authentication Administrator reset this administrator account’s MFA registration and issue a new Temporary Access Pass; if this is the tenant’s only accessible administrator, escalate the External ID tenant-access deadlock to Microsoft Support rather than disabling Security Defaults.^1^
Recover the administrator account
Private browsing does not change the account’s server-side authentication registration state, so use an administrator-assisted reset:
- From another administrator account, open Microsoft Entra admin center → Entra ID → Users → affected administrator → Authentication methods.
- Select Revoke sessions, then Require re-register multifactor authentication.
- Remove the affected work account from Microsoft Authenticator before starting registration again. This reset-and-remove sequence is the accepted remediation for an Authenticator registration loop.^2^
- Create a new Temporary Access Pass for the affected account. A TAP is a time-limited bootstrap or recovery credential for registering another authentication method.^3^
- Sign in with the TAP and register Authenticator again. Confirm that the final redirect reaches the requested resource rather than returning to the registration wizard.
Because the affected identity is itself an administrator, use Privileged Authentication Administrator for the recovery administrator; External ID User Flow Administrator is scoped to user-flow management and should not be elevated merely to repair authentication methods.
Keep Security Defaults enabled. It requires users to register MFA, and Security Defaults registration uses Microsoft Authenticator notifications; repeatedly disabling and re-enabling it is unnecessary here.^4^
If no second administrator can reach the tenant, the External ID–specific reports describe this registration state as having no reliable in-tenant self-service recovery path. Open a Microsoft Support case for tenant-access recovery, providing:
- Tenant ID and affected user object ID
- UTC timestamp and correlation/request ID from the failure
-
AADSTS530035 / BlockedBySecurityDefaults - Confirmation that TAP registration completed but the registration interrupt repeats
- Confirmation that this is an External ID external tenant
Support escalation is for restoring tenant access; it should not be described as asking Support to directly modify an organization-managed user’s MFA method.
Disable public sign-up without changing the role
Once Graph authentication works, retain External ID User Flow Administrator. It is the least-privileged supported role for updating an External ID self-service sign-up flow, together with delegated EventListener.ReadWrite.All.^5^
- In Entra ID → External Identities → User flows, select the flow.
- Under Use → Applications, copy the associated Application (client) ID.
- Obtain a delegated Microsoft Graph token containing
EventListener.ReadWrite.All. Granting tenant-wide consent to that scope may require an administrator with permission to consent; the user-flow role and OAuth consent are separate authorization checks. - List the flows and identify the one associated with that application:
GET https://graph.microsoft.com/v1.0/identity/authenticationEventsFlows
Authorization: Bearer {token}
Listing requires EventListener.Read.All or EventListener.ReadWrite.All, and External ID User Flow Administrator is a supported least-privileged directory role.^6^
- Update that flow to prohibit sign-up:
PATCH https://graph.microsoft.com/v1.0/identity/authenticationEventsFlows/{flow-id}
Authorization: Bearer {token}
Content-Type: application/json
{
"@odata.type": "#microsoft.graph.externalUsersSelfServiceSignUpEventsFlow",
"isSignUpAllowed": false
}
Microsoft’s External ID procedure requires retrieving the flow ID through Graph and updating that flow’s sign-up setting.^7^
Do not delete the flow or unlink the application merely to stop registration. Unlinking disables the entire customized authentication experience for that application, while deleting the flow also unlinks every associated application.^8^
If the loop remains after a clean reset
Inspect Entra ID → Users → Sign-in logs → affected event → Authentication Details. It shows the applied policy, authentication method sequence, success or failure, and whether the event remained at “registration prompted.”^9^
The least-privileged role for reading sign-in logs is Reports Reader; assign it only if the recovery administrator does not already have log access.^10^
References
- External tenant: “Keep your account secure” returns BadRequest for an internal admin account — how should admins register MFA? - Microsoft Q&A
- I have authentication issue with Microsoft Authenticator (authenticator asking for authentication). - Microsoft Q&A
- Configure Temporary Access Pass to register passwordless authentication methods
- Security defaults in Microsoft Entra ID
- Update authenticationEventsFlow
- List authenticationEventsFlows
- Disable sign-up in a sign-up and sign-in user flow
- Delete authenticationConditionApplication (from a user flow)
- Use the sign-in logs to review Microsoft Entra multifactor authentication events
- Least privileged roles by task in Microsoft Entra ID