Merge pull request #15920 from gsacavdm/patch-3

Author: PRMerger-2

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

@@ -32,7 +32,7 @@ In an Azure AD tenant, every user in the tenant (except users with existing Micr
 In an Azure AD B2C tenant, most apps want the user to sign in with any arbitrary email address (for example, [email protected], [email protected], [email protected], or [email protected]). This type of account is a local account. Today, we also support arbitrary user names (just plain strings) as local accounts (for example, joe, bob, sarah, or jim). You can choose one of these two local account types in the Azure AD B2C service.
 
 ### Which social identity providers do you support now? Which ones do you plan to support in the future?
-We currently support Facebook, Google+, LinkedIn, and Amazon. We will add support for other popular social identity providers based on customer demand.
+You can find the list of identity providers supported via built-in policies in the left navigation menu: Guides > Configure identity providers. You can add your own identity provider using [custom policies](https://docs.microsoft.com/azure/active-directory-b2c/active-directory-b2c-overview-custom). We will continue adding support for other popular social identity providers via built-in policies based on customer demand, let us know which ones you'd like to see via the [Azure AD B2C Feedback Forum](http://aka.ms/aadb2cuv).
 
 ### Can I configure scopes to gather more information about consumers from various social identity providers?
 No, but this feature is on our roadmap. The default scopes used for our supported set of social identity providers are: