Oauth2 /common endpoint You can't sign in here with a personal account. Use your work or school account instead

No. An unverified publisher is not the cause of that specific sign-in error.

That error usually indicates one of these conditions from the supported account and endpoint configuration:

1. The app is using the wrong authority endpoint for the account type.
   • For apps that support both work or school accounts and personal Microsoft accounts, the sign-in URL must use: https://login.microsoftonline.com/common
   • For multitenant work or school accounts only, use: https://login.microsoftonline.com/organizations
   • For personal Microsoft accounts only, use: https://login.microsoftonline.com/consumers
2. The app or downstream service does not actually support personal Microsoft accounts in that flow.
   • Some account types are not supported in certain authentication flows.
   • Personal Microsoft accounts also cannot be used in some scenarios and services even if the app registration is configured for both account types.

Based on the configuration shown:

• signInAudience = AzureADandPersonalMicrosoftAccount
• requestedAccessTokenVersion = 2
• /common/oauth2/v2.0/authorize

those settings match the documented requirement for an app that accepts both work/school and personal Microsoft accounts.

So the next checks are:

1. Confirm the actual authority used at runtime is /common
   • Verify the application is not overriding the authority elsewhere in code or configuration with a tenant-specific endpoint such as /{tenantId}.
   • If a tenant-specific endpoint is used, personal accounts and users from other organizations can fail with this exact class of sign-in problem.
2. Confirm the sign-in page supports Microsoft accounts
   • If the username hint says Email, phone, or Skype, that sign-in page supports Microsoft accounts.
   • If it does not, the flow is likely targeting a workforce-only experience.
3. Check whether the target service behind the token supports personal Microsoft accounts
   • A documented example is Azure DevOps: /common with personal Microsoft accounts is not supported for that scenario, even when the app registration allows both account types.
   • In that case, /consumers may authenticate the user, but the resulting tokens are not usable for that service.
4. If the app is intended to allow external personal users into an organization-scoped app, consider guest access
   • Personal Microsoft accounts can be invited as guest users into Microsoft Entra organizations.
   • If the app is effectively tenant-scoped, guest access may be required instead of direct personal-account sign-in.

About publisher verification:

• The context only supports that verified publisher status affects consent for newly registered multitenant apps.
• It does not indicate that lack of publisher verification causes the error message: You can't sign in here with a personal account. Use your work or school account instead.

• Error AADSTS50020 - User account from identity provider does not exist in tenant
• Sign-in options for Microsoft accounts in Microsoft Entra ID
• Supported account types
• Integration with OAuth2 / Entra ID for authorization with Microsoft APIs - Microsoft Q&A
• What's the difference between a Microsoft account and a work or school account?