question

akhtarsayyad avatar image
0 Votes"
akhtarsayyad asked JooLucasFAndreatta-4135 commented

Storage account Private end points not accessible from site-to-site vpn

I have enable private endpoints on the blob storage where I have hosted static website. If I go to the VM hosted in the same vnet I can access the endpoints. But from my computer where I have site-to-site vpn enabled I can not access and getting error 404.
From my computer I can access VM using private IP hosted in the same vnet/subnet where I have BLOB with private endpoint.

Did any one try this, is that working?

azure-blob-storageazure-static-web-appsazure-private-link
· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Restartalwais on your doc. in Power S.

0 Votes 0 ·

1 Answer

yusuke avatar image
0 Votes"
yusuke answered akhtarsayyad commented

I guess that you enabled a private DNS zone to your VNet. In this situation, your computer outside of VNet can't get the private IP address of a static website because your computer can't access 168.63.129.16 which has a private DNS zone.

To access a static website through a private endpoint from the outside of VNET, there are three options.

  1. Add the new entry which links the FQDN of a static website to the private IP address of a Private endpoint in hosts file.

  2. Add the new entry which links the FQDN of a static website to the private IP address of a Private endpoint in the DNS server which your computer uses

  3. Create DNS forwarder in your VNet and Set this DNS server to your computer

Best reagerds

· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

In the private DNS zone I have option 1 setup in place but it is not working i.e. abc.privatelink.web.core.windows.net is linked to the private IP of private endpoint.

0 Votes 0 ·