Merge branch 'master' of https://github.com/MicrosoftDocs/azure-docs-pr into 1678688-adding-zone-pivots-bing-image-search

Author: john-par

.openpublishing.publish.config.json

@@ -346,6 +346,26 @@
       "url": "https://github.com/Azure-Samples/azure-sdk-for-go-samples",
       "branch": "master"
     },
+    {
+      "path_to_root": "azure-sdk-for-java-event-hubs",
+      "url": "https://github.com/Azure/azure-sdk-for-java/",
+      "branch": "master"
+    },
+    {
+      "path_to_root": "azure-sdk-for-java-script-event-hubs",
+      "url": "https://github.com/Azure/azure-sdk-for-js/",
+      "branch": "master"
+    },        
+    {
+      "path_to_root": "azure-sdk-for-net-event-hubs",
+      "url": "https://github.com/Azure/azure-sdk-for-net/",
+      "branch": "master"
+    },
+    {
+      "path_to_root": "azure-sdk-for-python-event-hubs",
+      "url": "https://github.com/Azure/azure-sdk-for-python/",
+      "branch": "master"
+    },      
     {
       "path_to_root": "cosmos-dotnet-getting-started",
       "url": "https://github.com/Azure-Samples/cosmos-dotnet-getting-started",

articles/analysis-services/analysis-services-monitor.md

@@ -4,7 +4,7 @@ description: Learn how Analysis Services use Azure Metrics Explorer, a free tool
 author: minewiskan
 ms.service: azure-analysis-services
 ms.topic: conceptual
-ms.date: 10/30/2019
+ms.date: 03/04/2020
 ms.author: owend
 ms.reviewer: minewiskan
 
@@ -63,7 +63,7 @@ Use this table to determine which metrics are best for your monitoring scenario.
 |RowsWrittenPerSec|Processing: Rows written per sec|CountPerSecond|Average|Rate of rows written during processing.|
 |qpu_metric|QPU|Count|Average|QPU. Range 0-100 for S1, 0-200 for S2 and 0-400 for S4|
 |QueryPoolBusyThreads|Query Pool Busy Threads|Count|Average|Number of busy threads in the query thread pool.|
-|SuccessfullConnectionsPerSec|Successful Connections Per Sec|CountPerSecond|Average|Rate of successful connection completions.|
+|SuccessfulConnectionsPerSec|Successful Connections Per Sec|CountPerSecond|Average|Rate of successful connection completions.|
 |CommandPoolBusyThreads|Threads: Command pool busy threads|Count|Average|Number of busy threads in the command thread pool.|
 |CommandPoolIdleThreads|Threads: Command pool idle threads|Count|Average|Number of idle threads in the command thread pool.|
 |LongParsingBusyThreads|Threads: Long parsing busy threads|Count|Average|Number of busy threads in the long parsing thread pool.|

articles/automation/automation-tutorial-update-management.md

@@ -4,7 +4,7 @@ description: This article provides an overview of how to use Azure Automation Up
 services: automation
 ms.subservice: update-management
 ms.topic: tutorial
-ms.date: 01/21/2020
+ms.date: 03/04/2020
 ms.custom: mvc
 ---
 # Manage updates and patches for your Azure VMs
@@ -38,9 +38,9 @@ Sign in to the Azure portal at https://portal.azure.com.
 
 First, enable Update Management on your VM for this tutorial:
 
-1. In the [Azure portal](https://portal.azure.com) menu, select **Virtual machines** or search for and select **Virtual machines** from the **Home** page.
-1. Select the VM for which you want to enable Update Management.
-1. On the VM page, under **OPERATIONS**, select **Update management**. The **Enable Update Management** pane opens.
+1. In the [Azure portal](https://portal.azure.com), from the left-hand pane select **Virtual machines** or search for and select **Virtual machines** from the **Home** page.
+2. Select the VM for which you want to enable Update Management.
+3. On the VM page, under **Operations**, select **Update management**. The **Enable Update management** pane opens.
 
 Validation is performed to determine whether Update Management is enabled for this VM. This validation includes checks for a Log Analytics workspace and linked Automation account, and whether the Update Management solution is enabled in the workspace.
 
@@ -52,23 +52,23 @@ If any of the following prerequisites were found to be missing during onboarding
 
 * [Log Analytics](../azure-monitor/platform/data-platform-logs.md) workspace
 * An [Automation account](./automation-offering-get-started.md)
-* A [Hybrid Runbook Worker](./automation-hybrid-runbook-worker.md) (enabled on the VM)
+* A [Hybrid Runbook Worker](./automation-hybrid-runbook-worker.md) enabled on the VM
 
-Under **Update Management**, set the location, Log Analytics workspace, and Automation account to use. Then, select **Enable**. If these options aren't available, it means that another automation solution is enabled for the VM. In that case, the same workspace and Automation account must be used.
+Under **Update management**, set the location, Log Analytics workspace, and Automation account to use. Then, select **Enable**. If these options aren't available, it means that another Automation solution is enabled for the VM. In that case, the same workspace and Automation account must be used.
 
 ![Enable the Update Management solution window](./media/automation-tutorial-update-management/manageupdates-update-enable.png)
 
-Enabling the solution can take up to a few minutes. During this time, don't close the browser window. After the solution is enabled, information about missing updates on the VM flows to Azure Monitor logs. It can take between 30 minutes and 6 hours for the data to be available for analysis.
+Enabling the solution can take several minutes. During this time, don't close the browser window. After the solution is enabled, information about missing updates on the VM flows to Azure Monitor logs. It can take between 30 minutes and 6 hours for the data to be available for analysis.
 
 ## View update assessment
 
 After Update Management is enabled, the **Update management** pane opens. If any updates are identified as missing, a list of missing updates is shown on the **Missing updates** tab.
 
-Under **INFORMATION LINK**, select the update link to open the support article for the update. You can learn important information about the update.
+Under **Information link**, select the update link to open the support article for the update. You can learn important information about the update.
 
 ![View update status](./media/automation-tutorial-update-management/manageupdates-view-status-win.png)
 
-Click anywhere else on the update to open the **Log Search** pane for the selected update. The query for the log search is predefined for that specific update. You can modify this query or create your own query to view detailed information about the updates that are deployed or missing in your environment.
+Click anywhere else on the update to open the **Log search** pane for the selected update. The query for the log search is predefined for that specific update. You can modify this query or create your own query to view detailed information about the updates that are deployed or missing in your environment.
 
 ![View update status](./media/automation-tutorial-update-management/logsearch.png)
 
@@ -105,15 +105,15 @@ Under **Action groups**, select **Create New**. An action group is a group of ac
 
 In the **Action group name** box, enter a name for the alert and a short name. The short name is used in place of a full action group name when notifications are sent by using this group.
 
-Under **Actions**, enter a name for the action, like **Email Notifications**. Under **ACTION TYPE**, select **Email/SMS/Push/Voice**. Under **DETAILS**, select **Edit details**.
+Under **Actions**, enter a name for the action, like **Email notifications**. Under **Action type**, select **Email/SMS/Push/Voice**. Under **Details**, select **Edit details**.
 
 In the **Email/SMS/Push/Voice** pane, enter a name. Select the **Email** check box, and then enter a valid email address.
 
 ![Configure an email action group](./media/automation-tutorial-update-management/configure-email-action-group.png)
 
-In the **Email/SMS/Push/Voice** pane, select **OK**. In the **Add action group** pane, select **OK**.
+In the **Email/SMS/Push/Voice** pane, select **Ok**. In the **Add action group** pane, select **Ok**.
 
-To customize the subject of the alert email,  under **Create rule**, under **Customize Actions**, select **Email subject**. When you're finished, select **Create alert rule**. The alert tells you when an update deployment succeeds, and which machines were part of that update deployment run.
+To customize the subject of the alert email,  under **Create rule**, under **Customize actions**, select **Email subject**. When you're finished, select **Create alert rule**. The alert tells you when an update deployment succeeds, and which machines were part of that update deployment run.
 
 ## Schedule an update deployment
 
@@ -133,7 +133,7 @@ Under **New update deployment**, specify the following information:
 
 * **Groups to update (preview)**: Define a query based on a combination of subscription, resource groups, locations, and tags to build a dynamic group of Azure VMs to include in your deployment. To learn more, see [Dynamic Groups](automation-update-management-groups.md)
 
-* **Machines to update**: Select a Saved search, Imported group, or pick Machine from the drop-down and select individual machines. If you choose **Machines**, the readiness of the machine is shown in the **UPDATE AGENT READINESS** column. To learn about the different methods of creating computer groups in Azure Monitor logs, see [Computer groups in Azure Monitor logs](../azure-monitor/platform/computer-groups.md)
+* **Machines to update**: Select a Saved search, Imported group, or pick Machine from the drop-down and select individual machines. If you choose **Machines**, the readiness of the machine is shown in the **Update agent readiness** column. To learn about the different methods of creating computer groups in Azure Monitor logs, see [Computer groups in Azure Monitor logs](../azure-monitor/platform/computer-groups.md)
 
 * **Update classification**: Select the supported update classifications available for each product that can be included in the update deployment. For this tutorial, leave all types selected.
 
@@ -157,7 +157,7 @@ Under **New update deployment**, specify the following information:
 
 * **Schedule settings**: The **Schedule Settings** pane opens. The default start time is 30 minutes after the current time. You can set the start time to any time from 10 minutes in the future.
 
-   You can also specify whether the deployment occurs once, or set up a recurring schedule. Under **Recurrence**, select **Once**. Leave the default as 1 day and select **OK**. This sets up a recurring schedule.
+   You can also specify whether the deployment occurs once, or set up a recurring schedule. Under **Recurrence**, select **Once**. Leave the default as 1 day and select **Ok**. This sets up a recurring schedule.
 
 * **Pre-scripts + Post-scripts**: Select the scripts to run before and after your deployment. To learn more, see [Manage Pre and Post scripts](pre-post-scripts.md).
 

articles/automation/media/automation-tutorial-update-management/manageupdates-update-enable.png

@@ -16,7 +16,7 @@ The Azure Functions runtime provides flexibility in hosting where and how you wa
 
 The Azure Functions service is made up of two key components: a runtime and a scale controller.  The Functions runtime runs and executes your code.  The runtime includes logic on how to trigger, log, and manage function executions.  The Azure Functions runtime can run *anywhere*.  The other component is a scale controller.  The scale controller monitors the rate of events that are targeting your function, and proactively scales the number of instances running your app.  To learn more, see [Azure Functions scale and hosting](functions-scale.md).
 
-Kubernetes-based Functions provides the Functions runtime in a [Docker container](functions-create-function-linux-custom-image.md) with event-driven scaling through KEDA.  KEDA can scale down to 0 instances (when no events are occurring) and up to *n* instances. It does this by exposing custom metrics for the Kubernetes autoscaler (Horizontal Pod Autoscaler).  Using Functions containers with KEDA makes it possible to replicate serverless function capabilities in any Kubernetes cluster.  These functions can also be deployed using [Azure Kubernetes Services (AKS) virtual nodes](../aks/virtual-nodes-cli.md) feature for serverless infrastructure.
+Kubernetes-based Functions provides the Functions runtime in a [Docker container](functions-create-function-linux-custom-image.md) with event-driven scaling through KEDA.  KEDA can scale in to 0 instances (when no events are occurring) and out to *n* instances. It does this by exposing custom metrics for the Kubernetes autoscaler (Horizontal Pod Autoscaler).  Using Functions containers with KEDA makes it possible to replicate serverless function capabilities in any Kubernetes cluster.  These functions can also be deployed using [Azure Kubernetes Services (AKS) virtual nodes](../aks/virtual-nodes-cli.md) feature for serverless infrastructure.
 
 ## Managing KEDA and functions in Kubernetes
 
@@ -37,7 +37,7 @@ func init --docker-only
 To build an image and deploy your functions to Kubernetes, run the following command:
 
 > [!NOTE]
-> The core tools will leverage the docker CLI to build and publish the image. Be sure to have docker installed already and connected to your account with `docker login`.
+> The Core Tools will leverage the docker CLI to build and publish the image. Be sure to have docker installed already and connected to your account with `docker login`.
 
 ```cli
 func kubernetes deploy --name <name-of-function-deployment> --registry <container-registry-username>

articles/azure-functions/functions-kubernetes-keda.md

@@ -97,7 +97,7 @@ This section provides details about the supported Linux distributions.
 Starting with versions released after August 2018, we are making the following changes to our support model:  
 
 * Only the server versions are supported, not client.  
-* New versions of [Azure Linux Endorsed distros](../../virtual-machines/linux/endorsed-distros.md) are always supported.  
+* Focus support on any of the [Azure Linux Endorsed distros](../../virtual-machines/linux/endorsed-distros.md). Note that there may be some delay between a new distro/version being Azure Linux Endorsed and it being supported for the Log Analytics Linux agent.
 * All minor releases are supported for each major version listed.
 * Versions that have passed their manufacturer's end-of-support date are not supported.  
 * New versions of AMI are not supported.  

articles/azure-monitor/platform/log-analytics-agent.md

@@ -7,7 +7,7 @@ manager: craigg
 ms.service: sql-data-warehouse
 ms.topic: conceptual
 ms.subservice: manage
-ms.date: 10/21/2019
+ms.date: 03/04/2020
 ms.author: anjangsh
 ms.reviewer: igorstan
 ms.custom: seo-lt-2019"
@@ -53,7 +53,7 @@ The following lists details for restore point retention periods:
 2. Snapshots are not taken when a SQL pool is paused.
 3. The age of a restore point is measured by the absolute calendar days from the time the restore point is taken including when the SQL pool is paused.
 4. At any point in time, a SQL pool is guaranteed to be able to store up to 42 user-defined restore points and 42 automatic restore points as long as these restore points have not reached the 7-day retention period
-5. If a snapshot is taken, the SQL pool is then paused for greater than 7 days, and then resumes, it is possible for restore point to persist until there are 42 total restore points (including both user-defined and automatic)
+5. If a snapshot is taken, the SQL pool is then paused for greater than 7 days, and then resumes, the restore point will persist until there are 42 total restore points (including both user-defined and automatic)
 
 ### Snapshot retention when a SQL pool is dropped
 

articles/sql-data-warehouse/backup-and-restore.md

@@ -7,7 +7,7 @@ manager: craigg
 ms.service: sql-data-warehouse
 ms.topic: conceptual
 ms.subservice: load-data
-ms.date: 02/04/2020
+ms.date: 03/04/2020
 ms.author: kevin
 ms.reviewer: igorstan
 ms.custom: azure-synapse
@@ -42,6 +42,8 @@ To access your Data Lake Storage account, you will need to create a Database Mas
 
 To connect to Data Lake Storage using service principals, you must **first** create an Azure Active Directory Application, create an access key, and grant the application access to the Data Lake Storage account. For instructions, see [Authenticate to Azure Data Lake Storage Using Active Directory](../data-lake-store/data-lake-store-authenticate-using-active-directory.md).
 
+Log into your SQL pool with a user having CONTROL level permissions and execute the following SQL statements against your database:
+
 ```sql
 -- A: Create a Database Master Key.
 -- Only necessary if one does not already exist.

articles/sql-data-warehouse/sql-data-warehouse-load-from-azure-data-lake-store.md

@@ -10,7 +10,7 @@ ms.topic: conceptual
 author: dimitri-furman
 ms.author: dfurman
 ms.reviewer:
-ms.date: 10/12/2019
+ms.date: 03/03/2020
 ---
 # Azure SQL Database Hyperscale FAQ
 
@@ -268,7 +268,7 @@ No. Backups are managed by the storage subsystem, and leverage storage snapshots
 
 ### Can I perform geo-restore with a Hyperscale database
 
-Yes.  Geo-restore is fully supported. Unlike point-in-time restore, geo-restore may require a long running size-of-data operation.
+Yes. Geo-restore is fully supported. Unlike point-in-time restore, geo-restore requires a size-of-data operation. Data files are copied in parallel, so the duration of this operation depends primarily on the size of the largest file in the database, rather than on total database size. Geo-restore time will be significantly shorter if the database is restored in the Azure region that is [paired](https://docs.microsoft.com/azure/best-practices-availability-paired-regions) with the region of the source database.
 
 ### Can I set up geo-replication with Hyperscale database
 

articles/sql-database/sql-database-service-tier-hyperscale-faq.md

@@ -726,6 +726,10 @@
       href: ../../site-recovery/azure-to-azure-tutorial-migrate.md?toc=/azure/virtual-machines/linux/toc.json&bc=/azure/virtual-machines/linux/breadcrumb/toc.json
     - name: Move to an availability zone
       href: ../../site-recovery/move-azure-vms-avset-azone.md?toc=/azure/virtual-machines/linux/toc.json&bc=/azure/virtual-machines/linux/breadcrumb/toc.json
+    - name: Move Maintenance Control configurations to another region
+      href: ../move-region-maintenance-configuration.md?toc=/azure/virtual-machines/linux/toc.json&bc=/azure/virtual-machines/linux/breadcrumb/toc.json
+    - name: Move Maintenance Control configuration resources to another region
+      href: ../move-region-maintenance-configuration-resources.md?toc=/azure/virtual-machines/linux/toc.json&bc=/azure/virtual-machines/linux/breadcrumb/toc.json
     - name: Migrate AWS and on-premises VMs
       href: ../windows/on-prem-to-azure.md?toc=/azure/virtual-machines/linux/toc.json&bc=/azure/virtual-machines/linux/breadcrumb/toc.json
       items: