Merge pull request #286693 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/expressroute/expressroute-troubleshooting-arp-resource-manager.md

@@ -113,8 +113,8 @@ Sample output for one of the paths:
 ```output
 Age InterfaceProperty IpAddress  MacAddress    
 --- ----------------- ---------  ----------    
- 10 On-Prem           65.0.0.1   ffff.eeee.dddd
-  0 Microsoft         65.0.0.2   aaaa.bbbb.cccc
+ 10 On-Prem           20.33.0.1   ffff.eeee.dddd
+  0 Microsoft         20.33.0.2   aaaa.bbbb.cccc
 ```
 
 
@@ -131,15 +131,15 @@ The ARP table of a peering can be used to determine and validate layer 2 configu
 ```output
 Age InterfaceProperty IpAddress  MacAddress    
 --- ----------------- ---------  ----------    
- 10 On-Prem           65.0.0.1   ffff.eeee.dddd
-  0 Microsoft         65.0.0.2   aaaa.bbbb.cccc
+ 10 On-Prem           20.33.0.1   ffff.eeee.dddd
+  0 Microsoft         20.33.0.2   aaaa.bbbb.cccc
 ```
 or
 
 ```output
 Age InterfaceProperty IpAddress  MacAddress    
 --- ----------------- ---------  ----------    
- 10 On-Prem           65.0.0.1   ffff.eeee.dddd
+ 10 On-Prem           20.33.0.1   ffff.eeee.dddd
 ```
 
 ### ARP table when on-premises / connectivity provider side has problems
@@ -149,15 +149,15 @@ If a problem with the on-premises or connectivity provider occurs, the ARP table
 ```output
 Age InterfaceProperty IpAddress  MacAddress    
 --- ----------------- ---------  ----------   
-  0 On-Prem           65.0.0.1   Incomplete
-  0 Microsoft         65.0.0.2   aaaa.bbbb.cccc
+  0 On-Prem           20.33.0.1   Incomplete
+  0 Microsoft         20.33.0.2   aaaa.bbbb.cccc
 ```
 or
 
 ```output
 Age InterfaceProperty IpAddress  MacAddress    
 --- ----------------- ---------  ----------    
-  0 Microsoft         65.0.0.2   aaaa.bbbb.cccc
+  0 Microsoft         20.33.0.2   aaaa.bbbb.cccc
 ```  
 
 > [!NOTE]

articles/expressroute/expressroute-workflows.md

@@ -57,14 +57,14 @@ Ensure that the physical link and admin state are enabled across both links. Ref
 This section only pertains to the ExpressRoute partner connectivity model:
 
 * Provide the service key (s-key) to the connectivity provider.
-* Provide additional information needed by the connectivity provider (for example, VPN ID).
+* Provide additional information needed by the connectivity provider (for example, VLAN ID).
 * If the provider manages the routing configuration, provide the necessary details.
 
 You can ensure that the circuit has been provisioned successfully by verifying the ExpressRoute circuit provisioning state using PowerShell, the Azure portal or, CLI.
 
 ### 5. Configure routing domains
 
-Configure routing domains. If your connectivity provider manages Layer 3 configuration, they configure routing for your circuit. If your connectivity provider only offers Layer 2 services or if you're using ExpressRoute Direct, you must configure routing per the guidelines described in the [Routing requirements](expressroute-routing.md) and [Routing configuration](expressroute-howto-routing-classic.md) articles.
+Configure routing domains. If your connectivity provider manages Layer 3 configuration, they configure routing for your circuit. If your connectivity provider only offers Layer 2 services or if you're using ExpressRoute Direct, you must configure routing per the guidelines described in the [Routing requirements](expressroute-routing.md) and [Routing configuration](expressroute-howto-routing-arm.md) articles.
 
 #### For Azure private peering
 

articles/frontdoor/how-to-configure-endpoints.md

@@ -31,8 +31,8 @@ Before you can create a new endpoint with Front Door manager, you must have an A
     :::image type="content" source="./media/how-to-configure-endpoints/create-endpoint-page.png" alt-text="Screenshot of add an endpoint page.":::
 
 
-    * **Name** - Enter a unique name for the new Front Door endpoint. Azure Front Door generates a unique endpoint hostname based on the endpoint name in the form of `<endpointname>-hash.z01.azurefd.net`.
-    * **Endpoint hostname** - A deterministic DNS (domain name system) name that helps prevent subdomain takeover. This name is used to access your resources through your Azure Front Door at the domain `<endpointname>-hash.z01.azurefd.net`.
+    * **Name** - Enter a unique name for the new Front Door endpoint. Azure Front Door generates a unique endpoint hostname based on the endpoint name in the form of `<endpointname>-*.z01.azurefd.net`.
+    * **Endpoint hostname** - A deterministic DNS (domain name system) name that helps prevent subdomain takeover. This name is used to access your resources through your Azure Front Door at the domain `<endpointname>-*.z01.azurefd.net`.
     * **Status** - Set as checked to enable this endpoint.
 
 ### Add a route