Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into erratelimiting

Author: duongau

articles/active-directory-b2c/custom-domain.md

@@ -331,14 +331,6 @@ https://<domain-name>/11111111-1111-1111-1111-111111111111/v2.0/
 ```
 ::: zone pivot="b2c-custom-policy"
 
-## (Optional) Block access to the default domain name
-
-After you add the custom domain and configure your application, users will still be able to access the &lt;tenant-name&gt;.b2clogin.com domain. If you want to prevent access, you can configure the policy to check the authorization request "host name" against an allowed list of domains. The host name is the domain name that appears in the URL. The host name is available through `{Context:HostName}` [claim resolvers](claim-resolver-overview.md). Then you can present a custom error message. 
-
-1. Get the example of a conditional access policy that checks the host name from [GitHub](https://github.com/azure-ad-b2c/samples/tree/master/policies/check-host-name).
-1. In each file, replace the string `yourtenant` with the name of your Azure AD B2C tenant. For example, if the name of your B2C tenant is *contosob2c*, all instances of `yourtenant.onmicrosoft.com` become `contosob2c.onmicrosoft.com`.
-1. Upload the policy files in the following order: `B2C_1A_TrustFrameworkExtensions_HostName.xml` and then `B2C_1A_signup_signin_HostName.xml`.
-
 ::: zone-end
 
 

articles/azure-government/compliance/azure-services-in-fedramp-auditscope.md

@@ -325,7 +325,7 @@ This article provides a detailed list of Azure, Dynamics 365, Microsoft 365, and
 | [Cloud Services](../../cloud-services/index.yml) | ✅ | ✅ | ✅ | ✅ | ✅ |
 | [Cloud Shell](../../cloud-shell/overview.md) | ✅ | ✅ | ✅ | ✅ | ✅ |
 | **Service** | **FedRAMP High** | **DoD IL2** | **DoD IL4** | **DoD IL5** | **DoD IL6** |
-| [Cognitive Search](../../search/index.yml) (formerly Azure Search) | ✅ | ✅ | ✅ | ✅ | ✅ |
+| [Azure AI Search](../../search/index.yml) (formerly Azure Cognitive Search) | ✅ | ✅ | ✅ | ✅ | ✅ |
 | [Azure AI services: Computer Vision](../../ai-services/computer-vision/index.yml) | ✅ | ✅ | ✅ | ✅ | |
 | [Azure AI services: Content Moderator](../../ai-services/content-moderator/index.yml) | ✅ | ✅ | ✅ | ✅ | |
 | [Azure AI containers](../../ai-services/cognitive-services-container-support.md) | ✅ | ✅ | ✅ | ✅ | |

articles/azure-vmware/azure-vmware-solution-platform-updates.md

@@ -126,7 +126,7 @@ AV52 is now available in the East US 2 Region. This node size is used for inte
 
 **Customer-managed keys using Azure Key Vault**
 
-You can use customer-managed keys to bring and manage your master encryption keys to encrypt vSAN. Azure Key Vault allows you to store your privately managed keys securely to access your Azure VMware Solution data.
+You can use customer-managed keys to bring and manage your master encryption keys to encrypt vSAN data. Azure Key Vault allows you to store your privately managed keys securely to access your Azure VMware Solution data.
 
 **Azure NetApp Files - more storage options available**    
 
@@ -140,7 +140,7 @@ For more information, see [Azure Migration and Modernization blog](https://techc
 
 ## January 2023
 
-Starting January 2023, all new Azure VMware Solution private clouds are being deployed with Microsoft signed TLS certificate for vCenter Server and NSX-T Data Center.
+Starting January 2023, all new Azure VMware Solution private clouds are being deployed with Microsoft signed TLS certificate for vCenter Server and NSX.
 
 ## November 2022
 

articles/azure-vmware/faq.yml

@@ -245,7 +245,7 @@ sections:
         answer: Each ESXi host has two vSAN disk groups with a capacity tier of 15.2 TB and a 3.2-TB NVMe cache tier (1.6 TB in each disk group).      
 
       - question: Is data stored on the vSAN datastores encrypted at rest?
-        answer: Yes, vSAN datastores use data-at-rest encryption by default using keys stored in Azure Key Vault. The encryption solution is KMS-based and supports vCenter Server operations for key management.  When a host is removed from a vSphere cluster, data on SSDs is invalidated immediately.
+        answer: Yes, vSAN datastores use data-at-rest encryption by default using keys stored in Azure Key Vault. The encryption solution is KMS-based and supports vCenter Server operations for key management.  When a host is removed from a vSphere cluster, data on disk is invalidated immediately.
 
       - question: Can I rename a datastore or cluster during creation?
         answer: No, you can't change the name of datastores or clusters.

articles/azure-vmware/media/application-gateway/app-gateway-protects.png

@@ -3,7 +3,7 @@ title: Protect web apps on Azure VMware Solution with Azure Application Gateway
 description: Configure Azure Application Gateway to securely expose your web apps running on Azure VMware Solution.
 ms.topic: how-to
 ms.service: azure-vmware
-ms.date: 12/19/2023
+ms.date: 3/21/2024
 ms.custom: engagement-fy23
 ---
 

articles/azure-vmware/media/hub-spoke/azure-vmware-solution-second-level-traffic-segmentation.png

@@ -6,7 +6,7 @@ services: cdn
 author: duongau
 ms.service: azure-cdn
 ms.topic: how-to
-ms.date: 12/19/2023
+ms.date: 03/20/2024
 ms.author: duau
 ---
 
@@ -44,15 +44,15 @@ Contact support for any issues or assistance with Azure CDN from Edgio.
 
 For Azure Traffic Manager users with Multi-CDN:
 
-* If you registered an Edgio profile for your custom domain, you can delete your Akamai profile as your migration is complete.
-* Else, you need an extra TXT token validation to enable HTTPS with managed certificate. Contact support for further assistance.
+- If you registered an Edgio profile for your custom domain, you can delete your Akamai profile as your migration is complete.
+- Else, you need an extra TXT token validation to enable HTTPS with managed certificate. Contact support for further assistance.
 
 > [!TIP]
 > Items to validate related migration:
-> - HTTPS with Managed Certificate. To provision a managed certificate, you must CNAME your custom domain to an `azureedge.net`` endpoint. If you have changed the CNAME of your custom domain, check your HTTPS status and wait for the provisioning to complete.
+> - HTTPS with Managed Certificate. To provision a managed certificate, you must CNAME your custom domain to an `azureedge.net` endpoint. If you have changed the CNAME of your custom domain, check your HTTPS status and wait for the provisioning to complete.
 > - Azure CDN Standard from Edgio offers enhanced reporting and origin configuration options. You can access them by selecting the **Managed** button.
 
 ## Next steps
 
-* Create an [Azure Front Door](../frontdoor/create-front-door-portal.md) profile.
-* Create an [Azure CDN from Edgio](cdn-create-endpoint-how-to.md) profile.
+- Create an [Azure Front Door](../frontdoor/create-front-door-portal.md) profile.
+- Create an [Azure CDN from Edgio](cdn-create-endpoint-how-to.md) profile.