title: AAD-FindLocalAccountWithSocialEmail produces No suitable claims providers were found
body: <p>I am attempting to auto-link a social provider login to an existing local account.
  I'm using the <a href="https://github.com/azure-ad-b2c/samples/tree/master/policies/auto-account-linking/policy" rel="nofollow noreferrer">auto-linking sample</a>, but doing so having replaced the sample Facebook ClaimsProviders/etc with ones for Google. Using my version of B2C_1A_ACCOUNTLINK_SUSI, I can create and login to a local account successfully.  I can also add the user successfully with Google (if I delete the user beforehand - no linking).  So, I know that these both work individually.</p>
  <p>Yet, when I create the local account and attempt to login using Google as the idp and link that, I get an error that there are no suitable claims providers found.</p>
  <p>Has anyone tried this auto-linking sample with Google and seen any tweaks I may need to Input/Output claims or other?  I have made several over the course of a couple of weekends trying to get this to work. AppInsights shows that it happens in AAD-FindLocalAccountWithSocialEmail (AzureActiveDirectoryProvider) and Exception is: No suitable claims providers were found.</p>
  <p>Any suggestions appreciated.  I can post my Google ClaimsProvider blocks if that would help diagnose.</p>