Merge pull request #314169 from JasonWHowell/Fix-links-to-docs.azure.cn

Replacing docs.azure.cn links with local Azure links

Author: prmerger-automator[bot]

articles/application-gateway/json-web-token-overview.md

@@ -11,7 +11,7 @@ ms.date: 11/18/2025
 
 # JSON Web Token (JWT) validation in Azure Application Gateway (preview)
 
-[Azure Application Gateway](/azure/application-gateway/) validates JSON Web Tokens (JWTs) issued by [Microsoft Entra ID](https://docs.azure.cn/en-us/entra/fundamentals/what-is-entra) (formerly Azure Active Directory) in incoming HTTPS requests. This capability provides first-hop authentication enforcement for web APIs or any protected resource without requiring custom code in your backend applications.
+[Azure Application Gateway](/azure/application-gateway/) validates JSON Web Tokens (JWTs) issued by [Microsoft Entra ID](/entra/fundamentals/what-is-entra) (formerly Azure Active Directory) in incoming HTTPS requests. This capability provides first-hop authentication enforcement for web APIs or any protected resource without requiring custom code in your backend applications.
 
 This capability verifies the integrity and authenticity of tokens in incoming requests. It then determines whether to allow or deny access before forwarding traffic to backend services. Upon successful validation, the gateway injects the `x-msft-entra-identity` header into the request and forwards it to the backend. Downstream applications can then securely consume verified identity information.
 

articles/dns/sharding-private-dns-zones.md

@@ -145,7 +145,7 @@ Smaller environments or single-team deployments can continue using a flat privat
 
 ## Zone size and observability considerations
 
-Azure Private DNS enforces service limits on the number of record sets per zone and the number of records per record set. However, operational complexity and resiliency often increase well before these limits are reached. For current limits, see [Azure Private DNS Limits](https://docs.azure.cn/en-us/dns/private-dns-privatednszone#limits).
+Azure Private DNS enforces service limits on the number of record sets per zone and the number of records per record set. However, operational complexity and resiliency often increase well before these limits are reached. For current limits, see [Azure Private DNS Limits](private-dns-privatednszone.md#limits).
 
 As Private DNS Zones grow, especially in multiteam environments, zone size becomes an important operational signal. Large, flat zones can accumulate tens of thousands of records over time, making your workloads harder to govern and increasing the impact radius of changes.
 

articles/storage-mover/cloud-to-cloud-private-network-configs.md

@@ -85,7 +85,7 @@ Example custom IPsec/IKE settings (validate against your device compatibility):
 
 :::image type="content" source="./media/cloud-to-cloud-networking/ipsec-policy.png" alt-text="Screenshot of ipsec policy." lightbox="./media/cloud-to-cloud-networking/ipsec-policy.png":::
 
-**Learn more:** [Configure custom IPsec/IKE connection policies](https://docs.azure.cn/en-us/vpn-gateway/ipsec-ike-policy-howto).
+**Learn more:** [Configure custom IPsec/IKE connection policies](/azure/vpn-gateway/ipsec-ike-policy-howto).
 
 ### SD-WAN with network virtual appliances (NVAs)
 

articles/storage-mover/migrations-requiring-private-connections.md

@@ -31,7 +31,7 @@ Before you begin, ensure that you have the following resources and configuration
 
 ### Prerequisites for creating a private connection
 
-- A [Private Link Service Direct Connect](https://docs.azure.cn/en-us/private-link/create-private-link-service-portal?tabs=dynamic-ip) configured and ready to use.
+- A [Private Link Service Direct Connect](../private-link/create-private-link-service-portal.md) configured and ready to use.
 - Familiarity with [Azure Private Link networking documentation](/azure/private-link/).
 
 ## Known limits

articles/storage/blobs/soft-delete-vs-versioning-options.md

@@ -13,7 +13,7 @@ ms.date: 09/15/2025
 
 This article helps you determine when to enable soft delete, versioning, both, or neither.
 
-Both **blob soft delete** and **blob versioning** can help you protect from deletes and overwrites. These features can be used independently or together, depending on your workload, cost sensitivity, and recovery needs. To learn about other ways to protect blobs and containers, see [data protection overview](https://docs.azure.cn/en-us/storage/blobs/data-protection-overview).
+Both **blob soft delete** and **blob versioning** can help you protect from deletes and overwrites. These features can be used independently or together, depending on your workload, cost sensitivity, and recovery needs. To learn about other ways to protect blobs and containers, see [data protection overview](data-protection-overview.md).
 
 ## Our recommendation