Azure Monitor engineer suggests using wildcard instead of <cluster-region-name> for the FQDN of Azure Monitor for containers

[SnoWolfT]

As suggested by this document, we need to replace the part.

.ingest.monitor.azure.com | HTTPS:443 | This endpoint is used by Azure Monitor managed service for Prometheus metrics ingestion. .handler.control.monitor.azure.com | HTTPS:443 | This endpoint is used to fetch data collection rules for a specific cluster. But if I make research and find some examples in the MS Docs are as below. my-dce-5kyl.**eastus-1**.ingest.monitor.azure.com logs-ingestion-rzmk.**eastus2-1**.ingest.monitor.azure.com dceforjsonlog-rnwt.**centralus-1**.ingest.monitor.azure.com As discussed with Azure Monitor engineer, he suggests using wildcard instead of for the FQDN of Azure Monitor for containers. Please double confirm that. If true, does this document need to be updated? --- #### Document Details ⚠ *Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.* * ID: 64b637d2-4ed9-c7c4-65ad-2ff13db82d3b * Version Independent ID: 711e707f-83cd-6621-ac7d-6f59b0cb37fa * Content: [Outbound network and FQDN rules for Azure Kubernetes Service (AKS) clusters - Azure Kubernetes Service](https://learn.microsoft.com/en-us/azure/aks/outbound-rules-control-egress#azure-monitor-for-containers) * Content Source: [articles/aks/outbound-rules-control-egress.md](https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/aks/outbound-rules-control-egress.md) * Service: **azure-kubernetes-service** * Sub-service: **aks-networking** * GitHub Login: @asudbring * Microsoft Alias: **allensu**

[PesalaPavan]

@SnoWolfT, Thanks for your feedback! I've assigned this issue to the author who will investigate and update as appropriate.

[sf-msft]

reassign:sf-msft