Merge pull request #97139 from MicrosoftDocs/repo_sync_working_branch

Confirm merge from repo_sync_working_branch to master to sync with https://github.com/Microsoft/azure-docs (branch master)

Author: huypub

articles/active-directory/devices/manage-stale-devices.md

@@ -88,7 +88,7 @@ If your device is under control of Intune or any other MDM solution, retire the
 
 ### System-managed devices
 
-Don't delete system-managed devices. These are generally devices such as auto-pilot. Once deleted, these devices can't be reprovisioned. The new `get-msoldevice` cmdlet excludes system-managed devices by default. 
+Don't delete system-managed devices. These are generally devices such as Autopilot. Once deleted, these devices can't be reprovisioned. The new `get-msoldevice` cmdlet excludes system-managed devices by default. 
 
 ### Hybrid Azure AD joined devices
 
@@ -124,7 +124,7 @@ Disable or delete Azure AD registered devices in the Azure AD.
 
 ## Clean up stale devices in the Azure portal  
 
-While you can cleanup stale devices in the Azure portal, it is more efficient, to handle this process using a PowerShell script. Use the latest PowerShell V1 module to use the timestamp filter and to filter out system-managed devices such as auto-pilot. At this point, using PowerShell V2 is not recommended.
+While you can cleanup stale devices in the Azure portal, it is more efficient, to handle this process using a PowerShell script. Use the latest PowerShell V1 module to use the timestamp filter and to filter out system-managed devices such as Autopilot. At this point, using PowerShell V2 is not recommended.
 
 A typical routine consists of the following steps:
 

articles/active-directory/hybrid/how-to-connect-password-hash-synchronization.md

@@ -155,7 +155,7 @@ The synchronization of a password has no impact on the Azure user who is signed
 
 ## Password hash sync process for Azure AD Domain Services
 
-If you use Azure AD Domain Services to provide legacy authentication for applications and services that need to use Keberos, LDAP, or NTLM, some additional processes are part of the password hash synchronization flow. Azure AD Connect uses the additional following process to synchronize password hashes to Azure AD for use in Azure AD Domain Services:
+If you use Azure AD Domain Services to provide legacy authentication for applications and services that need to use Kerberos, LDAP, or NTLM, some additional processes are part of the password hash synchronization flow. Azure AD Connect uses the additional following process to synchronize password hashes to Azure AD for use in Azure AD Domain Services:
 
 > [!IMPORTANT]
 > Azure AD Connect should only be installed and configured for synchronization with on-premises AD DS environments. It's not supported to install Azure AD Connect in an Azure AD DS managed domain to synchronize objects back to Azure AD.

articles/api-management/api-management-howto-add-products.md

@@ -53,7 +53,7 @@ In this tutorial, you learn how to:
     | Requires approval        | Check **Require approval** if you want an administrator to review and accept or reject subscription attempts to this product. If the box is unchecked, subscription attempts are auto-approved.                                                                                                                         |
     | Subscription count limit | To limit the count of multiple simultaneous subscriptions, enter the subscription limit.                                                                                                                                                                                                                                |
     | Legal terms              | You can include the terms of use for the product which subscribers must accept in order to use the product.                                                                                                                                                                                                             |
-    | APIs                     | Products are associations of one or more APIs. You can include a number of APIs and offer them to developers through the developer portal. <br/> You can add an existing API during the product creation. You can add an API to the product later, either from the Products **Settings** page or while creating an API. |
+    | APIs                     | Products are associations of one or more APIs. You can include a number of APIs and offer them to developers through the developer portal. <br/> You can add an existing API during the product creation. You can add an API to the product later, either from the Product's **Settings** page or while creating an API. |
 
 3. Click **Create** to create the new product.
 
@@ -63,7 +63,7 @@ You can continue configuring the product after saving it by choosing the **Setti
 
 View/add subscribers to the product from the **Subscriptions** tab.
 
-Set visibility of a product for developers or guest from the **Access control** tab.
+Set visibility of a product for developers or guests from the **Access control** tab.
 
 ## <a name="add-apis"> </a>Add APIs to a product
 

articles/azure-databricks/store-secrets-azure-key-vault.md

@@ -124,7 +124,7 @@ Sign in to the [Azure portal](https://portal.azure.com/).
 
 4. Once your Azure Databricks workspace is open in a separate window, append **#secrets/createScope** to the URL. The URL should have the following format: 
 
-   **https://<\location>.azuredatabricks.net/?o=<\id>#secrets/createScope**.
+   **https://<\location>.azuredatabricks.net/#secrets/createScope**.
 
 5. Enter a scope name, and enter the Azure Key Vault DNS name and Resource ID you saved earlier. Save the scope name in a text editor for use later in this tutorial. Then, select **Create**.
 

articles/azure-monitor/insights/solution-office-365.md

@@ -197,8 +197,6 @@ To enable the administrative account for the first time, you must provide admini
 
 The last step is to subscribe the application to your Log Analytics workspace. You also do this with a PowerShell script.
 
-The last step is to subscribe the application to your Log Analytics workspace. You also do this with a PowerShell script.
-
 1. Save the following script as *office365_subscription.ps1*.
 
     ```powershell
@@ -457,15 +455,17 @@ You can remove the Office 365 management solution using the process in [Remove a
     # Create Authentication Context tied to Azure AD Tenant
     $authContext = New-Object "Microsoft.IdentityModel.Clients.ActiveDirectory.AuthenticationContext" -ArgumentList $authority
     # Acquire token
-    $global:authResultARM = $authContext.AcquireToken($resourceAppIdURIARM, $clientId, $redirectUri, "Auto")
-    $authHeader = $global:authResultARM.CreateAuthorizationHeader()
+    $platformParameters = New-Object "Microsoft.IdentityModel.Clients.ActiveDirectory.PlatformParameters" -ArgumentList "Auto"
+    $global:authResultARM = $authContext.AcquireTokenAsync($resourceAppIdURIARM, $clientId, $redirectUri, $platformParameters)
+    $global:authResultARM.Wait()
+    $authHeader = $global:authResultARM.Result.CreateAuthorizationHeader()
     $authHeader
     }
     
     Function Office-UnSubscribe-Call{
     
     #----------------------------------------------------------------------------------------------------------------------------------------------
-    $authHeader = $global:authResultARM.CreateAuthorizationHeader()
+    $authHeader = $global:authResultARM.Result.CreateAuthorizationHeader()
     $ResourceName = "https://manage.office.com"
     $SubscriptionId   = $Subscription[0].Subscription.Id
     $OfficeAPIUrl = $ARMResource + 'subscriptions/' + $SubscriptionId + '/resourceGroups/' + $ResourceGroupName + '/providers/Microsoft.OperationalInsights/workspaces/' + $WorkspaceName + '/datasources/office365datasources_'  + $SubscriptionId + $OfficeTennantId + '?api-version=2015-11-01-preview'
@@ -503,6 +503,8 @@ You can remove the Office 365 management solution using the process in [Remove a
     .\office365_unsubscribe.ps1 -WorkspaceName MyWorkspace -ResourceGroupName MyResourceGroup -SubscriptionId '60b79d74-f4e4-4867-b631-yyyyyyyyyyyy' -OfficeTennantID 'ce4464f8-a172-4dcf-b675-xxxxxxxxxxxx'
     ```
 
+You will be prompted for credentials. Provide the credentials for your Log Analytics workspace.
+
 ## Data collection
 
 ### Supported agents

articles/cosmos-db/local-emulator.md

@@ -22,7 +22,7 @@ While emulation of the Azure Cosmos DB service is faithful, the emulator's imple
 
 You can migrate data between the Azure Cosmos Emulator and the Azure Cosmos DB service by using the [Azure Cosmos DB Data Migration Tool](https://github.com/azure/azure-documentdb-datamigrationtool).
 
-You can run Azure Cosmos Emulator on the Windows Docker container, see the [Docker Hub](https://hub.docker.com/r/microsoft/azure-cosmosdb-emulator/) for the docker pull command and [GitHub](https://github.com/Azure/azure-cosmos-db-emulator-docker) for the emulator source code.
+You can run Azure Cosmos Emulator on the Windows Docker container, see the [Docker Hub](https://hub.docker.com/r/microsoft/azure-cosmosdb-emulator/) for the docker pull command and [GitHub](https://github.com/Azure/azure-cosmos-db-emulator-docker) for the `Dockerfile` and more information.
 
 ## Differences between the emulator and the service
 

articles/data-explorer/ingest-data-event-hub.md

@@ -134,6 +134,8 @@ Now you connect to the event hub from Azure Data Explorer. When this connection
     > [!NOTE]
     > * Select **My data includes routing info** to use dynamic routing, where your data includes the necessary routing information as seen in the [sample app](https://github.com/Azure-Samples/event-hubs-dotnet-ingest) comments. If both static and dynamic properties are set, the dynamic properties override the static ones. 
     > * Only events enqueued after you create the data connection are ingested.
+    > * Enable GZip compression for static routing by opening a [support request in the Azure portal](https://ms.portal.azure.com/#blade/Microsoft_Azure_Support/HelpAndSupportBlade/overview). Enable GZip compression for dynamic routing as seen in the [sample app](https://github.com/Azure-Samples/event-hubs-dotnet-ingest). 
+    > * Avro format and event system properties aren't supported on compression payload.
 
 ## Copy the connection string
 

articles/hdinsight/hdinsight-component-versioning.md

@@ -68,9 +68,9 @@ The following table lists the versions of HDInsight that are available in the Az
 | HDInsight version | VM OS | Release date | Support expiration date | Retirement date | High availability |  Availability in the Azure portal |
 | --- | --- | --- | --- | --- | --- | --- |
 | HDInsight 4.0 |Ubuntu 16.0.4 LTS |September 24, 2018 | | |Yes |Yes |
-| HDInsight 3.6 |Ubuntu 16.0.4 LTS |April 4, 2017 | June 30, 2020 |December 31, 2020 |Yes |Yes |
+| HDInsight 3.6 |Ubuntu 16.0.4 LTS |April 4, 2017 | December 31, 2020 |December 31, 2020 |Yes |Yes |
 
-Spark 2.1, 2.2 & Kafka 1.0 support will expire on June 30th, 2020 and retirement on Dec 31st 2020.
+Spark 2.1, 2.2 & Kafka 1.0 support will expire on June 30th, 2020.
 
 > [!NOTE]  
 > After support for a version has expired, it might not be available through the Microsoft Azure portal. However, cluster versions continue to be available using the `Version` parameter in the Windows PowerShell [New-AzHDInsightCluster](https://docs.microsoft.com/powershell/module/az.hdinsight/new-azhdinsightcluster) command and the .NET SDK until the version retirement date.

articles/openshift/cluster-administration-cluster-admin-role.md

@@ -15,26 +15,26 @@ ms.date: 09/25/2019
 
 You're the cluster administrator of an Azure Red Hat OpenShift cluster. Your account has increased permissions and access to all user-created projects.
 
-When your account has the osa-customer-admin authorization role bound to it, it can automatically manage a project.
+When your account has the customer-admin-cluster authorization role bound to it, it can automatically manage a project.
 
 > [!Note] 
-> The osa-customer-admin cluster role is not the same as the cluster-admin cluster role.
+> The customer-admin-cluster cluster role is not the same as the cluster-admin cluster role.
 
 
 For example, you can execute actions associated with a set of verbs (`create`) to operate on a set of resource names (`templates`). To view the details of these roles and their sets of verbs and resources, run the following command:
 
-`$ oc describe clusterrole/osa-customer-admin`
+`$ oc get clusterroles customer-admin-cluster -o yaml`
 
 The verb names don't necessarily all map directly to `oc` commands. They equate more generally to the types of CLI operations that you can perform. 
 
 For example, having the `list` verb means that you can display a list of all objects of a resource name (`oc get`). The `get` verb means that you can display the details of a specific object if you know its name (`oc describe`).
 
 ## Configure the customer administrator role
 
-You can configure the customer administrator role only during cluster creation by providing the flag `--customer-admin-group-id`. To learn how to configure Azure Active Directory and the Administrators group, see [Azure Active Directory integration for Azure Red Hat OpenShift](howto-aad-app-configuration.md).
+You can configure the customer-admin-cluster cluster role only during cluster creation by providing the flag `--customer-admin-group-id`. To learn how to configure Azure Active Directory and the Administrators group, see [Azure Active Directory integration for Azure Red Hat OpenShift](howto-aad-app-configuration.md).
 
 ## Next steps
 
-Configure the osa-customer-admin role:
+Configure the customer-admin-cluster cluster role:
 > [!div class="nextstepaction"]
 > [Azure Active Directory integration for Azure Red Hat OpenShift](howto-aad-app-configuration.md)

articles/sql-data-warehouse/pause-and-resume-compute-powershell.md

@@ -14,7 +14,7 @@ ms.custom: seo-lt-2019
 ---
 # Quickstart: Pause and resume compute in Azure SQL Data Warehouse with Azure PowerShell
 
-Use PowerShell to pause compute in Azure SQL Data Warehouse to save costs. [Resume compute](sql-data-warehouse-manage-compute-overview.md) when you are ready to use the data warehouse.
+Use Azure PowerShell to pause compute in Azure SQL Data Warehouse to save costs. [Resume compute](sql-data-warehouse-manage-compute-overview.md) when you are ready to use the data warehouse.
 
 If you don't have an Azure subscription, create a [free](https://azure.microsoft.com/free/) account before you begin.