Merge pull request #222423 from MicrosoftDocs/main

12/26/2022 PM Publish

Author: Taojunshen

articles/azure-arc/servers/index.yml

@@ -70,7 +70,7 @@ landingContent:
           - text: Azure PowerShell
             url: /powershell/module/az.connectedmachine/
           - text: .NET
-            url: /dotnet/api/overview/azure/hybridcompute/management
+            url: /dotnet/api/overview/azure/hybridcompute/management/management-hybridcompute
           - text: REST
             url: /rest/api/hybridcompute/
           - text: Java

articles/azure-arc/servers/onboard-group-policy-powershell.md

@@ -27,7 +27,7 @@ The Group Policy Object, which is used to onboard Azure Arc-enabled servers, req
     * Assign the Azure Connected Machine Onboarding role to your service principal and limit the scope of the role to the target Azure landing zone.
     * Make a note of the Service Principal Secret; you'll need this value later.
 
-1. Download and unzip the folder **ArcEnabledServersGroupPolicy_v1.0.1** from [https://aka.ms/gp-onboard](https://aka.ms/gp-onboard). This folder contains the ArcGPO project structure with the scripts `EnableAzureArc.ps1`, `DeployGPO.ps1`, and `AzureArcDeployment.psm1`. These assets will be used for onboarding the machine to Azure Arc-enabled servers.
+1. Download and unzip the folder **ArcEnabledServersGroupPolicy_v1.0.1** from [https://github.com/Azure/ArcEnabledServersGroupPolicy/releases/download/1.0.2/ArcEnabledServersGroupPolicy_v1.0.2.zip](https://github.com/Azure/ArcEnabledServersGroupPolicy/releases/download/1.0.2/ArcEnabledServersGroupPolicy_v1.0.2.zip). This folder contains the ArcGPO project structure with the scripts `EnableAzureArc.ps1`, `DeployGPO.ps1`, and `AzureArcDeployment.psm1`. These assets will be used for onboarding the machine to Azure Arc-enabled servers.
 
 1. Download the latest version of the [Azure Connected Machine agent Windows Installer package](https://aka.ms/AzureConnectedMachineAgent) from the Microsoft Download Center and save it to the remote share.
 

articles/virtual-network/deploy-container-networking-docker-linux.md

@@ -164,6 +164,18 @@ Repeat steps 1 through 13 to add as many configurations as containers you wish t
 
 The Docker container engine must be installed and configured on the virtual machine you created previously.
 
+Sign-in to the virtual machine you created previously with the Azure Bastion host you deployed with the virtual network.
+
+1. In the search box at the top of the portal, enter **Virtual machine**. Select **Virtual machines** in the search results.
+
+2. Select **myVM**.
+
+3. In the **Overview** of **myVM**, select **Connect** then **Bastion**.
+
+4. Enter the username and password you created when you deployed the virtual machine in the previous steps.
+
+5. Select **Connect**.
+
 For install instructions for Docker on an Ubuntu container host, see [Install Docker Engine on Ubuntu](https://docs.docker.com/engine/install/ubuntu/).
 
 After Docker is installed on the virtual machine, follow the instructions for the Linux post install. For instructions on the Linux post install, see [Docker Engine post-installation steps](https://docs.docker.com/engine/install/linux-postinstall/).
@@ -201,8 +213,7 @@ For more information about the Azure CNI plugin, see [Microsoft Azure Container
 8. Configure permissions and install the CNI plugin. The install script command requires a version number for the CNI plugin. At the time of the writing of this article, the newest version is **`v1.4.39`**. To obtain the latest version number of the plugin or previous versions, see [Releases](https://github.com/Azure/azure-container-networking/releases).
 
     ```bash
-    cd azure-container-networking
-    cd scripts
+    cd ./azure-container-networking/scripts
     chmod u+x install-cni-plugin.sh
     sudo ./install-cni-plugin.sh v1.4.39
     chmod u+x docker-run.sh