Merge branch 'master' of https://github.com/MicrosoftDocs/azure-docs-pr into us1546060u

Author: TimShererWithAquent

.openpublishing.redirection.json

@@ -779,7 +779,12 @@
       "source_path": "articles/cognitive-services/LUIS/luis-how-to-account-settings.md",
       "redirect_url": "/azure/cognitive-services/LUIS/luis-how-to-azure-subscription",
       "redirect_document_id": false
-    },    
+    },
+    {
+      "source_path": "articles/cognitive-services/QnAMaker/How-To/create-knowledge-base.md",
+      "redirect_url": "/azure/cognitive-services/QnAMaker/Quickstarts/create-publish-knowledge-base",
+      "redirect_document_id": false
+    },           
     {
       "source_path": "articles/cognitive-services/QnAMaker/quickstarts/csharp.md",
       "redirect_url": "/azure/cognitive-services/QnAMaker/quickstarts/create-publish-kb-csharp-sdk",
@@ -14420,6 +14425,16 @@
       "redirect_url": "/azure/sql-data-warehouse/release-notes-10-0-10106-0",
       "redirect_document_id": false
     },
+    {
+      "source_path": "articles/sql-data-warehouse/changing-maintenance-schedule.md",
+      "redirect_url": "/azure/sql-data-warehouse/maintenance-scheduling#change-a-maintenance-schedule",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/sql-data-warehouse/viewing-maintenance-schedule.md",
+      "redirect_url": "/azure/sql-data-warehouse/maintenance-scheduling#view-a-maintenance-schedule",
+      "redirect_document_id": false
+    },
     {
       "source_path": "articles/sql-data-warehouse/release-notes-april-2018.md",
       "redirect_url": "/azure/sql-data-warehouse/release-notes-10-0-10106-0",
@@ -14630,6 +14645,31 @@
       "redirect_url": "/azure/cognitive-services/Bing-Custom-Search/language-support",
       "redirect_document_id": true
     },
+    {
+      "source_path": "articles/cognitive-services/Bing-Web-Search/paging-webpages.md",
+      "redirect_url": "/azure/cognitive-services/Bing-Web-Search/paging-search-results",
+      "redirect_document_id": true
+    },
+    {
+      "source_path": "articles/cognitive-services/Bing-Custom-Search/page-webpages.md",
+      "redirect_url": "/azure/cognitive-services/Bing-Web-Search/paging-search-results",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/cognitive-services/Bing-News-Search/paging-news.md",
+      "redirect_url": "/azure/cognitive-services/Bing-Web-Search/paging-search-results",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/cognitive-services/Bing-Video-Search/paging-videos.md",
+      "redirect_url": "/azure/cognitive-services/Bing-Web-Search/paging-search-results",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/cognitive-services/Bing-Image-Search/paging-images.md",
+      "redirect_url": "/azure/cognitive-services/Bing-Web-Search/paging-search-results",
+      "redirect_document_id": false
+    },
     {
       "source_path": "articles/cognitive-services/Bing-Spell-Check/bing-spell-check-supported-languages.md",
       "redirect_url": "/azure/cognitive-services/bing-spell-check/language-support",
@@ -20921,7 +20961,7 @@
     },
     {
       "source_path": "articles/virtual-machines/virtual-machines-linux-vertical-scaling-automation.md",
-      "redirect_url": "/azure/virtual-machines/linux/vertical-scaling-automation",
+      "redirect_url": "/azure/virtual-machine-scale-sets/virtual-machine-scale-sets-vertical-scale-reprovision",
       "redirect_document_id": false
     },
     {
@@ -22351,7 +22391,17 @@
     },
     {
       "source_path": "articles/virtual-machines/virtual-machines-windows-vertical-scaling-automation.md",
-      "redirect_url": "/azure/virtual-machines/windows/vertical-scaling-automation",
+      "redirect_url": "/azure/virtual-machine-scale-sets/virtual-machine-scale-sets-vertical-scale-reprovision",
+      "redirect_document_id": false
+    },
+	{
+      "source_path": "articles/virtual-machines/windows/vertical-scaling-automation.md",
+      "redirect_url": "/azure/virtual-machine-scale-sets/virtual-machine-scale-sets-vertical-scale-reprovision",
+      "redirect_document_id": false
+    },
+	{
+      "source_path": "articles/virtual-machines/linux/vertical-scaling-automation.md",
+      "redirect_url": "/azure/virtual-machine-scale-sets/virtual-machine-scale-sets-vertical-scale-reprovision",
       "redirect_document_id": false
     },
     {
@@ -31661,7 +31711,7 @@
     },
     {
       "source_path": "articles/cognitive-services/QnAMaker/Guides/CreateKB.md",
-      "redirect_url": "/azure/cognitive-services/QnAMaker/How-To/create-knowledge-base",
+      "redirect_url": "/azure/cognitive-services/QnAMaker/Quickstarts/create-publish-knowledge-base",
       "redirect_document_id": false
     },
     {
@@ -35848,6 +35898,11 @@
       "redirect_url": "/azure/iot-central/quick-deploy-iot-central",
       "redirect_document_id": false
     },
+    {
+      "source_path": "articles/iot-central/howto-connect-powerbi-pnp.md",
+      "redirect_url": "/azure/iot-central/howto-connect-powerbi",
+      "redirect_document_id": false
+    },
     {
       "source_path": "articles/cognitive-services/QnAMaker/Quickstarts/update-kb-csharp.md",
       "redirect_url": "/azure/cognitive-services/QnAMaker/Quickstarts/csharp#Update",

articles/active-directory-b2c/jwt-issuer-technical-profile.md

@@ -49,7 +49,7 @@ The **InputClaims**, **OutputClaims**, and **PersistClaims** elements are empty
 | refresh_token_lifetime_secs | No | Refresh token lifetimes. The maximum time period before which a refresh token can be used to acquire a new access token, if your application had been granted the offline_access scope. The default is 120,9600 seconds (14 days). The minimum (inclusive) is 86,400 seconds (24 hours). The maximum (inclusive) is 7,776,000 seconds (90 days). |
 | rolling_refresh_token_lifetime_secs | No | Refresh token sliding window lifetime. After this time period elapses the user is forced to reauthenticate, irrespective of the validity period of the most recent refresh token acquired by the application. If you don't want to enforce a sliding window lifetime, set the value of allow_infinite_rolling_refresh_token to `true`. The default is 7,776,000 seconds (90 days). The minimum (inclusive) is 86,400 seconds (24 hours). The maximum (inclusive) is 31,536,000 seconds (365 days). |
 | allow_infinite_rolling_refresh_token | No | If set to `true`, the refresh token sliding window lifetime never expires. |
-| IssuanceClaimPattern | Yes | Controls the Issuer (iss) claim. One of the values:<ul><li>AuthorityAndTenantGuid - The iss claim includes your domain name, such as `login.microsoftonline` or `tenant-name.b2clogin.com`, and your tenant identifier https://login.microsoftonline.com/00000000-0000-0000-0000-000000000000/v2.0/</li><li>AuthorityWithTfp - The iss claim includes your domain name, such as `login.microsoftonline` or `tenant-name.b2clogin.com`, your tenant identifier and your relying party policy name. https://login.microsoftonline.com/tfp/00000000-0000-0000-0000-000000000000/b2c_1a_tp_sign-up-or-sign-in/v2.0/</li></ul> |
+| IssuanceClaimPattern | Yes | Controls the Issuer (iss) claim. One of the values:<ul><li>AuthorityAndTenantGuid - The iss claim includes your domain name, such as `login.microsoftonline` or `tenant-name.b2clogin.com`, and your tenant identifier https:\//login.microsoftonline.com/00000000-0000-0000-0000-000000000000/v2.0/</li><li>AuthorityWithTfp - The iss claim includes your domain name, such as `login.microsoftonline` or `tenant-name.b2clogin.com`, your tenant identifier and your relying party policy name. https:\//login.microsoftonline.com/tfp/00000000-0000-0000-0000-000000000000/b2c_1a_tp_sign-up-or-sign-in/v2.0/</li></ul> |
 | AuthenticationContextReferenceClaimPattern | No | Controls the `acr` claim value.<ul><li>None - Azure AD B2C doesn't issue the acr claim</li><li>PolicyId - the `acr` claim contains the policy name</li></ul>The options for setting this value are TFP (trust framework policy) and ACR (authentication context reference). It is recommended setting this value to TFP, to set the value, ensure the `<Item>` with the `Key="AuthenticationContextReferenceClaimPattern"` exists and the value is `None`. In your relying party policy, add `<OutputClaims>` item, add this element `<OutputClaim ClaimTypeReferenceId="trustFrameworkPolicy" Required="true" DefaultValue="{policy}" />`. Also make sure your policy contains the claim type `<ClaimType Id="trustFrameworkPolicy">	<DisplayName>trustFrameworkPolicy</DisplayName>		<DataType>string</DataType>	</ClaimType>` |
 
 ## Cryptographic keys

articles/active-directory-domain-services/manage-group-policy.md

@@ -35,6 +35,9 @@ To complete this article, you need the following resources and privileges:
     * If needed, complete the tutorial to [create a Windows Server VM and join it to a managed domain][create-join-windows-vm].
 * A user account that's a member of the *Azure AD DC administrators* group in your Azure AD tenant.
 
+> [!NOTE]
+> As there's [no access to domain controllers in Azure AD DS](faqs.md#can-i-connect-to-the-domain-controller-for-my-managed-domain-using-remote-desktop), you can't create and use a Central Store for group policy administrative templates in a managed domain. [Sysvol isn't included in on-premises Azure AD Connect synchronization](synchronization.md#what-isnt-synchronized-to-azure-ad-ds), so you also can't create an on-premises Central Store and synchronize it to Azure AD DS through Azure AD.
+
 ## Install Group Policy Management tools
 
 To create and configure Group Policy Object (GPOs), you need to install the Group Policy Management tools. These tools can be installed as a feature in Windows Server. For more information on how to install the administrative tools on a Windows client, see install [Remote Server Administration Tools (RSAT)][install-rsat].

articles/active-directory/develop/TOC.yml

@@ -219,6 +219,94 @@
           href: scenario-mobile-call-api.md
         - name: Move to production
           href: scenario-mobile-production.md      
+    - name: Microsoft Authentication Library (MSAL)
+      items:
+      - name: Overview
+        href: msal-overview.md
+      - name: Accounts & tenant profiles (Android)
+        href: accounts-overview.md
+      - name: Authorization agents (Android)
+        href: authorization-agents.md
+      - name: Brokered auth (Android)
+        href: brokered-auth.md
+      - name: Migration
+        items:
+        - name: Migrate to MSAL.NET
+          href: msal-net-migration.md
+        - name: Migrate to MSAL.js
+          href: msal-compare-msal-js-and-adal-js.md
+        - name: Migrate to MSAL.Android
+          href: migrate-android-adal-msal.md
+        - name: Migrate to MSAL.iOS and MacOS
+          href: migrate-objc-adal-msal.md
+        - name: Migrate Xamarin apps using brokers from ADAL.NET to MSAL.NET
+          href: msal-net-migration-ios-broker.md
+      - name: Supported authentication flows
+        href: msal-authentication-flows.md
+      - name: Single and multi account public client apps (Android)
+        href: single-multi-account.md
+      - name: Acquire and cache tokens
+        items:
+        - name: Acquire and cache tokens
+          href: msal-acquire-cache-tokens.md
+        - name: Scopes for v1.0 apps
+          href: msal-v1-app-scopes.md
+      - name: Client applications
+        items:
+        - name: Client applications
+          href: msal-client-applications.md
+        - name: Application configuration (.NET)
+          href: msal-client-application-configuration.md
+        - name: Initialize applications (.NET)
+          href: msal-net-initializing-client-applications.md
+        - name: Client assertions (.NET)
+          href: msal-net-client-assertions.md
+        - name: Initialize applications (JS)
+          href: msal-js-initializing-client-applications.md
+      - name: Handle errors and exceptions
+        href: msal-handling-exceptions.md        
+      - name: Logging
+        href: msal-logging.md
+      - name: Single sign-on
+        items:
+        - name: Single sign-on with MSAL.js
+          href: msal-js-sso.md
+        - name: Single sign-on with MSAL for iOS and macOS
+          items:
+          - name: SSO between MSAL apps
+            href: single-sign-on-macos-ios.md
+          - name: SSO between ADAL and MSAL apps
+            href: sso-between-adal-msal-apps-macos-ios.md
+      - name: Integrate with ADFS
+        items:
+        - name: ADFS support in MSAL.NET
+          href: msal-net-adfs-support.md
+      - name: Integrate with Azure AD B2C
+        items:
+        - name: Android
+          href: msal-android-b2c.md
+        - name: JavaScript
+          href: msal-b2c-overview.md
+        - name: .NET
+          href: msal-net-aad-b2c-considerations.md
+        - name: iOS and macOS
+          href: config-authority.md#b2c
+      - name: Considerations and known issues
+        items:
+          - name: MSAL.NET
+            items:
+            - name: Web browsers
+              href: msal-net-web-browsers.md              
+          - name: MSAL.js
+            items:
+            - name: Considerations using IE
+              href: msal-js-use-ie-browser.md
+            - name: Known issues- IE and Microsoft Edge
+              href: msal-js-known-issues-ie-edge-browsers.md
+            - name: Known issues- Safari 
+              href: msal-js-known-issues-safari-browser.md
+          - name: MSAL for iOS and macOS SSL issues
+            href: ssl-issues.md
     - name: Authentication protocol
       items:
       - name: Application types and OAuth2.0
@@ -368,98 +456,6 @@
         href: vs-active-directory-webapi-what-happened.md
       - name: Error during authentication detection
         href: vs-active-directory-error.md
-  - name: Microsoft Authentication Library (MSAL)
-    items:
-      - name: Overview
-        href: msal-overview.md
-      - name: Accounts & tenant profiles (Android)
-        href: accounts-overview.md
-      - name: Authorization agents (Android)
-        href: authorization-agents.md
-      - name: Brokered auth (Android)
-        items:
-          - name: Brokered auth (Android)
-            href: brokered-auth.md
-      - name: Migration
-        items:
-        - name: Migrate to MSAL.NET
-          href: msal-net-migration.md
-        - name: Migrate to MSAL.js
-          href: msal-compare-msal-js-and-adal-js.md
-        - name: Migrate to MSAL.Android
-          href: migrate-android-adal-msal.md
-        - name: Migrate to MSAL.iOS and MacOS
-          href: migrate-objc-adal-msal.md
-        - name: Migrate Xamarin apps using brokers from ADAL.NET to MSAL.NET
-          href: msal-net-migration-ios-broker.md
-      - name: Supported authentication flows
-        href: msal-authentication-flows.md
-      - name: Single and multi account public client apps (Android)
-        href: single-multi-account.md
-      - name: Acquire and cache tokens
-        items:
-        - name: Acquire and cache tokens
-          href: msal-acquire-cache-tokens.md
-        - name: Scopes for v1.0 apps
-          href: msal-v1-app-scopes.md
-      - name: Client applications
-        items:
-        - name: Client applications
-          href: msal-client-applications.md
-        - name: Application configuration (.NET)
-          href: msal-client-application-configuration.md
-        - name: Initialize applications (.NET)
-          href: msal-net-initializing-client-applications.md
-        - name: Client assertions (.NET)
-          href: msal-net-client-assertions.md
-        - name: Initialize applications (JS)
-          href: msal-js-initializing-client-applications.md
-      - name: Handle errors and exceptions
-        href: msal-handling-exceptions.md        
-      - name: Logging
-        href: msal-logging.md
-      - name: Single sign-on
-        items:
-        - name: Single sign-on with MSAL.js
-          href: msal-js-sso.md
-        - name: Single sign-on with MSAL for iOS and macOS
-          items:
-          - name: SSO between MSAL apps
-            href: single-sign-on-macos-ios.md
-          - name: SSO between ADAL and MSAL apps
-            href: sso-between-adal-msal-apps-macos-ios.md
-      - name: Integrate with ADFS
-        items:
-        - name: ADFS support in MSAL.NET
-          href: msal-net-adfs-support.md
-      - name: Integrate with Azure AD B2C
-        items:
-        - name: Android
-          href: msal-android-b2c.md
-        - name: JavaScript
-          href: msal-b2c-overview.md
-        - name: .NET
-          href: msal-net-aad-b2c-considerations.md
-        - name: iOS and macOS
-          href: config-authority.md#b2c
-      - name: Considerations and known issues
-        items:
-          - name: MSAL.NET
-            items:
-            - name: Web browsers
-              href: msal-net-web-browsers.md              
-          - name: MSAL.js
-            items:
-            - name: Considerations using IE
-              href: msal-js-use-ie-browser.md
-            - name: Known issues- IE and Microsoft Edge
-              href: msal-js-known-issues-ie-edge-browsers.md
-            - name: Known issues- Safari 
-              href: msal-js-known-issues-safari-browser.md
-          - name: MSAL for iOS and macOS
-            items:
-            - name: SSL issues
-              href: ssl-issues.md
   - name: References
     items:
     - name: Authentication libraries

articles/active-directory/develop/active-directory-saml-claims-customization.md

@@ -14,7 +14,7 @@ ms.workload: identity
 ms.tgt_pltfrm: na
 ms.devlang: na
 ms.topic: conceptual
-ms.date: 04/03/2019
+ms.date: 10/01/2019
 ms.author: ryanwi
 ms.reviewer: luleon, paulgarn, jeedes
 ms.custom: aaddev
@@ -80,6 +80,20 @@ Select the desired source for the `NameIdentifier` (or NameID) claim. You can se
 
 For more info, see [Table 3: Valid ID values per source](active-directory-claims-mapping.md#table-3-valid-id-values-per-source).
 
+You can also assign any constant (static) value to any claims which you define in Azure AD. Please follow the below steps to assign a constant value:
+
+1. In the [Azure portal](https://portal.azure.com/), on the **User Attributes & Claims** section, click on the **Edit** icon to edit the claims.
+
+1. Click on the required claim which you want to modify.
+
+1. Enter the constant value in the **Source attribute** as per your organization and click **Save**.
+
+    ![Open the User Attributes & Claims section in the Azure portal](./media/active-directory-saml-claims-customization/organization-attribute.png)
+
+1. The constant value will be displayed as below.
+
+    ![Open the User Attributes & Claims section in the Azure portal](./media/active-directory-saml-claims-customization/edit-attributes-claims.png)
+
 ### Special claims - Transformations
 
 You can also use the claims transformations functions.