Access issue to an Azure SQL Managed Instance Public Endpoint

Get Help
,
1

We have whitelisted all of the US IP Addresses from the Auth0 documentation on our SQL Managed Instance Conditional Access Policy. This has worked fine in the first Auth0 tenant that we setup connection to our Custom Database(our dev tenant). But now I’m trying to setup the connection and scripts in our Staging and Prod Auth0 tenants and am unable to hit the same Azure SQL Managed Instance public endpoint that works fine in the Dev one, from the Staging and Prod ones. The only difference I see is in the Auth0 tehants, dev is in US-4 and Staging and Prod are in US-5. But like I said, we whitelisted all of the US IPs given in the documentation. Any ideas? We’re baffled.

Thanks,

Brian

3

Hi @bmosher,

I understand you’ve whitelisted all the Auth0 US IP addresses listed here and still having trouble connecting to your custom DB.

You mentioned that your development tenant is in US-4 and staging and production are in US-5. This should not have any interference with connecting to your custom DB.

I have checked your development, staging and production tenants, and found that they have identical custom DB setup across all environments. When looking through the logs, I found no related records on the staging and production tenants.

One option that might help is to use the Real-time Webtask Logs extension with console.log() debugging statements to see what kind of output is happening when your staging and production tenants fail to connect to your custom DB.

Let me know what you find.

Thanks,
Rueben

4

I have results, but this will not let me attach or embed images, so I’m not really sure how to show the results.

5

Hi @bmosher,

Thanks for the reply.

Would you be able to share the Real-time Webtask Logs in text form instead?

If not, are you able to share just the error message?