Merge branch 'master' into portalMenu

Author: LauraKellerGitHub

.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,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

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

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.

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

@@ -1,6 +1,7 @@
 ---
-title: Track user behavior by using events in Application Insights from Azure Active Directory B2C | Microsoft Docs
-description: Learn how to enable event logs in Application Insights from Azure AD B2C user journeys by using custom policies (preview).
+title: Track user behavior with Application Insights
+titleSuffix: Azure AD B2C
+description: Learn how to enable event logs in Application Insights from Azure AD B2C user journeys by using custom policies.
 services: active-directory-b2c
 author: mmacy
 manager: celestedg
@@ -28,7 +29,7 @@ When you use Azure Active Directory B2C (Azure AD B2C) together with Azure Appli
 
 The Identity Experience Framework in Azure AD B2C includes the provider `Handler="Web.TPEngine.Providers.AzureApplicationInsightsProvider, Web.TPEngine, Version=1.0.0.0`. It sends event data directly to Application Insights by using the instrumentation key provided to Azure AD B2C.
 
-A technical profile uses this provider to define an event from Azure AD B2C. The profile specifies the name of the event, the claims that are recorded, and the instrumentation key. To post an event, the technical profile is then added as an `orchestration step`, or as a `validation technical profile` in a custom user journey.
+A technical profile uses this provider to define an event from Azure AD B2C. The profile specifies the name of the event, the claims that are recorded, and the instrumentation key. To post an event, the technical profile is then added as an `orchestration step` in a custom user journey.
 
 Application Insights can unify the events by using a correlation ID to record a user session. Application Insights makes the event and session available within seconds and presents many visualization, export, and analytical tools.
 

articles/active-directory-b2c/active-directory-b2c-custom-guide-eventlogger-appins.md

@@ -1,5 +1,6 @@
 ---
-title: Secure your RESTful services by using HTTP basic authentication in Azure Active Directory B2C | Microsoft Docs
+title: Secure a RESTful service by using HTTP basic authentication
+titleSuffix: Azure AD B2C
 description: Secure your custom REST API claims exchanges in your Azure AD B2C by using HTTP basic authentication.
 services: active-directory-b2c
 author: mmacy

articles/active-directory-b2c/active-directory-b2c-custom-rest-api-netfw-secure-basic.md

@@ -1,5 +1,6 @@
 ---
-title: Secure your RESTful service by using client certificates in Azure Active Directory B2C | Microsoft Docs
+title: Secure a RESTful service by using client certificates
+titleSuffix: Azure AD B2C
 description: Secure your custom REST API claims exchanges in your Azure AD B2C by using client certificates
 services: active-directory-b2c
 author: mmacy