The sign-in errors indicate issues with the Microsoft Entra tenant (directory) behind the account, not with the browser or device.
Key points from the errors described:
-
interaction_required and Application requested a user session which does not exist indicate the portal cannot get valid tokens for the current tenant/session.
- "Selected user account does not exist in tenant 'Microsoft Services' and cannot access the application" means the account is being evaluated against a tenant where it is not a member or guest.
From similar Azure sign-in issues in the context, there are two main patterns and resolutions:
- Tenant is blocked or inaccessible
When a tenant is blocked due to inactivity, sign-in can fail with interaction_required and AADSTS errors. In that case, the tenant admin must have the tenant reactivated by Microsoft support within the allowed window. The documented guidance is:
- Administrators can request reactivation of an inactive tenant by contacting Microsoft using the global support phone numbers.
- Avoid opening multiple support requests for the same issue while one is in progress.
- As a workaround to reach the correct tenant, sign in directly with the tenant identifier in the portal URL, for example:
-
https://portal.azure.com/<TenantId>
- or
https://portal.azure.com/<yourTenantName>.onmicrosoft.com
If the tenant is already in a blocked/inactive state, it must be reactivated by Microsoft before normal portal use (including app registration) will work.
- Account vs. tenant mismatch
The error stating the selected user account does not exist in the Microsoft Services tenant means the sign-in is being evaluated against a tenant where the account is not present. To proceed, either:
- Use the correct tenant where the account is actually a member (for example, by using the tenant-specific portal URL as above), or
- Have the account added as an external (guest) user in the target tenant if that tenant is where the app must be registered.
If the account is only a personal Microsoft account and there is no active Azure tenant associated with it, or the tenant is blocked, then to obtain Client ID, Tenant ID, and Client Secret for a plugin, one of the following is required:
- Reactivate the existing tenant via Microsoft support (if it is blocked/inactive and within the reactivation window), then register the app.
- Or create/associate a new tenant that is active, then sign in to that tenant in the Azure portal and register the app there.
In all cases, the underlying requirement is an active Microsoft Entra tenant where the account is a member or guest; without that, app registration for Azure-based authentication cannot proceed.
References: