Skip to content

Commit 87c94ba

Browse files
authored
Update storage-blob-static-website.md
Updating a Public Documentation FAQ regarding the PE Enabled and not able to access static websites in storage account.
1 parent 9856ceb commit 87c94ba

File tree

1 file changed

+4
-0
lines changed

1 file changed

+4
-0
lines changed

articles/storage/blobs/storage-blob-static-website.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -116,6 +116,10 @@ Yes. Storage account [network security rules](../common/storage-network-security
116116

117117
<a name='do-static-websites-support-azure-active-directory-azure-ad'></a>
118118

119+
##### Why am I unable to access static websites in a storage account when a private endpoint is enabled for the blob in the storage account.?
120+
121+
Enabling a private endpoint for blobs in a storage account restricts access to that storage account to only resources within the same virtual network. Consequently, this restriction prevents external access to the static website hosted in the storage account, making the static website content inaccessible. The private endpoint configuration limits access to all storage account resources, including the static website content, to resources within the same virtual network where the private endpoint is enabled. The resolution would be to create a private endpoint specifically for the static website.
122+
119123
##### Do static websites support Microsoft Entra ID?
120124

121125
No. A static website only supports anonymous read access for files in the **$web** container.

0 commit comments

Comments
 (0)