Update articles/deployment-environments/how-to-configure-extensibility-generic-container-image.md

Co-authored-by: Max Horstmann <[email protected]>

Author: RoseHJM

articles/deployment-environments/how-to-configure-extensibility-generic-container-image.md

@@ -139,7 +139,7 @@ In order to use custom images, you need to store them in a container registry. A
 It's also possible to store the image in a different container registry such as Docker Hub, but in that case it needs to be publicly accessible.
 
 > [!Caution]
-> Enabling anonymous (unauthenticated) pull access makes all registry content publicly available for read (pull) actions. 
+> Storing your container image in a registry with anonymous (unauthenticated) pull access makes it publicly accessible. Don't do that if your image contains any sensitive information. Instead, store it in Azure Container Instances (ACR) with anonymous pull access disabled.
 
 To use a custom image stored in the ACR, you need to ensure that ADE has appropriate permissions to access your image. When you create an ACR instance, it's secure by default and only allows authenticated users to gain access. With this configuration, you don't have to enable anonymous pull access.