Processes in Microsoft 365 for setting up Office apps, redeeming product keys, and activating licenses.
Follow these steps to troubleshoot the school account sign-in issue and the glitching sign-in page:
- Verify which identity has access
- If the same email address exists as both a personal Microsoft account and a school (work or school) account, selecting the wrong identity can cause “we can’t find your account” or looping/glitching sign-in.
- Fully sign out of all Microsoft sessions, then sign in again and explicitly choose the school/work account when prompted.
- Fully sign out and clear cached sign-in
- Close all browser windows (including any not using Microsoft 365).
- Open a private/incognito window.
- Go to
https://aka.ms/vssignout(Azure DevOps sign-out flow is a known pattern for clearing identities) to ensure complete sign-out. - After sign-out completes, close the browser, reopen it, and try signing in again with the school account, choosing the work/school identity when prompted.
- Check account validity with the school
- If the sign-in address truly “can’t be found,” the school account might be disabled, deleted, or not yet provisioned.
- Contact the school’s IT or help desk to confirm:
- The account is active.
- The correct username format (for example, including the right domain such as
@school.edu). - Any multifactor authentication (MFA) requirements.
- Try a different browser or profile
- Use another browser or a fresh profile to rule out corrupted cookies or cached credentials:
- In Microsoft Edge, go to
edge://settings/profiles, create a new profile, and sign in there. - If the new profile works, the previous profile likely had conflicting or corrupted credentials.
- In Microsoft Edge, go to
- Clear cookies and cached credentials (if still failing)
- In Edge:
edge://settings/privacy→ Clear browsing data → select Cookies and other site data and Cached images and files → Time range All time → Clear now. - Then try signing in again.
- If multiple attempts lock or block sign-in
- Repeated failed attempts can trigger Microsoft Entra multifactor authentication protections.
- If sign-in is blocked after many attempts, wait and try again later or use another MFA method if configured.
- If suspicious activity is suspected or the block persists, contact the school IT admin and ask them to check Microsoft Entra sign-in logs and MFA configuration.
If none of these steps resolve the issue, the school’s IT administrator must review the account status and sign-in logs, as misconfigured MFA, disabled accounts, or tenant policies can only be fixed by them.
References: