Merge pull request #235675 from maanasagovi/docs-editor/outbound-rules-control-egress-1682392265

Adding Additional Endpoints to the Egress List for Cluster extensions

Author: prmerger-automator[bot]

articles/aks/outbound-rules-control-egress.md

@@ -207,10 +207,13 @@ There are two options to provide access to Azure Monitor for containers:
 
 ### Required FQDN / application rules
 
-| FQDN | Port | Use |
+| FQDN | Port               | Use |
 |-----------------------------------------------|-----------|----------|
 | **`<region>.dp.kubernetesconfiguration.azure.com`** | **`HTTPS:443`** | This address is used to fetch configuration information from the Cluster Extensions service and report extension status to the service.|
 | **`mcr.microsoft.com, *.data.mcr.microsoft.com`** | **`HTTPS:443`** | This address is required to pull container images for installing cluster extension agents on AKS cluster.|
+|**`arcmktplaceprod.azurecr.io`**|**`HTTPS:443`**|This address is required to pull container images for installing marketplace extensions on AKS cluster.|
+|**`*.ingestion.msftcloudes.com, *.microsoftmetrics.com`**|**`HTTPS:443`**|This address is used to send agents metrics data to Azure.|
+|**`marketplaceapi.microsoft.com`**|**`HTTPS: 443`**|This address is used to send custom meter-based usage to the commerce metering API.|
 
 #### Azure US Government required FQDN / application rules