AADSTS5000611 Error: Fix No Reply Address Registered

To fix “No reply address is registered for the application,” register the callback required by the sign-in flow in the correct Microsoft Entra ID app registration. First verify the error code: that message is associated with AADSTS500113, so do not assume AADSTS5000611 is an interchangeable code. The steps below help you identify the application, correct its redirect configuration, and test sign-in.

Use the full error message to choose the right starting point:

Symptom Likely Cause Fix
AADSTS500113: “No reply address is registered for the application” The application used for sign-in has no suitable registered reply address. Add the application’s intended callback to its redirect configuration.
AADSTS50011: The reply address does not match The requested callback differs from the registered addresses. Compare the actual request with the registration and correct the difference.
AADSTS900971: “No reply address provided” The sign-in flow has not supplied a usable reply address. Check both the outgoing authentication request and the application’s redirect configuration.
A redirect URI is already registered, but the error continues You may be inspecting a different application, tenant, platform, or environment. Identify the app by the client ID in the failing request before changing anything.

What the “No Reply Address” Error Means

A reply address, also called a redirect URI or callback URL, is where Microsoft Entra ID sends the browser after processing an authentication request. Depending on the flow, the response can contain an authorization code or another authentication result.

Entra checks that destination against the application’s registered configuration. This prevents an application’s sign-in response from being redirected to an unintended destination.

The callback is not necessarily the application’s home page. It may be a dedicated route handled by authentication middleware, a service-managed endpoint, or a native application callback. It is also unrelated to an email message’s Reply-To address.

The missing reply address problem commonly appears after an app registration is created without an interactive sign-in configuration, or when deployment settings point to a different registration than expected.

If your error screen actually shows AADSTS5000611 with different wording, preserve that complete message. Do not change reply addresses solely because a search result pairs that code with this problem.

How to Fix the Missing Reply Address

For a missing reply address in an OAuth or OpenID Connect sign-in flow, correct the redirect configuration in the application’s Microsoft Entra app registration. You need permission to edit that registration; if another organization owns the application, its administrator or vendor must make the change.

Step 1: Identify the Application Making the Request

  1. Start sign-in from the application that fails, rather than from a bookmarked Microsoft login page.
  2. Save the complete error text and its diagnostic details.
  3. Identify the application’s client ID. It may appear in the error details, the application’s authentication configuration, or the outgoing authorization request.
  4. Identify the tenant or authority the application is using.

For a browser-based application, you can inspect the authorization request with the browser’s network tools. Look for the client_id and redirect_uri parameters. Decode URL-encoded parameter values before comparing them with the registration.

If redirect_uri is absent, note that explicitly. Registering a URL and making the application send the intended callback are separate parts of the configuration.

Do not share an unredacted network capture publicly. It may contain cookies, authorization codes, or other sensitive authentication data.

Step 2: Locate the Correct App Registration

A registered callback only helps when it belongs to the client ID actually used by the sign-in request.

  1. Open the Microsoft Entra administration interface and select the directory associated with the application.
  2. Find the application registration by its Application (client) ID.
  3. Confirm that this ID matches the failing request, not merely an application with a similar display name.
  4. Open the registration’s authentication settings and inspect its configured platforms and redirect URIs.

Do not substitute the application’s object ID for its client ID. Also distinguish the app registration from an enterprise application entry: for these OAuth/OpenID Connect flows, the redirect configuration belongs to the application registration.

If an organization owns the application and you cannot edit its registration, stop here and contact the owner. Creating an unrelated registration with the same display name will not repair the existing application.

Step 3: Determine the Intended Callback and Platform

  1. Find the callback configured in the application’s authentication library, middleware, or service integration.
  2. Compare it with the redirect_uri sent during sign-in.
  3. Select the platform configuration appropriate to how the application authenticates.
  4. Resolve any disagreement between the intended deployment address and the outgoing request before registering the URL.

A server-side web application, browser-based single-page application, and native desktop application do not necessarily use the same platform configuration. Choose the one required by the application’s authentication library, not whichever option accepts the URL.

For web callbacks, inspect the scheme, hostname, port, path, path capitalization, and trailing slash. Redirect URI paths are case-sensitive, and seemingly minor differences can matter. Use the URI produced by the intended authentication configuration rather than manually constructing a plausible address.

For local development, use the callback supported by the development app and its SDK. Do not copy a production web callback into a native-client configuration simply to remove the error.

Step 4: Correct and Save the Configuration

  1. Add the intended redirect URI to the appropriate platform configuration, or correct an existing entry that is wrong.
  2. Leave unrelated, valid callbacks in place unless you are deliberately retiring them.
  3. Save the registration.
  4. If you changed application-side authentication settings, apply those changes to the running deployment.

Only register destinations belonging to the intended application or its documented authentication service. Do not add an arbitrary address from an error screen without confirming that it is legitimate.

If the application sends no callback, correct its authentication configuration so it supplies the redirect URI required by its flow. Adding a portal entry alone is not a dependable fix for an incomplete authorization request.

If the callback contains an internal hostname or the wrong scheme behind a reverse proxy, correct the application’s external URL or trusted proxy configuration. Registering an unreachable internal URL may move the failure to the next stage instead of fixing sign-in.

Do not enable unrelated authentication flows, grant extra API permissions, or generate a new client secret just to address a missing reply URL.

Step 5: Start a New Sign-In and Test the Application

  1. Return to the application and begin a new sign-in attempt.
  2. Do not reuse the old authorization URL from the failed browser tab.
  3. Complete authentication and confirm that the browser returns to the application.
  4. Perform the operation that originally required sign-in.

For example, a mail integration should complete its intended mailbox operation, not merely display a successful Microsoft login screen.

If a new error appears, preserve its exact wording. A callback that now reaches the app but produces a routing, token-exchange, consent, or permissions error requires a different repair.

App-Specific Reply Address Fixes

Correct the redirect URI on the app registration used by the affected UiPath, Static Web Apps, or Bot Framework authentication flow, then restart sign-in.

UiPath Microsoft 365 Activities

For UiPath Microsoft 365 Activities, a “No reply address provided” failure can require adding or correcting the Azure application’s Redirect URI for the activity’s authentication scenario.

Identify the client ID configured in the UiPath connection or activity, then update that registration with the callback required by the selected authentication mode. Do not assume a redirect used by another UiPath connection is suitable.

Save the registration, restart authentication from the UiPath workflow, and rerun the failing activity. Confirm that the activity completes its Microsoft 365 operation.

Azure Static Web Apps

For Azure Static Web Apps custom Microsoft Entra authentication, openIdIssuer commonly takes the form https://login.microsoftonline.com/TENANT_ID/v2.0. Replace TENANT_ID with the intended tenant ID, and confirm the tenant and issuer in the Static Web App authentication configuration. The issuer identifies the identity provider; it is not the application’s callback.

If clientIdSettingName is set to AZURE_CLIENT_ID, the deployed application setting named AZURE_CLIENT_ID must contain the intended application’s client ID. Likewise, if clientSecretSettingName is set to AZURE_CLIENT_SECRET, the setting named AZURE_CLIENT_SECRET must contain that application’s client secret.

Those fields reference setting names; they do not contain the credentials themselves. A correctly configured issuer does not prove that the deployed app is using the registration you edited.

Inspect the callback generated by the deployed Static Web App’s authentication flow and register the callback required by that configuration. Apply any application-setting changes, deploy the updated configuration if necessary, then start a new sign-in and verify that an authenticated route loads.

Bot Framework

For a Bot Framework sample using the shared token service, a common reply URL is https://token.botframework.com/.auth/web/redirect. Add it to the Microsoft Entra app registration used by that sample’s authentication connection.

This is not a universal callback for every bot deployment. Confirm the exact redirect URI required by the app or service that initiates sign-in, particularly if the deployment uses a different environment or authentication arrangement.

Save the registration, restart the bot’s authentication flow, and verify that the bot receives a successful sign-in result, not just that the Microsoft login page completes.

How to Confirm the Fix and Prevent Recurrence

A successful repair means the authentication response reaches its intended handler and the application establishes a usable session.

Check that:

  • The callback is handled by the application rather than returning a missing-route or server error.
  • The application recognizes the signed-in user.
  • The original protected operation succeeds.
  • A newly started session works without depending on a previously authenticated browser tab.

If Microsoft sign-in succeeds but the callback returns an application error, inspect the application logs. Authentication middleware, session handling, and token exchange can fail after the reply-address check has passed.

To prevent recurrence, document each environment’s tenant, client ID, authentication mode, and intended callback together. Keep nonsecret authentication configuration under version control, and review it whenever a hostname, deployment environment, or sign-in library changes. Store credentials separately from that configuration.

If the failure remains unresolved, send the application owner the full error message, timestamp, correlation or request ID, and the relevant client ID and callback. Share those details through an appropriate support channel without including client secrets, tokens, or cookies.

Frequently Asked Questions

Why Does Outlook Show “No Reply Address Is Registered”?

The application initiating Microsoft sign-in can have an incorrect reply-address configuration even when the mailbox itself is working. If the error appears in an Outlook add-in, automation tool, or custom mail client, identify that integration rather than changing the mailbox’s Reply-To address. If ordinary Outlook sign-in fails and you do not manage the application, give your Microsoft 365 administrator the complete error details.

Does IMAP Authentication Need a Reply Address?

IMAP itself does not use a browser reply address; an OAuth flow used to obtain its access token may require one. An interactive browser sign-in needs the callback expected by that client, while a client-credentials flow does not use a browser callback. Diagnose how the application acquires its token before changing IMAP or mailbox settings.

How Do I Fix This With Connect-PnPOnline?

For interactive Connect-PnPOnline authentication, the application identified by the client ID must be configured for the sign-in flow and callback that PnP PowerShell uses. Confirm that the command targets your intended registration and that its native-client authentication configuration matches the installed PnP version’s requirements. Save any corrections, start a new connection attempt, and verify access with the intended SharePoint operation.

How Do I Fix This in Business Central?

For a custom Business Central integration, correct the callback on the app registration used by that integration’s interactive sign-in flow. Do not assume that the Business Central home page is the callback; use the endpoint required by the integration. Save the change and retry authentication from the integration, then test its intended operation. If the failure occurs in standard Business Central sign-in rather than an integration you control, send the complete error to the tenant administrator or service provider instead of creating a replacement app registration.