Merge pull request #222782 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: huypub

articles/active-directory/hybrid/how-to-connect-staged-rollout.md

@@ -171,6 +171,7 @@ You can roll out these options:
 - **Pass-through authentication** + **Seamless SSO**
 - **Not supported** - **Password hash sync** + **Pass-through authentication** + **Seamless SSO**
 - **Certificate-based authentication settings**
+- **Azure multifactor authentication**
 
 To configure Staged Rollout, follow these steps:
 

articles/aks/azure-csi-blob-storage-static.md

@@ -114,7 +114,7 @@ The following example demonstrates how to mount a Blob storage container as a pe
     kubectl create -f pv-blob-nfs.yaml
     ```
 
-3. Create a `pvc-blob-nfs.yaml` file with a *PersistentVolume*. For example:
+3. Create a `pvc-blob-nfs.yaml` file with a *PersistentVolumeClaim*. For example:
 
     ```yml
     kind: PersistentVolumeClaim

articles/iot-develop/quickstart-devkit-mxchip-az3166-iot-hub.md

@@ -204,7 +204,7 @@ To connect the MXCHIP DevKit to Azure, you'll modify a configuration file for Wi
     |Constant name|Value|
     |-------------|-----|
     |`IOT_HUB_HOSTNAME` |{*Your Iot hub hostName value*}|
-    |`IOT_DPS_REGISTRATION_ID` |{*Your Device ID value*}|
+    |`IOT_HUB_DEVICE_ID` |{*Your Device ID value*}|
     |`IOT_DEVICE_SAS_KEY` |{*Your Primary key value*}|
 
 1. Save and close the file.

articles/virtual-wan/virtual-wan-global-transit-network-architecture.md

@@ -112,9 +112,9 @@ The Remote User-to-branch path lets remote users who are using a point-to-site c
 The VNet-to-VNet transit enables VNets to connect to each other in order to interconnect multi-tier applications that are implemented across multiple VNets. Optionally, you can connect VNets to each other through VNet Peering and this may be suitable for some scenarios where transit via the VWAN hub isn't necessary.
 
 
-## <a name="DefaultRoute"></a>Force tunneling and default route
+## <a name="DefaultRoute"></a>Forced tunneling and default route
 
-Force Tunneling can be enabled by configuring the enable default route on a VPN, ExpressRoute, or Virtual Network connection in Virtual WAN.
+Forced Tunneling can be enabled by configuring the enable default route on a VPN, ExpressRoute, or Virtual Network connection in Virtual WAN.
 
 A virtual hub propagates a learned default route to a virtual network/site-to-site VPN/ExpressRoute connection if enable default flag is 'Enabled' on the connection. 
 

includes/vpn-gateway-virtual-wan-vpn-profile-intune.md

@@ -52,7 +52,7 @@ For other supported options, see the [VPNv2 CSP](/windows/client-management/mdm/
 1. Modify the entry between ```<ServerUrlList>``` and ```</ServerUrlList>``` with the entry from your downloaded profile (azurevpnconfig.xml). Change the "TrustedNetworkDetection" FQDN to fit your environment.
 1. Open the Azure downloaded profile (azurevpnconfig.xml) and copy the entire contents to the clipboard by highlighting the text and pressing (ctrl) + C. 
 1. Paste the copied text from the previous step into the file you created in step 2 between the ```<CustomConfiguration>  </CustomConfiguration>``` tags. Save the file with an xml extension.
-1. Write down the value in the ```<name>  </name>``` tags. This is the name of the profile. You will need this name when you create the profile in Intune. Close the file and remember the location where it is saved.
+1. Write down the value in the ```<name>  </name>``` tags. This is the name of the profile. You can also modify this value to something more meaningful, as it will be visible to the end users. You will need this name when you create the profile in Intune. Close the file and remember the location where it is saved.
 
 ## Create Intune profile