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

Author: aahill

.gitignore

@@ -1,5 +1,5 @@
 # Operating System files
- .DS_Store
+.DS_Store
 Thumbs.db
 
 # Visual Studio and VS Code files

.openpublishing.publish.config.json

@@ -210,6 +210,12 @@
       "branch": "tutorial",
       "branch_mapping": {}
     },
+    {
+      "path_to_root": "samples-tsi",
+      "url": "https://github.com/Azure-Samples/Azure-Time-Series-Insights",
+      "branch": "master",
+      "branch_mapping": {}
+    },
     {
       "path_to_root": "media-services-v3-dotnet-core-tutorials",
       "url": "https://github.com/Azure-Samples/media-services-v3-dotnet-core-tutorials",

.openpublishing.redirection.json

@@ -1,7 +1,5 @@
 # Contributing to Microsoft Azure Documentation
 
-> Between March 5th and March 9th 2019, the MicrosoftDocs/azure-docs repo will be undergoing a Migration from it's current Markdown engine to the [Markdig](https://github.com/lunet-io/markdig) markdown engine. During this time, we will be turning off the ability to suspending merging of public pull requests in order to complete the migration.
-
 Thank you for taking the time to contribute to the Microsoft Azure documentation.
 
 This guide covers some general topics around contribution and refers out to our [contributors guide](https://docs.microsoft.com/contribute) for more detailed explanations where relevant.

CONTRIBUTING.md

@@ -56,6 +56,8 @@
       href: active-directory-b2c-overview-custom.md
     - name: User access
       href: manage-user-access.md
+  - name: JavaScript and page contracts
+    href: user-flow-javascript-overview.md
   - name: OAuth 2.0
     href: active-directory-b2c-reference-oauth-code.md
   - name: OpenId Connect
@@ -70,8 +72,6 @@
     href: manage-user-data.md
   - name: User flows
     href: active-directory-b2c-reference-policies.md
-  - name: User flows with JavaScript
-    href: user-flow-javascript-overview.md
   - name: User interface customization
     href: customize-ui-overview.md
 - name: How-to guides

articles/active-directory-b2c/TOC.yml

@@ -3,7 +3,7 @@ title: Request an access token - Azure Active Directory B2C | Microsoft Docs
 description: Learn how to request an access token from Azure Active Directory B2C.
 services: active-directory-b2c
 author: davidmu1
-manager: daveba
+manager: celestedg
 
 ms.service: active-directory
 ms.workload: identity

articles/active-directory-b2c/active-directory-b2c-access-tokens.md

@@ -3,7 +3,7 @@ title: Applications types that can be used in Azure Active Directory B2C | Micro
 description: Learn about the types of applications you can use in the Azure Active Directory B2C.
 services: active-directory-b2c
 author: davidmu1
-manager: daveba
+manager: celestedg
 
 ms.service: active-directory
 ms.workload: identity

articles/active-directory-b2c/active-directory-b2c-apps.md

@@ -3,7 +3,7 @@ title: Add claims and customize user input using custom policies - Azure Active
 description: Learn how to customize user input and add claims to the sign-up or sign-in journey in Azure Active Directory B2C.
 services: active-directory-b2c
 author: davidmu1
-manager: daveba
+manager: celestedg
 
 ms.service: active-directory
 ms.workload: identity
@@ -16,20 +16,20 @@ ms.subservice: B2C
 
 [!INCLUDE [active-directory-b2c-advanced-audience-warning](../../includes/active-directory-b2c-advanced-audience-warning.md)]
 
-In this article, you add a new user provided entry (a claim) to your sign-up user journey in Azure Active Directory (Azure AD) B2C.  You configure the entry as a dropdown, and define whether it's required.
+In this article, you add a new user provided entry (a claim) to your sign-up user journey in Azure Active Directory (Azure AD) B2C.  You configure the entry as a dropdown and define whether it's required.
 
 ## Prerequisites
 
 Complete the steps in the article [Getting Started with Custom Policies](active-directory-b2c-get-started-custom.md). Test the sign-up or sign-in user journey to sign up a new local account before proceeding.
 
 ## Add claims
 
-Gathering initial data from your users is achieved using the sign-up or sign-in user journey. Additional claims can be gathered later by using a profile edit user journey. Anytime Azure AD B2C gathers information directly from the user interactively, the Identity Experience Framework uses its selfasserted provider.
+Gathering initial data from your users is achieved using the sign-up or sign-in user journey. Additional claims can be gathered later by using a profile edit user journey. Anytime Azure AD B2C gathers information directly from the user interactively, the Identity Experience Framework uses its self-asserted provider.
 
 
 ### Define the claim
 
-Lets ask the user for their city. Add the following element to the **ClaimsSchema** element in the TrustFrameworkBase policy file:
+Let's ask the user for their city. Add the following element to the **ClaimsSchema** element in the TrustFrameworkBase policy file:
 
 ```xml
 <ClaimType Id="city">

articles/active-directory-b2c/active-directory-b2c-configure-signup-self-asserted-custom.md

@@ -3,7 +3,7 @@ title: Add your own attributes to custom policies in Azure Active Directory B2C
 description: A walkthrough on using extension properties and custom attributes and including them in the user interface.
 services: active-directory-b2c
 author: davidmu1
-manager: daveba
+manager: celestedg
 
 ms.service: active-directory
 ms.workload: identity

articles/active-directory-b2c/active-directory-b2c-create-custom-attributes-profile-edit-custom.md

@@ -3,7 +3,7 @@ title: Track user behavior by using events in Application Insights from Azure Ac
 description: Learn how to enable event logs in Application Insights from Azure AD B2C user journeys by using custom policies (preview).
 services: active-directory-b2c
 author: davidmu1
-manager: daveba
+manager: celestedg
 
 ms.service: active-directory
 ms.topic: conceptual