Merge pull request #116610 from yoelhor/patch-2

Update technical-overview.md

Author: PMEds28

articles/active-directory-b2c/media/technical-overview/protocols.png

@@ -8,7 +8,7 @@ manager: celestedg
 ms.service: active-directory
 ms.workload: identity
 ms.topic: overview
-ms.date: 09/19/2019
+ms.date: 05/28/2020
 ms.author: mimart
 ms.subservice: B2C
 ---
@@ -32,7 +32,7 @@ The primary resources you work with in an Azure AD B2C tenant are:
   * *Social* identity providers like Facebook, LinkedIn, or Twitter that you want to support in your applications.
   * *External* identity providers that support standard identity protocols like OAuth 2.0, OpenID Connect, and more.
   * *Local* accounts that enable users to sign up and sign in with a username (or email address or other ID) and password.
-* **Keys** - Add and manage encryption keys for signing and validating tokens.
+* **Keys** - Add and manage encryption keys for signing and validating tokens, client secrets, certificates, and passwords.
 
 An Azure AD B2C tenant is the first resource you need to create to get started with Azure AD B2C. Learn how in [Tutorial: Create an Azure Active Directory B2C tenant](tutorial-create-tenant.md).
 
@@ -65,7 +65,7 @@ Learn more about the user account types in Azure AD B2C in [Overview of user acc
 
 ## External identity providers
 
-You can configure Azure AD B2C to allow users to sign in to your application with credentials from external social or enterprise identity providers (IdP). Azure AD B2C supports external identity providers like Facebook, Microsoft account, Google, Twitter, and any identity provider that supports OAuth 1.0, OAuth 2.0, OpenID Connect, SAML, or WS-Federation protocols.
+You can configure Azure AD B2C to allow users to sign in to your application with credentials from external social or enterprise identity providers (IdP). Azure AD B2C supports external identity providers like Facebook, Microsoft account, Google, Twitter, and any identity provider that supports OAuth 1.0, OAuth 2.0, OpenID Connect, and SAML protocols.
 
 ![External identity providers](media/technical-overview/external-idps.png)
 
@@ -130,16 +130,14 @@ Learn more about custom policies in [Custom policies in Azure Active Directory B
 
 ## Protocols and tokens
 
-Azure AD B2C supports the [OpenID Connect and OAuth 2.0 protocols](protocols-overview.md) for user journeys. In the Azure AD B2C implementation of OpenID Connect, your application starts the user journey by issuing authentication requests to Azure AD B2C.
+- For applications, Azure AD B2C supports the [OAuth 2.0](protocols-overview.md), [OpenID Connect](openid-connect.md), and [SAML protocols](connect-with-saml-service-providers.md) for user journeys. Your application starts the user journey by issuing authentication requests to Azure AD B2C. The result of a request to Azure AD B2C is a security token, such as an [ID token, access token](tokens-overview.md), or SAML token. This security token defines the user's identity within the application.
 
-The result of a request to Azure AD B2C is a security token, such as an [ID token or access token](tokens-overview.md). This security token defines the user's identity. Tokens are received from Azure AD B2C endpoints like the `/token` or `/authorize` endpoint. With these tokens, you can access claims that can be used to validate an identity and allow access to secure resources.
+- For external identities, Azure AD B2C supports federation with any OAuth 1.0, OAuth 2.0, OpenID Connect, and SAML identity providers.
 
-For external identities, Azure AD B2C supports federation with any OAuth 1.0, OAuth 2.0, OpenID Connect, SAML, and WS-Fed identity provider.
+The following diagram shows how Azure AD B2C can communicate using a variety of protocols within the same authentication flow:
 
 ![Diagram of OIDC-based client app federating with a SAML-based IdP](media/technical-overview/protocols.png)
 
-The preceding diagram shows how Azure AD B2C can communicate using variety of protocols within the same authentication flow:
-
 1. The relying party application initiates an authorization request to Azure AD B2C using OpenID Connect.
 1. When a user of the application chooses to sign in using an external identity provider that uses the SAML protocol, Azure AD B2C invokes the SAML protocol to communicate with that identity provider.
 1. After the user completes the sign-in operation with the external identity provider, Azure AD B2C then returns the token to the relying party application using OpenID Connect.
@@ -263,4 +261,4 @@ Find out more about usage analytics in [Track user behavior in Azure Active Dire
 Now that you have deeper view into the features and technical aspects of Azure Active Directory B2C, get started with the service by creating a B2C tenant:
 
 > [!div class="nextstepaction"]
-> [Tutorial: Create an Azure Active Directory B2C tenant >](tutorial-create-tenant.md)
+> [Tutorial: Create an Azure Active Directory B2C tenant >](tutorial-create-tenant.md)