Merge pull request #114083 from MicrosoftDocs/master

5/06 AM Publish

Author: huypub

.openpublishing.redirection.json

@@ -49084,6 +49084,51 @@
       "source_path": "articles/azure-cache-for-redis/cache-howto-manage-redis-cache-powershell.md",
       "redirect_url": "/azure/azure-cache-for-redis/cache-how-to-manage-redis-cache-powershell",
       "redirect_document_id": false
+    },
+        {
+      "source_path": "articles/marketplace/cloud-partner-portal/power-bi/cpp-prerequisites.md",
+      "redirect_url": "/azure/marketplace/partner-center-portal/create-power-bi-app-offer",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/marketplace/cloud-partner-portal/power-bi/cpp-create-offer.md",
+      "redirect_url": "/azure/marketplace/partner-center-portal/create-power-bi-app-offer",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/marketplace/cloud-partner-portal/power-bi/cpp-offer-settings-tab.md",
+      "redirect_url": "/azure/marketplace/partner-center-portal/create-power-bi-app-offer",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/marketplace/cloud-partner-portal/power-bi/cpp-technical-info-tab.md",
+      "redirect_url": "/azure/marketplace/partner-center-portal/create-power-bi-app-offer",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/marketplace/cloud-partner-portal/power-bi/cpp-storefront-details-tab.md",
+      "redirect_url": "/azure/marketplace/partner-center-portal/create-power-bi-app-offer",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/marketplace/cloud-partner-portal/power-bi/cpp-contacts-tab.md",
+      "redirect_url": "/azure/marketplace/partner-center-portal/create-power-bi-app-offer",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/marketplace/cloud-partner-portal/power-bi/cpp-create-technical-assets.md",
+      "redirect_url": "/azure/marketplace/partner-center-portal/create-power-bi-app-offer",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/marketplace/cloud-partner-portal/power-bi/cpp-publish-offer.md",
+      "redirect_url": "/azure/marketplace/partner-center-portal/create-power-bi-app-offer",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/marketplace/cloud-partner-portal/power-bi/cpp-update-existing-offer.md",
+      "redirect_url": "/azure/marketplace/partner-center-portal/create-power-bi-app-offer",
+      "redirect_document_id": false
     },
     {
       "source_path": "articles/machine-learning/algorithm-module-reference/import-from-azure-blob-storage.md",

articles/active-directory/app-provisioning/use-scim-to-provision-users-and-groups.md

@@ -1198,8 +1198,8 @@ The SCIM spec does not define a SCIM-specific scheme for authentication and auth
 [!NOTE] It's not recommended to leave the token field blank in the Azure AD provisioning configuration custom app UI. The token generated is primarily available for testing purposes.
 
 **OAuth authorization code grant flow:** The provisioning service supports the [authorization code grant](https://tools.ietf.org/html/rfc6749#page-24). After submitting your request for publishing your app in the gallery, our team will work with you to collect the following information:
-*  Authorization URL: A URL by the client to obtain authorization from the resource owner via user-agent redirection. The user is redirected to this URL to authorize access. 
-*  Token exchange URL: A URL by the client to exchange an authorization grant for an access token, typically with client authentication.
+*  Authorization URL: A URL by the client to obtain authorization from the resource owner via user-agent redirection. The user is redirected to this URL to authorize access. Note that this URL is currently not configurable per tenant.
+*  Token exchange URL: A URL by the client to exchange an authorization grant for an access token, typically with client authentication. Note that this URL is currently not configurable per tenant.
 *  Client ID: The authorization server issues the registered client a client identifier, which is a unique string representing the registration information provided by the client.  The client identifier is not a secret; it is exposed to the resource owner and **must not** be used alone for client authentication.  
 *  Client secret: The client secret is a secret generated by the authorization server. It should be a unique value known only to the authorization server. 
 

articles/active-directory/develop/v2-oauth2-auth-code-flow.md

@@ -31,7 +31,7 @@ At a high level, the entire authentication flow for a native/mobile application
 
 ## Request an authorization code
 
-The authorization code flow begins with the client directing the user to the `/authorize` endpoint. In this request, the client requests the `openid`, `offline_access`, and `https://graph.microsoft.com/mail.read ` permissions from from the user.  Some permissions are admin-restricted, for example writing data to an organization's directory by using `Directory.ReadWrite.All`. If your application requests access to one of these permissions from an organizational user, the user receives an error message that says they're not authorized to consent to your app's permissions. To request access to admin-restricted scopes, you should request them directly from a company administrator.  For more information, read [Admin-restricted permissions](v2-permissions-and-consent.md#admin-restricted-permissions).
+The authorization code flow begins with the client directing the user to the `/authorize` endpoint. In this request, the client requests the `openid`, `offline_access`, and `https://graph.microsoft.com/mail.read ` permissions from the user.  Some permissions are admin-restricted, for example writing data to an organization's directory by using `Directory.ReadWrite.All`. If your application requests access to one of these permissions from an organizational user, the user receives an error message that says they're not authorized to consent to your app's permissions. To request access to admin-restricted scopes, you should request them directly from a company administrator.  For more information, read [Admin-restricted permissions](v2-permissions-and-consent.md#admin-restricted-permissions).
 
 ```
 // Line breaks for legibility only

articles/active-directory/saas-apps/google-apps-tutorial.md

@@ -13,7 +13,7 @@ ms.subservice: saas-app-tutorial
 ms.workload: identity
 ms.tgt_pltfrm: na
 ms.topic: tutorial
-ms.date: 02/14/2020
+ms.date: 05/06/2020
 ms.author: jeedes
 
 ms.collection: M365-identity-device-management
@@ -137,8 +137,8 @@ Follow these steps to enable Azure AD SSO in the Azure portal.
 
     | |
 	|--|
-	| `https://google.com` |
-	| `https://google.com/a/<yourdomain.com>` |
+	| `https://www.google.com` |
+	| `https://www.google.com/a/<yourdomain.com>` |
 
 
 1. On the **Basic SAML Configuration** section, if you want to configure for the **Google Cloud Platform** perform the following steps:
@@ -158,8 +158,8 @@ Follow these steps to enable Azure AD SSO in the Azure portal.
 
     | |
 	|--|
-	| `https://google.com` |
-	| `https://google.com/a/<yourdomain.com>` |
+	| `https://www.google.com` |
+	| `https://www.google.com/a/<yourdomain.com>` |
 
     > [!NOTE]
 	> These values are not real. Update these values with the actual Sign-On URL and Identifier. Google Cloud (G Suite) Connector doesn't provide Entity ID/Identifier value on Single Sign On configuration so when you uncheck the **domain specific issuer** option the Identifier value will be `google.com`. If you check the **domain specific issuer** option it will be `google.com/a/<yourdomainname.com>`. To check/uncheck the **domain specific issuer** option you need to go to the **Configure Google Cloud (G Suite) Connector SSO** section which is explained later in the tutorial. For more information contact [Google Cloud (G Suite) Connector Client support team](https://www.google.com/contact/).

articles/automation/automation-solution-vm-management-config.md

@@ -1,15 +1,15 @@
 ---
-title: Azure Automation Configure Start/Stop VMs during off hours solution
+title: Azure Automation Configure Start/Stop VMs during off-hours solution
 description: This article describes how to configure the Start/Stop VMs during off-hours solution to support different use cases or scenarios.
 services: automation
 ms.subservice: process-automation
 ms.date: 04/01/2020
 ms.topic: conceptual
 ---
 
-# How to configure Start/Stop VMs during off hours solution
+# How to configure Start/Stop VMs during off-hours solution
 
-With the **Start/Stop VMs during off hours** solution, you can:
+With the **Start/Stop VMs during off-hours** solution, you can:
 
 - [Schedule VMs to start and stop](#schedule).
 - Schedule VMs to start and stop in ascending order by [using Azure Tags](#tags) (not supported for classic VMs).

articles/automation/automation-solution-vm-management-enable.md

@@ -1,6 +1,6 @@
 ---
-title: Enable Azure Automation Start/Stop VMs during off hours solution
-description: This article describes how to enable the Azure Automation Start/Stop VM solution for your Azure virtual machines.
+title: Enable Azure Automation Start/Stop VMs during off-hours solution
+description: This article describes how to enable the Azure Automation Start/Stop VM during off-hours solution for your Azure virtual machines.
 services: automation
 ms.subservice: process-automation
 ms.date: 04/01/2020

articles/automation/automation-solution-vm-management-logs.md

@@ -1,15 +1,15 @@
 ---
-title: How to query logs from Start/Stop VMs solution
-description: This article describes how to query log data generated by the Start/Stop VMs solution from Azure Monitor.
+title: How to query logs from Start/Stop VMs during off-hours
+description: This article describes how to query log data generated by Start/Stop VMs during off-hours solution from Azure Monitor.
 services: automation
 ms.subservice: process-automation
 ms.date: 04/01/2020
 ms.topic: conceptual
 ---
 
-# How to query logs from Start/Stop VMs solution
+# How to query logs from Start/Stop VMs during off-hours
 
-Azure Automation forwards two types of records to the linked Log Analytics workspace: job logs and job streams. This data is available for [query](../azure-monitor/log-query/log-query-overview.md) in Azure Monitor.
+Azure Automation forwards two types of records to the linked Log Analytics workspace: job logs and job streams. This article reviews the  data available for [query](../azure-monitor/log-query/log-query-overview.md) in Azure Monitor.
 
 ## Job logs