From f43f6bf284c44a0728fe5a02b6aba941079728d0 Mon Sep 17 00:00:00 2001 From: Terence Truong Date: Fri, 28 Mar 2025 11:12:51 -0400 Subject: [PATCH 1/5] updated endpoints for China region Signed-off-by: Terence Truong --- docs/client-firewall-rules.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/docs/client-firewall-rules.md b/docs/client-firewall-rules.md index 2348e96..c282618 100644 --- a/docs/client-firewall-rules.md +++ b/docs/client-firewall-rules.md @@ -13,6 +13,11 @@ To access Registry Endpoint and MAR discovery UI, the following FQDNs are requir | - | - | - | | Registry Endpoint and MAR discovery UI | https | `mcr.microsoft.com` | | Data Endpoint | https | `*.data.mcr.microsoft.com` | +| Registry Endpoint for China Region | https | `mcr.azure.cn` +| Data Endpoint for China Region | https | `*.data.mcr.azure.cn` | + +> **Note:** The China region endpoints (`mcr.azure.cn`) and (`*.data.mcr.azure.cn`) are counterparts to (`mcr.microsoft.com`) and (`*.data.mcr.microsoft.com`). + > **Note:** MAR provides global coverage through Azure Traffic Manager for the registry REST endpoint, with regional CDNs for the data endpoints. > Over time, MAR regional endpoints _will change_ assuring the best performance for our customers. It is strongly recommended to avoid using region specific rules. The `*.data.mcr.microsoft.com` firewall rules will avoid disruption as we alter regions for performance & readability. From 66639309924f7ba9abed1b128c1242ad119cee7b Mon Sep 17 00:00:00 2001 From: Terence Truong Date: Fri, 28 Mar 2025 11:14:39 -0400 Subject: [PATCH 2/5] added line breaker Signed-off-by: Terence Truong --- docs/client-firewall-rules.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/client-firewall-rules.md b/docs/client-firewall-rules.md index c282618..b2eece3 100644 --- a/docs/client-firewall-rules.md +++ b/docs/client-firewall-rules.md @@ -13,7 +13,7 @@ To access Registry Endpoint and MAR discovery UI, the following FQDNs are requir | - | - | - | | Registry Endpoint and MAR discovery UI | https | `mcr.microsoft.com` | | Data Endpoint | https | `*.data.mcr.microsoft.com` | -| Registry Endpoint for China Region | https | `mcr.azure.cn` +| Registry Endpoint for China Region | https | `mcr.azure.cn` | | Data Endpoint for China Region | https | `*.data.mcr.azure.cn` | > **Note:** The China region endpoints (`mcr.azure.cn`) and (`*.data.mcr.azure.cn`) are counterparts to (`mcr.microsoft.com`) and (`*.data.mcr.microsoft.com`). From fb9a00028ef5c246680a6b3bd3320cf4230a8a36 Mon Sep 17 00:00:00 2001 From: Terence Truong Date: Fri, 28 Mar 2025 11:18:32 -0400 Subject: [PATCH 3/5] updated mcr-endpoints-guidance.md Signed-off-by: Terence Truong --- docs/mcr-endpoints-guidance.md | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/docs/mcr-endpoints-guidance.md b/docs/mcr-endpoints-guidance.md index 8da2b87..8b4d5c6 100644 --- a/docs/mcr-endpoints-guidance.md +++ b/docs/mcr-endpoints-guidance.md @@ -24,6 +24,10 @@ To access Registry Endpoint and MAR discovery UI, the following FQDNs should be | - | - | - | | Registry Endpoint and MAR discovery UI | https | `mcr.microsoft.com` | | Data Endpoint | https | `*.data.mcr.microsoft.com` | +| Registry Endpoint for China Region | https | `mcr.azure.cn` | +| Data Endpoint for China Region | https | `*.data.mcr.azure.cn` | + +> **Note:** The China region endpoints (`mcr.azure.cn`) and (`*.data.mcr.azure.cn`) are counterparts to (`mcr.microsoft.com`) and (`*.data.mcr.microsoft.com`). > **Note:** MAR provides global coverage through Azure Traffic Manager for the registry endpoint, with regional CDNs managed by Azure Front Door for the data endpoints. > Over time, MAR team will continue adding regional endpoints to ensure the best performance for our customers. Check the [MAR Firewall Rules][mcr-firewall-rules] article for details how to configure your firewall rules. @@ -36,12 +40,15 @@ MAR registry REST endpoints are available in the following nine locations: - Asia South East - Europe North - Europe West +- North China +- East China - US Central - US East - US West - US West 2 - US West-Central + ## MAR Data Endpoint Locations MAR uses Azure Front Door CDN point of presence (POP) locations to provide reliable delivery of Microsoft content. Single CDN POP location can have multiple nodes serving the MAR content. To obtain the list of CDN POP locations for MAR use the following articles from Azure Front Door: @@ -63,4 +70,4 @@ If you experience issues with pulling artifact from MAR, [contact Microsoft Supp [azure-cdn-china]: https://docs.azure.cn/cdn/cdn-pops [oci-spec]: https://github.com/opencontainers/distribution-spec [oci-artifacts]: https://github.com/opencontainers/artifacts -[mcr-firewall-rules]: ../client-firewall-rules.md +[mcr-firewall-rules]: client-firewall-rules.md From 51c7a0931fdc542b66b500e067881b23ec13fa81 Mon Sep 17 00:00:00 2001 From: Terence Truong Date: Mon, 31 Mar 2025 11:28:27 -0400 Subject: [PATCH 4/5] Updated guidance based on comments Signed-off-by: Terence Truong --- docs/client-firewall-rules.md | 10 ++++++---- docs/mcr-endpoints-guidance.md | 7 ++++--- 2 files changed, 10 insertions(+), 7 deletions(-) diff --git a/docs/client-firewall-rules.md b/docs/client-firewall-rules.md index b2eece3..c205ebf 100644 --- a/docs/client-firewall-rules.md +++ b/docs/client-firewall-rules.md @@ -16,11 +16,13 @@ To access Registry Endpoint and MAR discovery UI, the following FQDNs are requir | Registry Endpoint for China Region | https | `mcr.azure.cn` | | Data Endpoint for China Region | https | `*.data.mcr.azure.cn` | -> **Note:** The China region endpoints (`mcr.azure.cn`) and (`*.data.mcr.azure.cn`) are counterparts to (`mcr.microsoft.com`) and (`*.data.mcr.microsoft.com`). +> [!NOTE] +> The China region endpoints (`mcr.azure.cn` and `*.data.mcr.azure.cn`) are counterparts to (`mcr.microsoft.com` and `*.data.mcr.microsoft.com`). - -> **Note:** MAR provides global coverage through Azure Traffic Manager for the registry REST endpoint, with regional CDNs for the data endpoints. -> Over time, MAR regional endpoints _will change_ assuring the best performance for our customers. It is strongly recommended to avoid using region specific rules. The `*.data.mcr.microsoft.com` firewall rules will avoid disruption as we alter regions for performance & readability. +> [!NOTE] +> MAR provides global coverage through Azure Traffic Manager for the registry REST endpoint, with regional CDNs for the data endpoints. +> Over time, MAR regional endpoints _will change_ assuring the best performance for our customers. +> It is strongly recommended to avoid using region specific rules. The `*.data.mcr.microsoft.com` firewall rules will avoid disruption as we alter regions for performance & readability. Within Azure, the following configuration may be applied: diff --git a/docs/mcr-endpoints-guidance.md b/docs/mcr-endpoints-guidance.md index 8b4d5c6..29c6db0 100644 --- a/docs/mcr-endpoints-guidance.md +++ b/docs/mcr-endpoints-guidance.md @@ -27,9 +27,11 @@ To access Registry Endpoint and MAR discovery UI, the following FQDNs should be | Registry Endpoint for China Region | https | `mcr.azure.cn` | | Data Endpoint for China Region | https | `*.data.mcr.azure.cn` | -> **Note:** The China region endpoints (`mcr.azure.cn`) and (`*.data.mcr.azure.cn`) are counterparts to (`mcr.microsoft.com`) and (`*.data.mcr.microsoft.com`). +> [!NOTE] +> The China region endpoints (`mcr.azure.cn` and `*.data.mcr.azure.cn`) are counterparts to (`mcr.microsoft.com` and `*.data.mcr.microsoft.com`). -> **Note:** MAR provides global coverage through Azure Traffic Manager for the registry endpoint, with regional CDNs managed by Azure Front Door for the data endpoints. +> [!NOTE] +> MAR provides global coverage through Azure Traffic Manager for the registry endpoint, with regional CDNs managed by Azure Front Door for the data endpoints. > Over time, MAR team will continue adding regional endpoints to ensure the best performance for our customers. Check the [MAR Firewall Rules][mcr-firewall-rules] article for details how to configure your firewall rules. ## MAR Registry Endpoint Locations @@ -48,7 +50,6 @@ MAR registry REST endpoints are available in the following nine locations: - US West 2 - US West-Central - ## MAR Data Endpoint Locations MAR uses Azure Front Door CDN point of presence (POP) locations to provide reliable delivery of Microsoft content. Single CDN POP location can have multiple nodes serving the MAR content. To obtain the list of CDN POP locations for MAR use the following articles from Azure Front Door: From b3d561d88654b46e9bb032504d67d851ee65751e Mon Sep 17 00:00:00 2001 From: Terence Truong Date: Tue, 1 Apr 2025 10:07:52 -0400 Subject: [PATCH 5/5] updated endpoints Signed-off-by: Terence Truong --- docs/mcr-endpoints-guidance.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/mcr-endpoints-guidance.md b/docs/mcr-endpoints-guidance.md index 29c6db0..4b157c6 100644 --- a/docs/mcr-endpoints-guidance.md +++ b/docs/mcr-endpoints-guidance.md @@ -2,7 +2,7 @@ title: Guidance for using the official Microsoft Artifact Registry (MAR) endpoints description: This articles provides information about the official endpoints of Microsoft Artifact Registry (MAR) and provides guidance how to use the REST and CDN endpoints to pull official Microsoft artifacts around the world. ms.topic: guidance -ms.date: 05/25/2022 +ms.date: 04/01/2025 ms.author: ttruong author: terencet-dev ms.custom: @@ -40,10 +40,10 @@ MAR registry REST endpoints are available in the following nine locations: - Asia East - Asia South East +- China East 3 +- China North 3 - Europe North - Europe West -- North China -- East China - US Central - US East - US West