AADSTS50011: The redirect URI error

(0) Share

Report

Posted on by PA-17061302-0

Dear Team,

Is it possible to use the same static redirect URL for a custom connector across multiple tenants, where the connector is created in one tenant and the solution is imported into another tenant?

Could you please guide.

Thanks and Regards

FathimaMary

Categories:

Building Power Apps

Connector development

Error handling

I have the same question (0)

All responses (3)

Answers (0)

Sort by

Suggested answer

Sunil Kumar Pashikanti 2,195 Moderator on at

Like (0)

Report
Copy link

Link copied!
Hi @PA-17061302-0,

This is expected behavior when moving custom connectors across tenants.

The redirect URI generated by Power Automate is environment-specific, so when you import the solution into another tenant, a new redirect URI is created. If your Azure app registration still has the old one, you’ll get the AADSTS50011 error.

Fix:

Open the custom connector in the target environment and copy the new redirect URI

Go to Azure Portal → App registrations → Authentication

Add the new redirect URI

If you are using a multi-tenant app registration, you don’t need a new app each time. You can simply keep adding the redirect URIs for each environment (up to the allowed limit).

In short, the URI is not truly reusable across tenants, but you can handle it by updating your app registration per environment.

✅ If this answer helped resolve your issue, please mark it as Accepted so it can help others with the same problem.
👍 Feel free to Like the post if you found it useful.

Sunil Kumar Pashikanti, Moderator
Blog: https://sunilpashikanti.com/posts/

Was this reply helpful? Yes No
Suggested answer

DP_Prabh 363 on at

Like (1)

Report
Copy link

Link copied!

Hi @PA-17061302-0,

To fix this, please follow the following steps:

1. Copy the Application ID from the error message. This identifies the app registered in Microsoft Entra ID.
2. Sign in to the Azure portal using an account with permissions to update app registrations.
3. Navigate to Microsoft Entra ID and select App registrations.
4. Locate the app registration using the Application ID and open its details page.
5. Select Authentication from the menu.
6. In the Platform configurations section, click Add URI.
7. Add the redirect URI specified in the error message to the list of redirect URIs.
8. Save the changes and wait 3–5 minutes for them to take effect.
9. Retry the login request. If the issue persists, clear your browser's password cache or use InPrivate browsing.
10. If the redirect URI in the application code is incorrect, update it to match the one configured in the Azure portal.

Reference: Error AADSTS50011 the redirect URI does not match the redirect URIs configured for the application | Microsoft Learn

I hope this works for you!

✅ If this helped, please mark it as the Accepted Solution. 👍 A Like is appreciated and helps others find the answer more easily!

Was this reply helpful? Yes No
Suggested answer

11manish 3,038 on at

Like (0)

Report
Copy link

Link copied!

Yes, you can use the same static redirect URI across multiple tenants, and this is the standard pattern for Power Platform custom connectors.

The key requirement is that the underlying OAuth application supports the target tenants (typically by being configured as a multi-tenant Entra

ID application) and that each target tenant grants the necessary consent and creates its own connection after solution import.

Was this reply helpful? Yes No