Managing external identities to enable secure access for partners, customers, and other non-employees
The live.com account is a personal Microsoft account (MSA), not an organizational Microsoft Entra ID account. The error indicates that this MSA does not exist as a user in the Microsoft Services tenant, so it cannot access the Azure Portal application for that tenant.
From the provided context, MSAs can be used as external identities via OpenID Connect in an external tenant, but they are not native organizational accounts. For tenant administration and Azure Portal access, an organizational account in the tenant is required.
Based on the context:
- A Microsoft account (live.com) can be configured as an external identity provider for customer/external tenants using OpenID Connect. This allows users to sign in to applications with their MSA, but this is explicitly for external customer scenarios and not for B2B guest users or core tenant administration.
- The note in the MSA federation article states that this feature is available only for users who sign up with a Microsoft account (MSA) and is not available for B2B guest users invited to the tenant.
Given that, the implications for the scenario are:
- A live.com MSA cannot function as a native organizational admin account for the Microsoft Services tenant.
- To administer the tenant and access the Azure Portal for that tenant, a native Entra ID organizational account in that tenant is required.
- Adding the MSA as a guest/external user does not convert it into a full organizational admin identity for tenant-level management.
Therefore, to resolve the mismatch:
- Create or use a native organizational account in the Microsoft Services tenant (for example, a user with an @<tenantname>.onmicrosoft.com or verified custom domain) and assign it the Global Administrator role.
- Use that organizational account to sign in to the Azure Portal for the Microsoft Services tenant and manage subscriptions and services.
- The live.com account can be used as an external identity for customer-facing apps if configured via OpenID Connect, but not as the primary tenant admin identity.
This aligns with the documented pattern where MSAs are used via OIDC as external identities in customer tenants, while tenant administration is performed by organizational accounts in Entra ID.
References: