Managing personal Outlook.com account settings, security, and privacy
The behavior is caused by how Microsoft identity and authentication are configured for the email address being used, not by the Outlook.com mailbox itself.
When signing in to Azure or other Microsoft services, the Microsoft Identity Platform determines whether the sign-in should be treated as:
- A personal Microsoft account (Outlook.com, Hotmail, etc.), or
- A work/school (organizational) account managed by Microsoft Entra ID (formerly Azure AD).
If the company has set up federated sign-in or single sign-on (SSO) for that email domain, sign-in requests for that address can be redirected to the organization’s identity provider and its Authenticator/MFA policies, even if the same address is also used as a personal Outlook.com account.
Removing the account from the Authenticator app on the device does not change how the identity platform routes the sign-in. The routing is based on how the domain and account are configured in Microsoft Entra ID and in the Microsoft identity platform, not on the local Authenticator configuration.
To proceed with Azure app registration using a personal account, ensure that the sign-in explicitly uses a Microsoft personal account that is not associated with the organization’s federated domain. If the same email address is used both as a personal Microsoft account and as an organizational account, the organizational configuration and SSO can still force the sign-in through the company’s Authenticator and policies.
If the goal is to use a purely personal identity for Azure and Outlook OAuth, create or use a Microsoft personal account that is not tied to the company’s federated domain and sign in with that account when accessing Azure.
References: