updated

Author: v-bhgad

.openpublishing.publish.config.json

@@ -334,6 +334,11 @@
       "path_to_root": "VideoReviewConsoleApp",
       "url": "https://github.com/MicrosoftContentModerator/VideoReviewConsoleApp",
       "branch": "master"
+    },
+    {
+      "path_to_root": "cognitive-services-quickstart-code",
+      "url": "https://github.com/Azure-Samples/cognitive-services-quickstart-code",
+      "branch": "master"
     }
   ],
   "branch_target_mapping": {

.openpublishing.redirection.json

@@ -10,12 +10,7 @@
 articles/ @apex-docs-pr-reviewers
 
 # Cognitive Services
-articles/cognitive-services/ @nitinme @tchristiani @cjgronlund
-articles/cognitive-services/LUIS/ @cjgronlund @nitinme @diberry
-articles/cognitive-services/Speaker-recognition/ @cjgronlund @nitinme @erhopf
-articles/cognitive-services/Speech-Service/ @cjgronlund @nitinme @erhopf
-articles/cognitive-services/Translator/ @cjgronlund @nitinme @erhopf
-articles/cognitive-services/QnAMaker/ @cjgronlund @nitinme @diberry
+articles/cognitive-services/ @diberry @erhopf, @nitinme
 
 # DevOps
 
@@ -26,4 +21,4 @@ articles/terraform/ @TomArcherMsft
 
 # Governance
 
-articles/governance/ @DCtheGeek
+articles/governance/ @DCtheGeek

CODEOWNERS

@@ -46,7 +46,7 @@
   href: code-samples.md
 - name: Concepts
   items:
-  - name: Applications types
+  - name: Application types
     href: active-directory-b2c-apps.md
   - name: Authentication protocols
     href: active-directory-b2c-reference-protocols.md

articles/active-directory-b2c/TOC.yml

@@ -1,28 +1,28 @@
 ---
-title: Applications types that can be used in Azure Active Directory B2C | Microsoft Docs
-description: Learn about the types of applications you can use in the Azure Active Directory B2C.
+title: Application types that can be used in Azure Active Directory B2C
+description: Learn about the types of applications you can use with Azure Active Directory B2C.
 services: active-directory-b2c
 author: mmacy
 manager: celestedg
 
 ms.service: active-directory
 ms.workload: identity
 ms.topic: conceptual
-ms.date: 01/11/2019
+ms.date: 07/24/2019
 ms.author: marsma
 ms.subservice: B2C
 
 ---
-# Applications types that can be used in Active Directory B2C
+# Application types that can be used in Active Directory B2C
 
-Azure Active Directory (Azure AD) B2C supports authentication for a variety of modern application architectures. All of them are based on the industry standard protocols [OAuth 2.0](active-directory-b2c-reference-protocols.md) or [OpenID Connect](active-directory-b2c-reference-protocols.md). This document describes the types of applications that you can build, independent of the language or platform you prefer. It also helps you understand the high-level scenarios before you start building applications.
+Azure Active Directory (Azure AD) B2C supports authentication for a variety of modern application architectures. All of them are based on the industry standard protocols [OAuth 2.0](active-directory-b2c-reference-protocols.md) or [OpenID Connect](active-directory-b2c-reference-protocols.md). This article describes the types of applications that you can build, independent of the language or platform you prefer. It also helps you understand the high-level scenarios before you start building applications.
 
 Every application that uses Azure AD B2C must be registered in your [Azure AD B2C tenant](active-directory-b2c-get-started.md) by using the [Azure portal](https://portal.azure.com/). The application registration process collects and assigns values, such as:
 
 * An **Application ID** that uniquely identifies your application.
 * A **Reply URL** that can be used to direct responses back to your application.
 
-Each request that is sent to Azure AD B2C specifies a **user flow**, which is a policy that controls the behavior of Azure AD. You can also use these endpoints to create a highly customizable set of user experiences. We provide a set of user flows to help you set up common policies, including sign-up, sign-in, and profile-edit policies. But you can also create your own custom policies. If you are not familiar with policies, you should read about the Azure AD B2C [extensible policy framework](active-directory-b2c-reference-policies.md) before you continue.
+Each request that is sent to Azure AD B2C specifies a **user flow** (a built-in policy) or a **custom policy** that controls the behavior of Azure AD B2C. Both policy types enable you to create a highly customizable set of user experiences.
 
 The interaction of every application follows a similar high-level pattern:
 
@@ -39,7 +39,7 @@ These steps can differ slightly based on the type of application you're building
 
 For web applications (including .NET, PHP, Java, Ruby, Python, and Node.js) that are hosted on a server and accessed through a browser, Azure AD B2C supports [OpenID Connect](active-directory-b2c-reference-protocols.md) for all user experiences. In the Azure AD B2C implementation of OpenID Connect, your web application initiates user experiences by issuing authentication requests to Azure AD. The result of the request is an `id_token`. This security token represents the user's identity. It also provides information about the user in the form of claims:
 
-```
+```json
 // Partial raw id_token
 eyJ0eXAiOiJKV1QiLCJhbGciOiJSUzI1NiIsIng1dCI6ImtyaU1QZG1Cd...
 
@@ -102,19 +102,19 @@ To learn how to secure a web API by using Azure AD B2C, check out the web API tu
 
 ## Mobile and native applications
 
-Applications that are installed on devices, such as mobile and desktop applications, often need to access back-end services or web APIs on behalf of users. You can add customized identity management experiences to your native applications and securely call back-end services by using Azure AD B2C and the [OAuth 2.0 authorization code flow](active-directory-b2c-reference-oauth-code.md).  
+Applications that are installed on devices, such as mobile and desktop applications, often need to access back-end services or web APIs on behalf of users. You can add customized identity management experiences to your native applications and securely call back-end services by using Azure AD B2C and the [OAuth 2.0 authorization code flow](active-directory-b2c-reference-oauth-code.md).
 
 In this flow, the application executes [policies](active-directory-b2c-reference-policies.md) and receives an `authorization_code` from Azure AD after the user completes the policy. The `authorization_code` represents the application's permission to call back-end services on behalf of the user who is currently signed in. The application can then exchange the `authorization_code` in the background for an `access_token` and a `refresh_token`.  The application can use the `access_token` to authenticate to a back-end web API in HTTP requests. It can also use the `refresh_token` to get a new `access_token` when an older one expires.
 
 ## Current limitations
 
-### Application not supported 
+### Unsupported application types
 
 #### Daemons/server-side applications
 
 Applications that contain long-running processes or that operate without the presence of a user also need a way to access secured resources such as web APIs. These applications can authenticate and get tokens by using the application's identity (rather than a user's delegated identity) and by using the OAuth 2.0 client credentials flow. Client credential flow is not the same as on-behalf-flow and on-behalf-flow should not be used for server-to-server authentication.
 
-Although client credential flow is not currently supported by Azure AD B2C, you can set up client credential flow using Azure AD. An Azure AD B2C tenant shares some functionality with Azure AD enterprise tenants.  The client credential flow is supported using the Azure AD functionality of the Azure AD B2C tenant. 
+Although client credential flow is not currently supported by Azure AD B2C, you can set up client credential flow using Azure AD. An Azure AD B2C tenant shares some functionality with Azure AD enterprise tenants.  The client credential flow is supported using the Azure AD functionality of the Azure AD B2C tenant.
 
 To set up client credential flow, see [Azure Active Directory v2.0 and the OAuth 2.0 client credentials flow](https://docs.microsoft.com/azure/active-directory/develop/active-directory-v2-protocols-oauth-client-creds). A successful authentication results in the receipt of a token formatted so that it can be used by Azure AD as described in [Azure AD token reference](https://docs.microsoft.com/azure/active-directory/develop/active-directory-token-and-claims).
 
@@ -135,3 +135,6 @@ If you edit the Azure AD B2C application outside of the Azure portal, it becomes
 
 To delete the application, go to the [Application Registration Portal](https://apps.dev.microsoft.com/) and delete the application there. In order for the application to be visible, you need to be the owner of the application (and not just an admin of the tenant).
 
+## Next steps
+
+Find out more about the built-in policies provided by [User flows in Azure Active Directory B2C](active-directory-b2c-reference-policies.md).