Hi Stephen Todd
Typically, accounts provisioned through a non-profit organization are Azure Active Directory (AAD) accounts, which differ slightly from personal Microsoft accounts. While both can access Microsoft services, certain portals or apps may specifically require a personal Microsoft account rather than an organizational one.
To fix this, please ensure that the users are signing in with the organizational credentials tied to your non-profit tenant (usually in the format ****@yourorg.onmicrosoft.com or ****@yourdomain.org). If they attempt to use those credentials in a context that requires a personal Microsoft account, the system may not recognize them.
If your users need access to services that only accept personal Microsoft accounts, one option is to create linked personal accounts and then assign the necessary licenses or permissions through your admin center. Alternatively, you can verify that the licenses (such as Microsoft 365 Nonprofit offers) are correctly assigned to each user in the Microsoft 365 Admin Portal.
I also recommend checking whether the accounts have been fully synchronized and activated. Sometimes, a delay in directory sync or incomplete setup can cause recognition issues. Running a quick check in Azure AD to confirm the accounts’ status should help.
If the issue persists, please share the specific service or portal where the recognition problem occurs, so I can provide more targeted guidance.
I hope this explanation helps clarify the distinction and gives you a path forward. If you find this answer helpful, please hit “Accept Answer” it helps us track resolutions and ensures you get the support you need.