Merge pull request #270105 from dramasamy/nnf-t-proxy

Add a note about VNF VM image pull

Author: prmerger-automator[bot]

articles/operator-nexus/howto-virtual-machine-image.md

@@ -197,6 +197,9 @@ echo "VNF image $ACR_URL/$CONTAINER_IMAGE_NAME:$CONTAINER_IMAGE_TAG created succ
 
 After executing the script, you'll have a VM image tailored for your Virtual Network Function (VNF). You can use this image to deploy your VNF.
 
+> [!NOTE]
+> To ensure that the VNF image can be pulled correctly, ensure the ACR URL is in the egress allow list of the cloud services network that you will use with your Operator Nexus virtual machine.
+
 ## Example usage
 
 1. Set the required environment variables.

articles/operator-nexus/quickstarts-tenant-workload-prerequisites.md

@@ -236,6 +236,9 @@ New-AzNetworkCloudServicesNetwork -CloudServicesNetworkName "<YourCloudServicesN
 
 After setting up the cloud services network, you can use it to create a VM or cluster that can connect to the egress endpoints you have specified. Remember that the proxy only works with HTTPS.
 
+> [!NOTE]
+> To ensure that the VNF image can be pulled correctly, ensure the ACR URL is in the egress allow list of the cloud services network that you will use with your Operator Nexus virtual machine.
+
 #### Using the proxy to reach outside of the virtual machine
 
 After creating your Operator Nexus VM or Operator Nexus Kubernetes cluster with this cloud services network, you need to additionally set appropriate environment variables within VM to use tenant proxy and to reach outside of virtual machine. This tenant proxy is useful if you need to access resources outside of the virtual machine, such as managing packages or installing software.