Merge pull request #104122 from MGoedtel/UpdateArcSvr212

updated article, names, TOC, redirect

Author: GitHubber17

.openpublishing.redirection.json

@@ -450,6 +450,16 @@
       "redirect_url": "https://docs.microsoft.com/previous-versions/azure/batch-ai/overview-what-happened-batch-ai",
       "redirect_document_id": true
     },
+    {
+      "source_path": "articles/azure-arc/servers/quickstart-onboard-portal.md",
+      "redirect_url": "/azure/azure-arc/servers/onboard-portal",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/azure-arc/servers/quickstart-onboard-powershell.md",
+      "redirect_url": "/azure/azure-arc/servers/onboard-service-principal",
+      "redirect_document_id": false
+    },
     {
       "source_path": "articles/batch-ai/quickstart-create-cluster-cli.md",
       "redirect_url": "https://docs.microsoft.com/previous-versions/azure/batch-ai/quickstart-create-cluster-cli",

articles/azure-arc/servers/media/quickstart-onboard/apps-and-features.png renamed to articles/azure-arc/servers/media/onboard-portal/apps-and-features.png

@@ -6,9 +6,8 @@ ms.service: azure-arc
 ms.subservice: azure-arc-servers
 author: mgoedtel
 ms.author: magoedte
-ms.date: 02/09/2020
-ms.custom: mvc
-ms.topic: quickstart
+ms.date: 02/12/2020
+ms.topic: conceptual
 ---
 
 # Connect hybrid machines to Azure from the Azure portal
@@ -39,6 +38,7 @@ The script to automate the download and installation, and to establish the conne
     >- WestEurope
     >- WestAsia
     >
+    >Review additional considerations when selecting a region [here](overview.md#supported-regions) in the Overview article.
 
 1. On the **Generate script** page, in the **Operating system** drop-down list, select the operating system that the script will be running on.
 
@@ -141,7 +141,7 @@ After you install the agent, configure it to communicate with the Azure Arc serv
 
 After you install the agent and configure it to connect to Azure Arc for servers (preview), go to the Azure portal to verify that the server has been successfully connected. View your machines in the [Azure portal](https://aka.ms/hybridmachineportal).
 
-![A successful server connection](./media/quickstart-onboard/arc-for-servers-successful-onboard.png)
+![A successful server connection](./media/onboard-portal/arc-for-servers-successful-onboard.png)
 
 ## Clean up
 
@@ -160,7 +160,7 @@ To disconnect a machine from Azure Arc for servers (preview), do the following:
     >[!NOTE]
     > You can also run the agent setup wizard by double-clicking the **AzureConnectedMachineAgent.msi** installer package.
 
-    If you want to script the uninstallation, you can use the following example, which retrieves the product code and uninstalls the agent by using the Msiexec.exe command line - `msiexec /x {Product Code}`. To do so:  
+    If you want to script removal of the agent, you can use the following example, which retrieves the product code and uninstalls the agent by using the Msiexec.exe command line - `msiexec /x {Product Code}`. To do so:  
 
     a. Open the Registry Editor.  
     b. Under registry key `HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Uninstall`, look for and copy the product code GUID.  

articles/azure-arc/servers/media/quickstart-onboard/arc-for-servers-successful-onboard.png renamed to articles/azure-arc/servers/media/onboard-portal/arc-for-servers-successful-onboard.png

@@ -7,12 +7,11 @@ ms.subservice: azure-arc-servers
 author: mgoedtel
 ms.author: magoedte
 ms.date: 02/04/2020
-ms.custom: mvc
-ms.topic: quickstart
+ms.topic: conceptual
 ---
 # Connect hybrid machines to Azure at scale
 
-You can enable Azure Arc for servers (preview) for multiple Windows or Linux machines in your environment with several flexible options depending on your requirements. Using the template script we provide, you can automate every step of the installation, including establishing the connection to Azure Arc. However, you are required to interactively execute this script with an account that has elevated permissions on the target machine and in Azure. To connect the machines to Azure Arc for servers, you can use an Azure Active Directory [service principal](../../active-directory/develop/app-objects-and-service-principals.md) instead of using your privileged identity to [interactively connect the machine](quickstart-onboard-portal.md). A service principal is a special limited management identity that is granted only the minimum permission necessary to connect machines to Azure using the `azcmagent` command. This is safer than using a higher privileged account like a Tenant Administrator, and follows our access control security best practices. The service principal is used only during onboarding, it is not used for any other purpose.  
+You can enable Azure Arc for servers (preview) for multiple Windows or Linux machines in your environment with several flexible options depending on your requirements. Using the template script we provide, you can automate every step of the installation, including establishing the connection to Azure Arc. However, you are required to interactively execute this script with an account that has elevated permissions on the target machine and in Azure. To connect the machines to Azure Arc for servers, you can use an Azure Active Directory [service principal](../../active-directory/develop/app-objects-and-service-principals.md) instead of using your privileged identity to [interactively connect the machine](onboard-portal.md). A service principal is a special limited management identity that is granted only the minimum permission necessary to connect machines to Azure using the `azcmagent` command. This is safer than using a higher privileged account like a Tenant Administrator, and follows our access control security best practices. The service principal is used only during onboarding, it is not used for any other purpose.  
 
 The installation methods to install and configure the Connected Machine agent requires that the automated method you use has  administrator permissions on the machines. On Linux, by using the root account and on Windows, as a member of the Local Administrators group.
 
@@ -71,7 +70,7 @@ The **Azure Connected Machine Onboarding** role contains only the permissions re
 
 ## Install the agent and connect to Azure
 
-The following steps install and configure the Connected Machine agent on your hybrid machines by using the script template, which performs similar steps described in the [Connect hybrid machines to Azure from the Azure portal](quickstart-onboard-portal.md) article. The difference is in the final step where you establish the connection to Azure Arc using the `azcmagent` command using the service principal. 
+The following steps install and configure the Connected Machine agent on your hybrid machines by using the script template, which performs similar steps described in the [Connect hybrid machines to Azure from the Azure portal](onboard-portal.md) article. The difference is in the final step where you establish the connection to Azure Arc using the `azcmagent` command using the service principal. 
 
 The following are the settings that you configure the `azcmagent` command to use for the service principal.
 
@@ -89,7 +88,8 @@ The following is an example of the Connected Machine agent for Windows installat
 
 ```
  # Download the package
-Invoke-WebRequest -Uri https://aka.ms/AzureConnectedMachineAgent -OutFile AzureConnectedMachineAgent.msi
+function download() {$ProgressPreference="SilentlyContinue"; Invoke-WebRequest -Uri https://aka.ms/AzureConnectedMachineAgent -OutFile AzureConnectedMachineAgent.msi}
+download
 
 # Install the package
 msiexec /i AzureConnectedMachineAgent.msi /l*v installationlog.txt /qn | Out-String
@@ -127,7 +127,7 @@ azcmagent connect \
 
 After you install the agent and configure it to connect to Azure Arc for servers (preview), go to the Azure portal to verify that the server has been successfully connected. View your machines in the [Azure portal](https://aka.ms/hybridmachineportal).
 
-![A successful server connection](./media/quickstart-onboard/arc-for-servers-successful-onboard.png)
+![A successful server connection](./media/onboard-portal/arc-for-servers-successful-onboard.png)
 
 ## Next steps
 

articles/azure-arc/servers/quickstart-onboard-portal.md renamed to articles/azure-arc/servers/onboard-portal.md

@@ -7,8 +7,7 @@ ms.subservice: azure-arc-servers
 author: mgoedtel
 ms.author: magoedte
 keywords: azure automation, DSC, powershell, desired state configuration, update management, change tracking, inventory, runbooks, python, graphical, hybrid
-ms.date: 02/03/2020
-ms.custom: mvc
+ms.date: 02/12/2020
 ms.topic: overview
 ---
 
@@ -37,6 +36,8 @@ With Azure Arc for servers (preview), only certain regions are supported:
 - WestEurope
 - WestAsia
 
+In most cases, the location you select when you create the installation script should be the Azure region geographically closest to your machine's location. Data at rest will be stored within the Azure geography containing the region you specify, which may also affect your choice of region if you have data residency requirements. If the Azure region your machine is connected to is affected by an outage, the connected machine is not affected, but management operations using Azure may be unable to complete. For resilience in the event of a regional outage, if you have multiple locations which provide a geographically-redundant service, it is best to connect the machines in each location to a different Azure region.
+
 ## Prerequisites
 
 ### Supported operating systems
@@ -130,10 +131,10 @@ Connecting machines in your hybrid environment directly with Azure can be accomp
 
 | Method | Description |
 |--------|-------------|
-| Interactively | Manually install the agent on a single or small number of machines following the steps in [Connect machines from Azure portal](quickstart-onboard-portal.md).<br> From the Azure portal, you can generate a script and execute it on the machine to automate the install and configuration steps of the agent.|
-| At scale | Install and configure the agent for multiple machines following the [Connect machines using a Service Principal](quickstart-onboard-powershell.md).<br> This method creates a service principal to connect machines non-interactively.|
+| Interactively | Manually install the agent on a single or small number of machines following the steps in [Connect machines from Azure portal](onboard-portal.md).<br> From the Azure portal, you can generate a script and execute it on the machine to automate the install and configuration steps of the agent.|
+| At scale | Install and configure the agent for multiple machines following the [Connect machines using a Service Principal](onboard-service-principal.md).<br> This method creates a service principal to connect machines non-interactively.|
 
 
 ## Next steps
 
-- To begin evaluating Azure Arc for servers (preview), follow the article [Connect hybrid machines to Azure from the Azure portal](quickstart-onboard-portal.md). 
+- To begin evaluating Azure Arc for servers (preview), follow the article [Connect hybrid machines to Azure from the Azure portal](onboard-portal.md). 

articles/azure-arc/servers/quickstart-onboard-powershell.md renamed to articles/azure-arc/servers/onboard-service-principal.md

@@ -9,9 +9,9 @@
   expanded: true
   items:
   - name: Connect machines to Azure Arc from the Azure portal
-    href: ./servers/quickstart-onboard-portal.md
+    href: ./servers/onboard-portal.md
   - name: Connect machines at scale using a service principal
-    href: ./servers/quickstart-onboard-powershell.md
+    href: ./servers/onboard-service-principal.md
 - name: Reference
   items:
     - name: Azure Connected Machine Agent CLI interface