AADSTS500113: No reply address is registered for the application
The app registration has no redirect URI for the platform being used, so Entra ID has nowhere to send the response.
Seen on:
Azure
Meaning
Each platform (Web, SPA, Mobile/desktop) has its own redirect URI list. New registrations without any redirect URI, or using the SPA flow with only Web URIs, cause this.
Common causes
- No redirect URI configured
- Redirect URI added under the wrong platform
- App still using a deleted URI
⚡ Quick fix
- Add the redirect URI under the correct platform in Authentication
- Match the redirect URI used by your code exactly
Detailed fix by platform
Azure CLI
az ad app update --id <app-id> --web-redirect-uris https://app.example.com/signin-oidc
How to diagnose
- Platforms — Authentication blade entries
- Code — redirect_uri sent in the request
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
- AADSTS50020 AADSTS50020: User account from identity provider does not exist in tenant and cannot access the application
- AADSTS50034 AADSTS50034: The user account does not exist in the directory
- AADSTS50053 AADSTS50053: Your account is locked (Smart Lockout) / sign-in blocked due to suspicious activity
Most viewed in Azure
- AADSTS50076 Azure AD (Entra ID): AADSTS50076 / AADSTS50079 — multi-factor authentication required
- AuthorizationPermissionMismatch Azure Storage: AuthorizationPermissionMismatch (403) — This request is not authorized to perform this operation using this permission
- App Service Application Error Azure App Service: ":( Application Error" / container didn’t respond to HTTP pings
Other ways to find it
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
Was this page helpful?
Report a correction or suggest an improvement
Last updated 7 Oct 2026