Merge branch 'master' of https://github.com/MicrosoftDocs/azure-docs-pr into rolyon-landing-data-lake-store

Author: rolyon

.openpublishing.redirection.json

@@ -3585,6 +3585,11 @@
       "redirect_url": "/azure/sql-database/troubleshoot-connectivity-issues-microsoft-azure-sql-database",
       "redirect_document_id": false
     },
+    {
+      "source_path": "articles/sql-database/sql-database-operate-query-store.md",
+      "redirect_url": "https://docs.microsoft.com/sql/relational-databases/performance/best-practice-with-the-query-store#Insight",
+      "redirect_document_id": false
+    },
     {
       "source_path": "articles/sql-database/sql-database-customer-implementations.md",
       "redirect_url": "http://customers.microsoft.com",
@@ -3680,6 +3685,11 @@
       "redirect_url": "/azure/sql-database/sql-database-performance-guidance",
       "redirect_document_id": false
     },
+    {
+      "source_path": "articles/sql-database/sql-database-performance.md",
+      "redirect_url": "/azure/sql-database/sql-database-monitor-overview",
+      "redirect_document_id": false
+    },
     {
       "source_path": "articles/sql-database/sql-database-managed-instance-vnet-configuration.md",
       "redirect_url": "/azure/sql-database/sql-database-managed-instance-configure-vnet-subnet",

articles/aks/private-clusters.md

@@ -7,93 +7,16 @@ ms.date: 2/21/2020
 
 ---
 
-# Create a private Azure Kubernetes Service cluster (preview)
+# Create a private Azure Kubernetes Service cluster
 
 In a private cluster, the control plane or API server has internal IP addresses that are defined in the [RFC1918 - Address Allocation for Private Internets](https://tools.ietf.org/html/rfc1918) document. By using a private cluster, you can ensure that network traffic between your API server and your node pools remains on the private network only.
 
 The control plane or API server is in an Azure Kubernetes Service (AKS)-managed Azure subscription. A customer's cluster or node pool is in the customer's subscription. The server and the cluster or node pool can communicate with each other through the [Azure Private Link service][private-link-service] in the API server virtual network and a private endpoint that's exposed in the subnet of the customer's AKS cluster.
 
-> [!IMPORTANT]
-> AKS preview features are self-service and are offered on an opt-in basis. Previews are provided *as is* and *as available* and are excluded from the service-level agreement (SLA) and limited warranty. AKS previews are partially covered by customer support on a *best effort* basis. Therefore, the features aren't meant for production use. For more information, see the following support articles:
->
-> * [AKS Support Policies](support-policies.md)
-> * [Azure Support FAQ](faq.md)
-
 ## Prerequisites
 
-* The Azure CLI version 2.0.77 or later, and the Azure CLI AKS Preview extension version 0.4.18
-
-## Currently supported regions
-
-* Australia East
-* Australia Southeast
-* Brazil South
-* Canada Central
-* Canada East
-* Cenral US
-* East Asia
-* East US
-* East US 2
-* East US 2 EUAP
-* France Central
-* Germany North
-* Japan East
-* Japan West
-* Korea Central
-* Korea South
-* North Central US
-* North Europe
-* North Europe
-* South Central US
-* UK South
-* West Europe
-* West US
-* West US 2
-* East US 2
-
-## Currently Supported Availability Zones
-
-* Central US
-* East US
-* East US 2
-* France Central
-* Japan East
-* North Europe
-* Southeast Asia
-* UK South
-* West Europe
-* West US 2
-
-## Install the latest Azure CLI AKS Preview extension
-
-To use private clusters, you need the Azure CLI AKS Preview extension version 0.4.18 or later. Install the Azure CLI AKS Preview extension by using the [az extension add][az-extension-add] command, and then check for any available updates by using the following [az extension update][az-extension-update] command:
-
-```azurecli-interactive
-# Install the aks-preview extension
-az extension add --name aks-preview
-
-# Update the extension to make sure you have the latest version installed
-az extension update --name aks-preview
-```
-> [!CAUTION]
-> When you register a feature on a subscription, you can't currently un-register that feature. After you enable some preview features, you can use default settings for all AKS clusters that were created in the subscription. Don't enable preview features on production subscriptions. Use a separate subscription to test preview features and gather feedback.
-
-```azurecli-interactive
-az feature register --name AKSPrivateLinkPreview --namespace Microsoft.ContainerService
-```
-
-It might take several minutes for the registration status to show as *Registered*. You can check on the status by using the following [az feature list][az-feature-list] command:
-
-```azurecli-interactive
-az feature list -o table --query "[?contains(name, 'Microsoft.ContainerService/AKSPrivateLinkPreview')].{Name:name,State:properties.state}"
-```
-
-When the state is registered, refresh the registration of the *Microsoft.ContainerService* resource provider by using the following [az provider register][az-provider-register] command:
+* The Azure CLI version 2.2.0 or later
 
-```azurecli-interactive
-az provider register --namespace Microsoft.ContainerService
-az provider register --namespace Microsoft.Network
-```
 ## Create a private AKS cluster
 
 ### Create a resource group
@@ -155,6 +78,7 @@ As mentioned, VNet peering is one way to access your private cluster. To use VNe
 9. Go to the virtual network where you have the VM, select **Peerings**, select the AKS virtual network, and then create the peering. If the address ranges on the AKS virtual network and the VM's virtual network clash, peering fails. For more information, see  [Virtual network peering][virtual-network-peering].
 
 ## Dependencies  
+
 * The Private Link service is supported on Standard Azure Load Balancer only. Basic Azure Load Balancer isn't supported.  
 * To use a custom DNS server, deploy an AD server with DNS to forward to this IP 168.63.129.16
 
@@ -169,7 +93,6 @@ As mentioned, VNet peering is one way to access your private cluster. To use VNe
 * No support for converting existing AKS clusters into private clusters
 * Deleting or modifying the private endpoint in the customer subnet will cause the cluster to stop functioning. 
 * Azure Monitor for containers Live Data isn't currently supported.
-* *Bring your own DNS* isn't currently supported.
 
 
 <!-- LINKS - internal -->

articles/analysis-services/analysis-services-qs-firewall.md

@@ -17,7 +17,8 @@ This quickstart helps you configure a firewall for your Azure Analysis Services
 
 - An Analysis Services server in your subscription. To learn more, see [Quickstart: Create a server - Portal](analysis-services-create-server.md) or [Quickstart: Create a server - PowerShell](analysis-services-create-powershell.md)
 - One or more IP address ranges for client computers (if needed).
-- Please Note that Import scenario from Power BI Premium is currently not supported.
+- Some scenarios where Power BI Premium connects to Azure Analysis Services, including data import (refresh) and paginated reports, are currently not supported even when Allow access from Power BI is enabled. The more common scenario of using Live Connect from Power BI Premium is supported. All Power BI Pro scenarios are supported.
+
 
 ## Sign in to the Azure portal 
 

articles/automation/shared-resources/variables.md

@@ -26,7 +26,7 @@ Since Automation variables are persisted, they are available even if the runbook
 
 When creating a variable, you can specify its encryption and storage by Azure Automation as a secure asset. Other secure assets include credentials, certificates, and connections. Azure Automation encrypts these assets and stores them using a unique key that is generated for each Automation account. The key is stored in a system-managed Key Vault. Before storing a secure asset, Azure Automation loads the key from the Key Vault and then uses it to encrypt the asset. 
 
-Azure Automation stores each encrypted variable securely. Its value can't be retrieved using the [Get-AzAutomationVariable](https://docs.microsoft.com/powershell/module/az.automation/get-azautomationvariable?view=azps-3.5.0) cmdlet that ships as part of the Azure PowerShell module. The only way to retrieve an encrypted value is by using the **Get-AutomationVariable** activity in a runbook or DSC configuration.
+Azure Automation stores each encrypted variable securely. Its value can't be retrieved using the [Get-AzAutomationVariable](https://docs.microsoft.com/powershell/module/az.automation/get-azautomationvariable?view=azps-3.5.0) cmdlet that ships as part of the Azure PowerShell module. The only way to retrieve an encrypted value is by using the `Get-AutomationVariable` activity in a runbook or DSC configuration.
 
 >[!NOTE]
 >This article has been updated to use the new Azure PowerShell Az module. You can still use the AzureRM module, which will continue to receive bug fixes until at least December 2020. To learn more about the new Az module and AzureRM compatibility, see [Introducing the new Azure PowerShell Az module](https://docs.microsoft.com/powershell/azure/new-azureps-module-az?view=azps-3.5.0). For Az module installation instructions on your Hybrid Runbook Worker, see [Install the Azure PowerShell Module](https://docs.microsoft.com/powershell/azure/install-az-ps?view=azps-3.5.0). For your Automation account, you can update your modules to the latest version using [How to update Azure PowerShell modules in Azure Automation](../automation-update-azure-modules.md).
@@ -41,7 +41,7 @@ When you create a variable with the Azure portal, you must specify a data type f
 * Boolean
 * Null
 
-The variable isn't restricted to the designated data type. You must set the variable using Windows PowerShell if you want to specify a value of a different type. If you indicate **Not defined**, the value of the variable is set to **null**, and you must set the value with the [Set-AzAutomationVariable](https://docs.microsoft.com/powershell/module/az.automation/set-azautomationvariable?view=azps-3.5.0) cmdlet or the **Set-AutomationVariable** activity.
+The variable isn't restricted to the designated data type. You must set the variable using Windows PowerShell if you want to specify a value of a different type. If you indicate **Not defined**, the value of the variable is set to Null, and you must set the value with the [Set-AzAutomationVariable](https://docs.microsoft.com/powershell/module/az.automation/set-azautomationvariable?view=azps-3.5.0) cmdlet or the `Set-AutomationVariable` activity.
 
 You can't use the portal to create or change the value for a complex variable type. However, you can provide a value of any type using Windows PowerShell. Complex types are retrieved as a [PSCustomObject](/dotnet/api/system.management.automation.pscustomobject).
 
@@ -60,31 +60,31 @@ For the Az module, the cmdlets in the following table are used to create and man
 
 ## Activities to access variables
 
-The activities in the following table are used to access variables in runbooks and DSC configurations. The difference between **Get-AzAutomationVariable** and **Get-AutomationVariable** is explained for encrypted variables at the start of this article.
+The activities in the following table are used to access variables in runbooks and DSC configurations. The difference between `Get-AzAutomationVariable` and `Get-AutomationVariable` is explained for encrypted variables at the start of this article.
 
 | Activity | Description |
 |:---|:---|
-|**Get-AutomationVariable**|Retrieves the value of an existing variable.|
-|**Set-AutomationVariable**|Sets the value for an existing variable.|
+|`Get-AutomationVariable`|Retrieves the value of an existing variable.|
+|`Set-AutomationVariable`|Sets the value for an existing variable.|
 
 > [!NOTE]
-> Avoid using variables in the *Name* parameter of **Get-AutomationVariable** in a runbook or DSC configuration. Use of this parameter can complicate the discovery of dependencies between runbooks or DSC configurations and Automation variables at design time.
+> Avoid using variables in the `Name` parameter of `Get-AutomationVariable` in a runbook or DSC configuration. Use of this parameter can complicate the discovery of dependencies between runbooks or DSC configurations and Automation variables at design time.
 
 The functions in the following table are used to access and retrieve variables in a Python2 runbook.
 
 |Python2 Functions|Description|
 |:---|:---|
-|automationassets.get_automation_variable|Retrieves the value of an existing variable. |
-|automationassets.set_automation_variable|Sets the value for an existing variable. |
+|`automationassets.get_automation_variable`|Retrieves the value of an existing variable. |
+|`automationassets.set_automation_variable`|Sets the value for an existing variable. |
 
 > [!NOTE]
-> You must import the **automationassets** module at the top of your Python runbook to access the asset functions.
+> You must import the `automationassets` module at the top of your Python runbook to access the asset functions.
 
 ## Creating a new Automation variable
 
 ### Create a new variable using the Azure portal
 
-1. From your Automation account, click the **Assets** tile and then on the **Assets** blade, select **Variables**.
+1. From your Automation account, click the **Assets** tile, then the **Assets** blade, and select **Variables**.
 2. On the **Variables** tile, select **Add a variable**.
 3. Complete the options on the **New Variable** blade and then click **Create** to save the new variable.
 
@@ -93,7 +93,7 @@ The functions in the following table are used to access and retrieve variables i
 
 ### Create a new variable with Windows PowerShell
 
-The script uses the **New-AzAutomationVariable** cmdlet to create a new variable and set its initial value. It can then retrieve the value using **Get-AzAutomationVariable**. If the value is a simple type, then that same type is retrieved. If it's a complex type, then a **PSCustomObject** type is retrieved.
+The script uses the `New-AzAutomationVariable` cmdlet to create a new variable and set its initial value. It can then retrieve the value using `Get-AzAutomationVariable`. If the value is a simple type, then that same type is retrieved. If it's a complex type, then a `PSCustomObject` type is retrieved.
 
 The following example shows how to create a variable of type String and then return its value.
 
@@ -119,17 +119,17 @@ $vmIpAddress = $vmValue.IpAddress
 
 ## Using a variable in a runbook or DSC configuration
 
-Use the **Set-AutomationVariable** activity to set the value of an Automation variable in a PowerShell runbook or DSC configuration, and the **Get-AutomationVariable** to retrieve it. You shouldn't use the **Set-AzAutomationVariable** and **Get-AzAutomationVariable** cmdlets or their AzureRM module equivalents in a runbook or DSC configuration, since they are less efficient than the workflow activities. 
+Use the `Set-AutomationVariable` activity to set the value of an Automation variable in a PowerShell runbook or DSC configuration, and the `Get-AutomationVariable` to retrieve it. You shouldn't use the `Set-AzAutomationVariable` and `Get-AzAutomationVariable` cmdlets or their AzureRM module equivalents in a runbook or DSC configuration, since they are less efficient than the workflow activities. 
 
-Note that you can't retrieve the value of a secure variable with **Get-AzAutomationVariable** or its AzureRM module equivalent. 
+Note that you can't retrieve the value of a secure variable with `Get-AzAutomationVariable` or its AzureRM module equivalent. 
 
-The only way to create a new variable from within a runbook or DSC configuration is to use the **New-AzAutomationVariable** cmdlet.
+The only way to create a new variable from within a runbook or DSC configuration is to use the `New-AzAutomationVariable` cmdlet.
 
 ### Textual runbook samples
 
 #### Set and retrieve a simple value from a variable
 
-The following sample commands show how to set and retrieve a variable in a textual runbook. This sample assumes the creation of integer variables named *NumberOfIterations* and *NumberOfRunnings* and a string variable named *SampleMessage*.
+The following sample commands show how to set and retrieve a variable in a textual runbook. This sample assumes the creation of integer variables named `NumberOfIterations` and `NumberOfRunnings` and a string variable named `SampleMessage`.
 
 ```powershell
 $NumberOfIterations = Get-AzAutomationVariable -ResourceGroupName "ResourceGroup01" –AutomationAccountName "MyAutomationAccount" -Name 'NumberOfIterations'
@@ -170,13 +170,13 @@ except AutomationAssetNotFound:
 
 ### Graphical runbook samples
 
-In a graphical runbook, you can add the **Get-AutomationVariable** or **Set-AutomationVariable** activity. Simply right-click the variable in the Library pane of the graphical editor and select the activity that you want.
+In a graphical runbook, you can add the `Get-AutomationVariable` or `Set-AutomationVariable` activity. Simply right-click the variable in the Library pane of the graphical editor and select the activity that you want.
 
 ![Add variable to canvas](../media/variables/runbook-variable-add-canvas.png)
 
 #### Set values in a variable
 
-The following image shows sample activities to update a variable with a simple value in a graphical runbook. In this sample, **Get-AzVM**  retrieves a single Azure virtual machine and saves the computer name to an existing Automation variable with a type of String. It doesn't matter whether the [link is a pipeline or sequence](../automation-graphical-authoring-intro.md#links-and-workflow) since the code only expects a single object in the output.
+The following image shows sample activities to update a variable with a simple value in a graphical runbook. In this sample, `Get-AzVM`  retrieves a single Azure virtual machine and saves the computer name to an existing Automation string variable. It doesn't matter whether the [link is a pipeline or sequence](../automation-graphical-authoring-intro.md#links-and-workflow) since the code only expects a single object in the output.
 
 ![Set simple variable](../media/variables/runbook-set-simple-variable.png)