You turn off public access on a storage account, add a private endpoint, deploy... and your app gets a 403 "This request is not authorized to perform this operation" .
The networking is almost never the problem. It's DNS.
This post walks through a Bicep pattern that works, explains why each piece is there, and covers the hybrid DNS gotchas that bite once on-premises networks get involved.
Why it breaks
When you create a private endpoint for mystorage.blob.core.windows.net , Azure changes the public DNS record into a CNAME:
mystorage.blob.core.windows.net -> CNAME mystorage.privatelink.blob.core.windows.net
Enter fullscreen mode
Exit fullscreen mode
If your client can resolve privatelink.blob.core.windows.net from a private DNS zone , it gets the endpoint's private IP (say 10.10.0.4 ) and everything works.
If it can't, the lookup falls through to public DNS, the client gets the account's public IP, and because public network access is disabled, the request is refused.
So the job is: make sure every…