Forum Discussion

Susmita1240's avatar
Susmita1240
Copper Contributor
Jun 14, 2023

AADSTS900971 : No Reply Address Provided (ADAL and MSAL issue)

We are integrating Zenople and MS Teams, we are receiving an error when attempting to create an auth token. We have correctly setup redirectURLs and seems like this is a Teams issue. Also we have enabled the flagging for admin attention. Below is the entire message:

 

Sign in

Sorry, but we’re having trouble signing you in.

AADSTS900971: No reply address provided.

 

Troubleshooting details

If you contact your administrator, send this info to them.

Copy info to clipboard

Request Id: 5a7ba8eb-fdea-4ec1-8f5e-614cc6c40600

Correlation Id: ee4c0a7e-568c-4163-a39b-a5db949eeedb

Timestamp: 2023-06-14T04:34:28Z

Message: AADSTS900971: No reply address provided.

Flag sign-in errors for review: Enable flagging

If you plan on getting help for this problem, enable flagging and try to reproduce the error within 20 minutes. Flagged events make diagnostics available and are raised to admin attention.

 

Any suggestions would be helpful

  • Susmita1240 

    To fix this issue, you can try the following steps:

    1. Verify that the redirect URI configured in AAD for your application matches the one configured in Auth0.
    2. Make sure the "Reply URLs" field in the Azure portal for the app registration in AAD has the same redirect URI you configured in the Auth0's application.
    3. Verify that the application's client ID and tenant ID in your code match the values in AAD.
    4. Check if the API permissions are granted to the application.
    5. If everything seems to be in place and the problem persist, try to remove the application from AAD and add it again.

    If the problem still persists after trying these steps, you can check the AAD logs to see if there is any additional information about the error.

    • Nivedipa-MSFT's avatar
      Nivedipa-MSFT
      Icon for Microsoft rankMicrosoft
      Susmita1240 - Could you please confirm whether your issue has been resolved or if you are still experiencing the same problem?

Resources