cancel
Showing results for 
Search instead for 
Did you mean: 
Data Engineering
cancel
Showing results for 
Search instead for 
Did you mean: 

Redirect error in access to web app in Azure Databricks with private front endpoint

FerArribas
Contributor

I have created a workspace with private endpoint in Azure following this guide:

https://learn.microsoft.com/en-us/azure/databricks/administration-guide/cloud-configurations/azure/p...

Once I have created the private link of type browser_authentication and I try to log in to the Web UI and the redirect fails:

AADSTS50011: The redirect URI 'https://centralus-c2.pl-auth.privatelink.azuredatabricks.net/login.html' specified in the request does not match the redirect URIs configured for the application '2ff814a6-3304-4ab8-85cb-cd0e6f879c1d'. Make sure the redirect URI sent in the request matches one added to your application in the Azure portal. Navigate to https://aka.ms/redirectUriMismatchError to learn more about how to fix this.

That redirect url doesn't seem to be allowed in the business application (2ff814a6-3304-4ab8-85cb-cd0e6f879c1d) in Azure AD...

Thanks,

1 ACCEPTED SOLUTION

Accepted Solutions

FerArribas
Contributor

Hi,

We have solved the problem by setting up CNAME type records in our resolver DNS architecture.

Thanks!

View solution in original post

5 REPLIES 5

Debayan
Esteemed Contributor III
Esteemed Contributor III

Hi @Fernando Arribas Jara​ , could you please refer to https://learn.microsoft.com/en-us/troubleshoot/azure/active-directory/error-code-aadsts50011-redirec... which talks about the same error.

Kaniz
Community Manager
Community Manager

Hi @Fernando Arribas Jara​​, We haven’t heard from you since the last response from @Debayan Mukherjee​, and I was checking back to see if you have a resolution yet.

If you have any solution, please share it with the community as it can be helpful to others. Otherwise, we will respond with more details and try to help.

Also, Please don't forget to click on the "Select As Best" button whenever the information provided helps resolve your question.

Anonymous
Not applicable

Hi @Fernando Arribas Jara​ 

Hope all is well!

Just wanted to check in if you were able to resolve your issue and would you be happy to share the solution or mark an answer as best? Else please let us know if you need more help. 

We'd love to hear from you.

Thanks!

FerArribas
Contributor

Hi,

We have solved the problem by setting up CNAME type records in our resolver DNS architecture.

Thanks!

Kaniz
Community Manager
Community Manager

Great!

Thanks for the update.

Welcome to Databricks Community: Lets learn, network and celebrate together

Join our fast-growing data practitioner and expert community of 80K+ members, ready to discover, help and collaborate together while making meaningful connections. 

Click here to register and join today! 

Engage in exciting technical discussions, join a group with your peers and meet our Featured Members.