Azure Virtual Network
An Azure networking service that is used to provision private networks and optionally to connect to on-premises datacenters.
2,489 questions
Azure app service with private endpoint - throws 403 on kudu
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(3.2, 31%, 10%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ES%3C/text%3E%3C/svg%3E)
SecretNest
1
Reputation point
Hi.
First of all, I've read https://learn.microsoft.com/en-us/answers/questions/264747/azure-app-service-with-private-endpoint-throws-403.html, which didn't resolve my problem.
I have a private network to connect a web app to a sqlserver instance. While adding the web app, a dns zone named "privatelink.azurewebsites.net" is created with 2 records (scm and not) pointed to the private ip of the web app. While adding the sqlserver instance to this zone, another dns zone is created using "privatelink.database.windows.net" as its name, with one record pointed to the sqlserver instance. 2 zones are created forcely on the same private network.
After that, I cannot visit the kudu. 403 Fordidden.
I've tried to separate them into 2 subnets. But kudu still cannot accept.
How to resolve this problem? Thanks.
{count} votes
-
SecretNest 1 Reputation point
2021-03-15T09:59:01.147+00:00 Or, any guide for connecting a web app to sql server instance using private network?
-
brtrach-MSFT 16,506 Reputation points Microsoft Employee2021-03-16T04:22:39.687+00:00 @SecretNest We apologize for the 403 error you are receiving when trying to visit kudu with private endpoint setup.
It sounds like you followed the steps in this documentation to have a dedicated DNS record for scm. Can you please verify you followed these steps?
If the DNS appears to be setup properly then the next resource I would suggest referring to is this architectural document, which talks about a web app with private database connectivity.
Lastly, if you followed the architectural design and are still receiving 403 errors, please reply back and let us know so we can assist you further.
-
SecretNest 1 Reputation point
2021-03-16T04:49:36.92+00:00 Thanks for your reply.
Due to too complicated to implement this private network, we choose to use public ip with firewall setting to get around of this.
Thanks again for your help.
Sign in to comment
Sign in to answer