PL edits

Author: Harikrishnan-M-B

articles/frontdoor/how-to-enable-private-link-storage-static-website.md

@@ -135,6 +135,13 @@ Once the origin is added and the private endpoint connection is approved, you ca
 
 ::: zone-end
 
+## Common mistakes to avoid
+
+The following are common mistakes when configuring an origin with Azure Private Link enabled:
+
+* Adding the origin with Azure Private Link enabled to an existing origin group that contains public origins. Azure Front Door doesn't allow mixing public and private origins in the same origin group.
+
+
 ## Next steps
 
 Learn about [Private Link service with storage account](../storage/common/storage-private-endpoints.md).

articles/frontdoor/standard-premium/how-to-enable-private-link-internal-load-balancer.md

@@ -65,6 +65,11 @@ In this section, you map the Private Link service to a private endpoint created
 
 1. The *connection state* should change to **Approved**. It might take a couple of minutes for the connection to fully establish. You can now access your internal load balancer from Azure Front Door.
 
+## Common mistakes to avoid
+
+The following are common mistakes when configuring an origin with Azure Private Link enabled:
+
+* Adding the origin with Azure Private Link enabled to an existing origin group that contains public origins. Azure Front Door doesn't allow mixing public and private origins in the same origin group.
 
 ## Next steps
 

articles/frontdoor/standard-premium/how-to-enable-private-link-storage-account-cli.md

@@ -66,6 +66,13 @@ az afd origin create --enabled-state Enabled \
 > [!NOTE]
 > If the blob or container within the storage account does not allow anonymous access, requests must be authorized. One way to authorize requests is by using [shared access signatures](../../storage/common/storage-sas-overview.md).
 
+## Common mistakes to avoid
+
+The following are common mistakes when configuring an origin with Azure Private Link enabled:
+
+* Adding the origin with Azure Private Link enabled to an existing origin group that contains public origins. Azure Front Door doesn't allow mixing public and private origins in the same origin group.
+* Not using SAS tokens while connecting to storage account that does not allow anonymous access.
+
 ## Next steps
 
 Learn more about [Private Link service with storage account](../../storage/common/storage-private-endpoints.md).

articles/frontdoor/standard-premium/how-to-enable-private-link-storage-account.md

@@ -72,6 +72,13 @@ In this section, you map the Private Link service to a private endpoint created
 > [!NOTE]
 > If the blob or container within the storage account doesn't permit anonymous access, requests made against the blob/container should be authorized. One option for authorizing a request is by using [shared access signatures](../../storage/common/storage-sas-overview.md).
 
+## Common mistakes to avoid
+
+The following are common mistakes when configuring an origin with Azure Private Link enabled:
+
+* Adding the origin with Azure Private Link enabled to an existing origin group that contains public origins. Azure Front Door doesn't allow mixing public and private origins in the same origin group.
+* Not using SAS tokens while connecting to storage account that does not allow anonymous access.
+
 ## Next steps
 
 Learn about [Private Link service with storage account](../../storage/common/storage-private-endpoints.md).

articles/frontdoor/standard-premium/how-to-enable-private-link-web-app-cli.md

@@ -63,6 +63,12 @@ az afd origin create --enabled-state Enabled \
 
 3. Once approved, it takes a few minutes for the connection to fully establish. You can now access your App Service from Azure Front Door Premium. Direct access to the App Service from the public internet will be disabled after the private endpoint is enabled.
 
+## Common mistakes to avoid
+
+The following are common mistakes when configuring an origin with Azure Private Link enabled:
+
+* Adding the origin with Azure Private Link enabled to an existing origin group that contains public origins. Azure Front Door doesn't allow mixing public and private origins in the same origin group.
+
 ## Next steps
 
 Learn more about [Private Link service with App Service](../../app-service/networking/private-endpoint.md).

articles/frontdoor/standard-premium/how-to-enable-private-link-web-app.md

@@ -67,6 +67,13 @@ In this section, you map the Private Link service to a private endpoint within A
 
 1. After approval, the connection status will update. It can take a few minutes for the connection to fully establish. Once established, you can access your web app through Azure Front Door Premium. Direct access to the web app from the public internet is disabled once private endpoint is enabled.
 
+## Common mistakes to avoid
+
+The following are common mistakes when configuring an origin with Azure Private Link enabled:
+
+* Adding the origin with Azure Private Link enabled to an existing origin group that contains public origins. Azure Front Door doesn't allow mixing public and private origins in the same origin group. 
+
+
 ## Next steps
 
 Learn about [Private Link service with App service](../../app-service/networking/private-endpoint.md).