Merge pull request #2 from MicrosoftDocs/master

Syncing my fork to the original repository

Author: docohe

.gitignore

@@ -22,5 +22,5 @@ articles/directories.txt
 AzureMigration.ps1
 
 !/.vscode/extensions.json
-articles/data-lake-analytics/.vscode/settings.json
 .gitignore
+**/.vscode/settings.json

.markdownlint.json

@@ -9,6 +9,7 @@
     "MD007": false,
     "MD009": false,
     "MD010": false,
+    "MD011": true,
     "MD012": false,
     "MD013": false,
     "MD014": false,
@@ -32,10 +33,28 @@
     "MD035": false,
     "MD036": false,
     "MD037": false,
+    "MD038": true,
+    "MD039": true,
     "MD040": false,
     "MD041": false,
     "MD042": false,
+    "MD043": true,
+    "MD044": {
+        "code_blocks": false,
+        "names": [
+            ".NET",
+            "ASP.NET",
+            "Azure",
+            "JavaScript",
+            "NuGet",
+            "PowerShell",
+            "macOS",
+            "C#",
+            "CLI"
+        ]
+    },
     "MD045": false,
     "MD046": false,
-    "MD047": false
+    "MD047": false,
+    "MD048": true
 }

.openpublishing.publish.config.json

@@ -194,7 +194,7 @@
     {
       "path_to_root": "samples-cognitive-services-speech-sdk",
       "url": "https://github.com/Azure-Samples/cognitive-services-speech-sdk",
-      "branch": "rhurey/quickstart.refactor"
+      "branch": "release-ignite-cogserv-speech-service"
     },
     {
       "path_to_root": "media-services-v3-dotnet-quickstarts",

.openpublishing.redirection.json

@@ -1,24 +1,17 @@
 # Testing the new code owners feature in GitHub. Please contact Cory Fowler if you have questions.
-# articles/storage/  @tamram @robinsh
-# articles/virtual-machines/  @iainfoulds @cynthn
-# articles/virtual-machines/linux/  @iainfoulds @cynthn
-# articles/virtual-machines/windows/  @iainfoulds @cynthn
-# articles/application-insights/  @SergeyKanzhelev
-# articles/cosmos-db/ @mimig1
-
-# All Articles
-articles/ @apex-docs-pr-reviewers
-
 # Cognitive Services
 articles/cognitive-services/ @diberry @erhopf, @nitinme
 
 # DevOps
-
 articles/ansible/ @TomArcherMsft
 articles/chef/ @TomArcherMsft
 articles/jenkins/ @TomArcherMsft
 articles/terraform/ @TomArcherMsft
 
 # Governance
-
 articles/governance/ @DCtheGeek
+
+# Configuration
+*.json @SyntaxC4 @snoviking @arob98
+.acrolinx-config.edn @MonicaRush @arob98
+articles/zone-pivot-groups.yml @SyntaxC4 @snoviking @arob98

CODEOWNERS

@@ -1,10 +1,11 @@
+
 # Microsoft Azure Documentation
 
 Welcome to the open-source [documentation](https://docs.microsoft.com/azure) of [Microsoft Azure](https://azure.microsoft.com). Please review this README file to understand how you can assist in contributing to the Microsoft Azure documentation.
 
 ## Getting Started
 
-Contributing to open source is more than just providing updates, it's also letting us know when there is an issue. Read our [Contributing guidance](CONTRIBUTING.md) to find out more.
+Contributing to open source is more than just providing updates, it's also about letting us know when there is an issue. Read our [Contributing guidance](CONTRIBUTING.md) to find out more.
 
 ### Prerequisites
 

README.md

@@ -76,8 +76,11 @@
   items:
   - name: App integration
     items:
-    - name: Register an application
+    - name: Register an OIDC application
       href: tutorial-register-applications.md
+    - name: Register a SAML service provider
+      href: connect-with-saml-service-providers.md
+      displayName: SP, RP, service provider, connect
     - name: Add a web API application
       href: add-web-application.md
     - name: Add a native client application
@@ -160,6 +163,9 @@
         href: active-directory-b2c-reference-kmsi-custom.md
       - name: Password change
         href: active-directory-b2c-reference-password-change-custom.md
+      - name: Phone sign-up & sign-in
+        href: phone-authentication.md
+        displayName: otp, passwordless, phone number
     - name: UX customization
       items:
       - name: Configure user input
@@ -168,6 +174,9 @@
         href: active-directory-b2c-ui-customization-custom.md
       - name: Customize the UI dynamically
         href: active-directory-b2c-ui-customization-custom-dynamic.md
+      - name: Custom email
+        href: custom-email.md
+        displayName: verification
       - name: Page layout
         href: page-layout.md
       - name: Enable JavaScript
@@ -196,8 +205,10 @@
         items:
         - name: ADFS
           href: active-directory-b2c-custom-setup-adfs2016-idp.md
+          displayName: SAML
         - name: Salesforce
           href: active-directory-b2c-setup-sf-app-custom.md
+          displayName: SAML
     - name: Tokens and session management
       items:
       - name: Customize tokens
@@ -254,6 +265,8 @@
             href: integer-transformations.md
           - name: JSON
             href: json-transformations.md
+          - name: Phone number
+            href: phone-number-claims-transformations.md
           - name: External accounts
             href: social-transformations.md
           - name: StringCollection
@@ -277,6 +290,9 @@
           items:
           - name: About technical profiles
             href: technical-profiles-overview.md
+          - name: Azure Multi-Factor Authentication
+            href: multi-factor-auth-technical-profile.md
+            displayName: mfa
           - name: Claim resolvers
             href: claim-resolver-overview.md
           - name: Azure Active Directory
@@ -289,6 +305,9 @@
             href: oauth1-technical-profile.md
           - name: OAuth2
             href: oauth2-technical-profile.md
+          - name: One-time password
+            href: one-time-password-technical-profile.md
+            displayName: otp
           - name: OpenID Connect
             href: openid-connect-technical-profile.md
           - name: REST
@@ -301,6 +320,11 @@
             href: active-directory-b2c-reference-sso-custom.md
           - name: Validation
             href: validation-technical-profile.md
+      - name: DisplayControls
+        href: display-controls.md
+        items:
+        - name: Verification
+          href: display-control-verification.md
       - name: UserJourneys
         href: userjourneys.md
       - name: RelyingParty
@@ -348,6 +372,8 @@
     href: https://azure.microsoft.com/resources/samples/?service=active-directory-b2c
   - name: Cookie definitions
     href: cookie-definitions.md
+  - name: Error codes
+    href: error-codes.md
   - name: Region availability & data residency
     href: active-directory-b2c-reference-tenant-type.md
   - name: Enable billing

articles/active-directory-b2c/TOC.yml

@@ -1,5 +1,6 @@
 ---
-title: Application types that can be used in Azure Active Directory B2C
+title: Application types supported by Azure AD B2C
+titleSuffix: Azure AD B2C
 description: Learn about the types of applications you can use with Azure Active Directory B2C.
 services: active-directory-b2c
 author: mmacy
@@ -120,7 +121,7 @@ To set up client credential flow, see [Azure Active Directory v2.0 and the OAuth
 
 #### Web API chains (on-behalf-of flow)
 
-Many architectures include a web API that needs to call another downstream web API, where both are secured by Azure AD B2C. This scenario is common in native clients that have a Web API back-end and calls a Microsoft online service such as the Azure AD Graph API.
+Many architectures include a web API that needs to call another downstream web API, where both are secured by Azure AD B2C. This scenario is common in native clients that have a Web API back-end and calls a Microsoft online service such as the Microsoft Graph API or Azure AD Graph API.
 
 This chained web API scenario can be supported by using the OAuth 2.0 JWT bearer credential grant, also known as the on-behalf-of flow.  However, the on-behalf-of flow is not currently implemented in the Azure AD B2C.
 

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

@@ -1,5 +1,6 @@
 ---
-title: Add claims and customize user input using custom policies - Azure Active Directory B2C | Microsoft Docs
+title: Add claims and customize user input in custom policies
+titleSuffix: Azure AD B2C
 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: mmacy

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

@@ -1,5 +1,6 @@
 ---
-title: Add your own attributes to custom policies in Azure Active Directory B2C | Microsoft Docs
+title: Add your own attributes to custom policies
+titleSuffix: Azure AD B2C
 description: A walkthrough on using extension properties and custom attributes and including them in the user interface.
 services: active-directory-b2c
 author: mmacy
@@ -297,3 +298,4 @@ For more information on extension properties, see the article [Directory schema
 > * A **TechnicalProfile** is an element type, or function, that defines an endpoint’s name, metadata, and protocol. The **TechnicalProfile** details the exchange of claims that the Identity Experience Framework performs. When this function is called in an orchestration step or from another **TechnicalProfile**, the **InputClaims** and **OutputClaims** are provided as parameters by the caller.
 > * Extension attributes in the Graph API are named by using the convention `extension_ApplicationObjectID_attributename`.
 > * Custom policies refer to extension attributes as **extension_attributename**. This reference omits the **ApplicationObjectId** in XML.
+> * You have to specify the attribute ID in the following format **extension_attributename** wherever it is being referenced.