Merge pull request #259979 from MicrosoftDocs/repo_sync_working_branch

Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/azure-docs (branch main)

Author: Taojunshen

articles/active-directory-b2c/best-practices.md

@@ -41,7 +41,6 @@ Define your application and service architecture, inventory current systems, and
 | Migrate existing apps to b2clogin.com | The deprecation of login.microsoftonline.com will go into effect for all Azure AD B2C tenants on 04 December 2020. [Learn more](b2clogin.md). |
 | Use Identity Protection and Conditional Access | Use these capabilities for significantly greater control over risky authentications and access policies. Azure AD B2C Premium P2 is required. [Learn more](conditional-access-identity-protection-overview.md). |
 |Tenant size | You need to plan with Azure AD B2C tenant size in mind. By default, Azure AD B2C tenant can accommodate 1.25 million objects (user accounts and applications). You can increase this limit to 5.25 million objects by adding a custom domain to your tenant, and verifying it. If you need a bigger tenant size, you need to contact [Support](find-help-open-support-ticket.md).|
-| Use Identity Protection and Conditional Access | Use these capabilities for greater control over risky authentications and access policies. Azure AD B2C Premium P2 is required. [Learn more](conditional-access-identity-protection-overview.md). |
 
 ## Implementation
 

articles/aks/azure-csi-disk-storage-provision.md

@@ -328,7 +328,7 @@ When you create an Azure disk for use with AKS, you can create the disk resource
     pvc-azuredisk   Bound    pv-azuredisk   20Gi        RWO                           5s
     ```
 
-5. Create a *azure-disk-pod.yaml* file to reference your *PersistentVolumeClaim*.
+5. Create an *azure-disk-pod.yaml* file to reference your *PersistentVolumeClaim*.
 
     ```yaml
     apiVersion: v1

articles/expressroute/about-fastpath.md

@@ -35,6 +35,8 @@ While FastPath supports most configurations, it doesn't support the following fe
 
 * Private Link: FastPath Connectivity to a private endpoint or Private Link service over an ExpressRoute Direct circuit is supported for limited scenarios. For more information, see [enable FastPath and Private Link for 100 Gbps ExpressRoute Direct](expressroute-howto-linkvnet-arm.md#fastpath-and-private-link-for-100-gbps-expressroute-direct). FastPath connectivity to a Private endpoint/Private Link service is not supported for ExpressRoute partner circuits.
 
+* DNS Private Resolver: Azure ExpressRoute FastPath does not support connectivity to [DNS Private Resolver](../dns/dns-private-resolver-overview.md).
+
 ### IP address limits
 
 | ExpressRoute SKU | Bandwidth | FastPath IP limit |

articles/machine-learning/prompt-flow/how-to-secure-prompt-flow.md

@@ -99,6 +99,6 @@ Workspace managed virtual network is the recommended way to support network isol
 
 - [Secure workspace resources](../how-to-secure-workspace-vnet.md)
 - [Workspace managed network isolation](../how-to-managed-network.md)
-- [Secure Azure Kubernetes Service inferencing environment](../how-to-secure-online-endpoint.md)
-- [Secure your managed online endpoints with network isolation](../how-to-secure-kubernetes-inferencing-environment.md)
+- [Secure Azure Kubernetes Service inferencing environment](../how-to-secure-kubernetes-inferencing-environment.md)
+- [Secure your managed online endpoints with network isolation](../how-to-secure-online-endpoint.md)
 - [Secure your RAG workflows with network isolation](../how-to-secure-rag-workflows.md)