With reference to the Microsoft-confirmed identity.7 incident. I am seeing a similar issue. The key evidence is:
- Original SWA and an independent Standard replacement both failed at /.auth/login/aad/callback.
- They used different regions, hostnames, Entra registrations and credentials.
- A clean Free-tier app with no SchoolFlow code also failed during built-in authentication.
- All three resources were routed through identity.7.azurestaticapps.net.
- The application never loaded, so the failure occurred before our roles source or application authorization.
Can you confirm the incident and reroute the affected SWA resources to a healthy identity backend?
With reference to the Microsoft-confirmed identity.7 incident. I am seeing a similar issue. The key evidence is:
Can you confirm the incident and reroute the affected SWA resources to a healthy identity backend?