Not able to configure the post-authentication in Azure Static Web Apps

Question

Not able to configure the post-authentication in Azure Static Web Apps

Manuel 0

I have a single-tenant authentication setup with my company (via Microsoft Entra ID). The login prompt appears correctly, but I cannot go past the authentication screen.

For context: I have an Azure Static Web App and a single-tenant registered app. I followed the instructions to get the AZURE_CLIENT_ID and AZURE_CLIENT_SECRET_APP_SETTING_NAME from the value that appears only once after creation. I set the redirect URI to:

https://

Manuel 0

Just as a note, the JSONs I wrote are just a small sub-section of the whole. The holw JSON includes this part too:

  "navigationFallback": {
    "rewrite": "/index.html"
  },
  "routes": [
    {
      "route": "/*",
      "allowedRoles": ["authenticated"]
    }
  ],
  "responseOverrides": {
    "401": {
      "statusCode": 302,
      "redirect": "/.auth/login/aad"
    }
  },

Carolyne 1,151 Reputation points Microsoft Employee

2026-01-28T20:47:36.8666667+00:00

Some few things to consider:
-Redirect URI mismatch: Ensure the Entra ID app uses the exact Static Web Apps callback URL (/.auth/login/aad/callback) for the correct domain (including custom domains), otherwise authentication loops at the login screen.
-Auth config alignment: Verify staticwebapp.config.json matches single‑tenant settings (correct clientId, openIdIssuer, and allowedRoles: ["authenticated"]), and avoid mixing built‑in providers with custom auth.
-Route rules/fallbacks: Confirm your navigationFallback and responseOverrides don’t block post‑auth routing (e.g., 401 → 302 redirect) before the auth provider completes.

Your answer

Manuel 0 Reputation points

2025-11-28T17:59:55.0633333+00:00

Just as a note, the JSONs I wrote are just a small sub-section of the whole. The holw JSON includes this part too:

"navigationFallback": { "rewrite": "/index.html" }, "routes": [ { "route": "/*", "allowedRoles": ["authenticated"] } ], "responseOverrides": { "401": { "statusCode": 302, "redirect": "/.auth/login/aad" } },
Carolyne 1,151 Reputation points Microsoft Employee

2026-01-28T20:47:36.8666667+00:00

Some few things to consider:
-Redirect URI mismatch: Ensure the Entra ID app uses the exact Static Web Apps callback URL (/.auth/login/aad/callback) for the correct domain (including custom domains), otherwise authentication loops at the login screen.
-Auth config alignment: Verify staticwebapp.config.json matches single‑tenant settings (correct clientId, openIdIssuer, and allowedRoles: ["authenticated"]), and avoid mixing built‑in providers with custom auth.
-Route rules/fallbacks: Confirm your navigationFallback and responseOverrides don’t block post‑auth routing (e.g., 401 → 302 redirect) before the auth provider completes.