Merge pull request #174091 from kengaderdus/content-freshness-on-stale-articles-b2c

[identity][AAD][B2C] Content freshness on stale b2c content

Author: v-ccolin

articles/active-directory-b2c/overview.md

@@ -8,18 +8,23 @@ manager: celestedg
 ms.service: active-directory
 ms.workload: identity
 ms.topic: overview
-ms.date: 09/19/2019
+ms.date: 10/01/2021
 ms.author: mimart
 ms.subservice: B2C
 ---
 
 # What is Azure Active Directory B2C?
 
-Azure Active Directory B2C provides business-to-customer identity as a service. Your customers use their preferred social, enterprise, or local account identities to get single sign-on access to your applications and APIs.
+Azure Active Directory Business-to-consumer (Azure AD B2C) provides business-to-customer identity as a service. Your customers use their preferred social, enterprise, or local account identities to get single sign-on access to your applications and APIs.
 
 ![Infographic of Azure AD B2C identity providers and downstream applications](./media/overview/azureadb2c-overview.png)
 
-Azure Active Directory B2C (Azure AD B2C) is a customer identity access management (CIAM) solution capable of supporting millions of users and billions of authentications per day. It takes care of the scaling and safety of the authentication platform, monitoring and automatically handling threats like denial-of-service, password spray, or brute force attacks.
+Azure AD B2C is a customer identity access management (CIAM) solution capable of supporting millions of users and billions of authentications per day. It takes care of the scaling and safety of the authentication platform, monitoring, and automatically handling threats like denial-of-service, password spray, or brute force attacks.
+
+Azure AD B2C is a separate service from [Azure Active Directory (Azure AD)](../active-directory/fundamentals/active-directory-whatis.md). It is built on the same technology as Azure AD but for a different purpose - to allow businesses build customer facing application and then allow anyone to sign up into those applications with no restrictions on user account.
+   
+## Who uses Azure AD B2C?
+Any business or individual who wishes to allow anyone to sign up to their web/mobile applications. 
 
 ## Custom-branded identity solution
 
@@ -31,35 +36,36 @@ Customize every page displayed by Azure AD B2C when your users sign up, sign in,
 
 ## Single sign-on access with a user-provided identity
 
-Azure AD B2C uses standards-based authentication protocols including OpenID Connect, OAuth 2.0, and SAML. It integrates with most modern applications and commercial off-the-shelf software.
+Azure AD B2C uses standards-based authentication protocols including OpenID Connect, OAuth 2.0, and Security Assertion Markup Language (SAML). It integrates with most modern applications and commercial off-the-shelf software.
 
-![Diagram of third-party identities federating to Azure AD B2C](./media/overview/scenario-singlesignon.png)
+:::image type="content" source="./media/overview/scenario-singlesignon.png" alt-text="Diagram of third-party identities federating to Azure AD B2C.":::
 
 By serving as the central authentication authority for your web applications, mobile apps, and APIs, Azure AD B2C enables you to build a single sign-on (SSO) solution for them all. Centralize the collection of user profile and preference information, and capture detailed analytics about sign-in behavior and sign-up conversion.
 
 ## Integrate with external user stores
 
 Azure AD B2C provides a directory that can hold 100 custom attributes per user. However, you can also integrate with external systems. For example, use Azure AD B2C for authentication, but delegate to an external customer relationship management (CRM) or customer loyalty database as the source of truth for customer data.
 
-Another external user store scenario is to have Azure AD B2C handle the authentication for your application, but integrate with an external system that stores user profile or personal data. For example, to satisfy data residency requirements like regional or on-premises data storage policies.
+Another external user store scenario is to have Azure AD B2C handle the authentication for your application, but integrate with an external system that stores user profile or personal data. For example, to satisfy data residency requirements like regional or on-premises data storage policies. However, Azure AD B2C service itself is worldwide via the Azure public cloud. 
 
-![A logical diagram of Azure AD B2C communicating with an external user store](./media/overview/scenario-remoteprofile.png)
+:::image type="content" source="./media/overview/scenario-remoteprofile.png" alt-text="A logical diagram of Azure AD B2C communicating with an external user store.":::
 
-Azure AD B2C can facilitate collecting the information from the user during registration or profile editing, then hand that data off to the external system. Then, during future authentications, Azure AD B2C can retrieve the data from the external system and, if needed, include it as a part of the authentication token response it sends to your application.
+Azure AD B2C can facilitate collecting the information from the user during registration or profile editing, then hand that data off to the external system via API. Then, during future authentications, Azure AD B2C can retrieve the data from the external system and, if needed, include it as a part of the authentication token response it sends to your application.
 
 ## Progressive profiling
 
 Another user journey option includes progressive profiling. Progressive profiling allows your customers to quickly complete their first transaction by collecting a minimal amount of information. Then, gradually collect more profile data from the customer on future sign-ins.
 
-![A visual depiction of progressive profiling](./media/overview/scenario-progressive.png)
+:::image type="content" source="./media/overview/scenario-progressive.png" alt-text="A visual depiction of progressive profiling.":::
 
 ## Third-party identity verification and proofing
 
-Use Azure AD B2C to facilitate identity verification and proofing by collecting user data, then passing it to a third party system to perform validation, trust scoring, and approval for user account creation.
+Use Azure AD B2C to facilitate identity verification and proofing by collecting user data, then passing it to a third-party system to perform validation, trust scoring, and approval for user account creation.
+
 
-![A diagram showing the user flow for third-party identity proofing](./media/overview/scenario-idproofing.png)
+:::image type="content" source="./media/overview/scenario-idproofing.png" alt-text="A diagram showing the user flow for third-party identity proofing.":::
 
-These are just some of the things you can do with Azure AD B2C as your business-to-customer identity platform. The following sections of this overview walk you through a demo application that uses Azure AD B2C. You're also welcome to move on directly to a more in-depth [technical overview of Azure AD B2C](technical-overview.md).
+You have learned some of the things you can do with Azure AD B2C as your business-to-customer identity platform. The following sections of this overview walk you through a demo application that uses Azure AD B2C. You're also welcome to move on directly to a more in-depth [technical overview of Azure AD B2C](technical-overview.md).
 
 ## Example: WoodGrove Groceries
 
@@ -99,7 +105,7 @@ Clicking the **Create** button causes Azure AD B2C to redirect the user back to
 
 ### Authenticate business customers
 
-When a customer selects one of the options under **Business customers**, the WoodGrove Groceries website invokes a different Azure AD B2C policy than it does for individual customers.
+When a customer selects one of the options under **Business customers**, the WoodGrove Groceries website invokes a different Azure AD *B2C policy* than it does for individual customers. You learn what a *B2C policy* is in [technical overview of Azure AD B2C](technical-overview.md)
 
 This policy presents the user with an option to use their corporate credentials for sign-up and sign-in. In the WoodGrove example, users are prompted to sign in with any work or school account. This policy uses a [multi-tenant Azure AD application](../active-directory/develop/howto-convert-app-to-be-multi-tenant.md) and the `/common` Azure AD endpoint to federate Azure AD B2C with any Microsoft 365 customer in the world.
 

articles/active-directory-b2c/quickstart-web-app-dotnet.md

@@ -9,16 +9,18 @@ manager: celestedg
 ms.service: active-directory
 ms.topic: quickstart
 ms.custom: "devx-track-csharp, mvc"
-ms.date: 09/12/2019
+ms.date: 10/01/2021
 ms.author: mimart
 ms.subservice: B2C
 ---
 
 # Quickstart: Set up sign in for an ASP.NET application using Azure Active Directory B2C
 
-Azure Active Directory B2C (Azure AD B2C) provides cloud identity management to keep your application, business, and customers protected. Azure AD B2C enables your applications to authenticate to social accounts and enterprise accounts using open standard protocols. In this quickstart, you use an ASP.NET application to sign in using a social identity provider and call an Azure AD B2C protected web API.
+Azure Active Directory B2C (Azure AD B2C) provides cloud identity management to keep your application, business, and customers protected. Azure AD B2C enables your applications to authenticate to social accounts and enterprise accounts using open standard protocols. 
+
+In this quickstart, you use an ASP.NET application to sign in using a social identity provider and call an Azure AD B2C protected web API.
+
 
-[!INCLUDE [quickstarts-free-trial-note](../../includes/quickstarts-free-trial-note.md)]
 
 ## Prerequisites
 
@@ -40,21 +42,21 @@ Azure Active Directory B2C (Azure AD B2C) provides cloud identity management to
 1. In the sample application project folder, open the **B2C-WebAPI-DotNet.sln** solution in Visual Studio.
 2. For this quickstart, you run both the **TaskWebApp** and **TaskService** projects at the same time. Right-click the **B2C-WebAPI-DotNet** solution in Solution Explorer, and then select **Set StartUp Projects**.
 3. Select **Multiple startup projects** and change the **Action** for both projects to **Start**.
-4. Click **OK**.
+4. Select **OK**.
 5. Press **F5** to debug both applications. Each application opens in its own browser tab:
 
     - `https://localhost:44316/` - The ASP.NET web application. You interact directly with this application in the quickstart.
     - `https://localhost:44332/` - The web API that's called by the ASP.NET web application.
 
 ## Sign in using your account
 
-1. Click **Sign up / Sign in** in the ASP.NET web application to start the workflow.
+1. Select **Sign up / Sign in** in the ASP.NET web application to start the workflow.
 
     ![Sample ASP.NET web app in browser with sign up/sign link highlighted](./media/quickstart-web-app-dotnet/web-app-sign-in.png)
 
     The sample supports several sign-up options including using a social identity provider or creating a local account using an email address. For this quickstart, use a social identity provider account from either Facebook, Google, or Microsoft.
 
-2. Azure AD B2C presents a sign-in page for a fictitious company called Fabrikam for the sample web application. To sign up using a social identity provider, click the button of the identity provider you want to use.
+2. Azure AD B2C presents a sign-in page for a fictitious company called Fabrikam for the sample web application. To sign up using a social identity provider, select the button of the identity provider you want to use.
 
     ![Sign In or Sign Up page showing identity provider buttons](./media/quickstart-web-app-dotnet/sign-in-or-sign-up-web.png)
 
@@ -66,40 +68,27 @@ Azure Active Directory B2C (Azure AD B2C) provides cloud identity management to
 
 Azure Active Directory B2C provides functionality to allow users to update their profiles. The sample web app uses an Azure AD B2C edit profile user flow for the workflow.
 
-1. In the application menu bar, click your profile name and select **Edit profile** to edit the profile you created.
+1. In the application menu bar, select your profile name, and then select **Edit profile** to edit the profile you created.
 
     ![Sample web app in browser with Edit profile link highlighted](./media/quickstart-web-app-dotnet/edit-profile-web.png)
 
-2. Change your **Display name** or **City**, and then click **Continue** to update your profile.
+2. Change your **Display name** or **City**, and then select **Continue** to update your profile.
 
-    The changed is displayed in the upper right portion of the web application's home page.
+    The change is displayed in the upper right portion of the web application's home page.
 
 ## Access a protected API resource
 
-1. Click **To-Do List** to enter and modify your to-do list items.
+1. Select **To-Do List** to enter and modify your to-do list items.
 
-2. Enter text in the **New Item** text box. Click **Add** to call the Azure AD B2C protected web API that adds a to-do list item.
+2. In the **New Item** text box, enter text. To call the Azure AD B2C protected web API that adds a to-do list item, select **Add**.
 
     ![Sample web app in browser with Add a to-do list item](./media/quickstart-web-app-dotnet/add-todo-item-web.png)
 
     The ASP.NET web application includes an Azure AD access token in the request to the protected web API resource to perform operations on the user's to-do list items.
 
 You've successfully used your Azure AD B2C user account to make an authorized call an Azure AD B2C protected web API.
 
-## Clean up resources
-
-You can use your Azure AD B2C tenant if you plan to try other Azure AD B2C quickstarts or tutorials. When no longer needed, you can [delete your Azure AD B2C tenant](faq.yml#how-do-i-delete-my-azure-ad-b2c-tenant-).
 
 ## Next steps
 
-In this quickstart, you used a sample ASP.NET application to:
-
-* Sign in with a custom login page
-* Sign in with a social identity provider
-* Create an Azure AD B2C account
-* Call a web API protected by Azure AD B2C
-
-Get started creating your own Azure AD B2C tenant.
-
-> [!div class="nextstepaction"]
-> [Create an Azure Active Directory B2C tenant in the Azure portal](tutorial-create-tenant.md)
+[Create an Azure Active Directory B2C tenant in the Azure portal](tutorial-create-tenant.md)