title: What does <IncludeInSso> actually do in an Azure B2C custom policy?
body: <p>In the documentation for Azure B2C policies, under SSO session (<a href="https://docs.microsoft.com/en-au/azure/active-directory-b2c/active-directory-b2c-reference-sso-custom" rel="nofollow noreferrer">https://docs.microsoft.com/en-au/azure/active-directory-b2c/active-directory-b2c-reference-sso-custom</a>) there is no mention of the element  which is available under technical policies.</p>
  
  <p>Yet, in the starter pack code (eg. <a href="https://github.com/Azure-Samples/active-directory-b2c-custom-policy-starterpack/blob/master/SocialAndLocalAccountsWithMfa/TrustFrameworkBase.xml" rel="nofollow noreferrer">https://github.com/Azure-Samples/active-directory-b2c-custom-policy-starterpack/blob/master/SocialAndLocalAccountsWithMfa/TrustFrameworkBase.xml</a>) the element is used throughout.</p>
  
  <p>Under the reference documentation for TechnicalProfiles, the  element is not even mentioned (<a href="https://docs.microsoft.com/en-au/azure/active-directory-b2c/technicalprofiles" rel="nofollow noreferrer">https://docs.microsoft.com/en-au/azure/active-directory-b2c/technicalprofiles</a>)</p>
  
  <p>Does anyone know what the element actually does?  My guess is that it prevents that technical profile from using an existing session, but under what scenarios should I use it and which I shouldn't?</p>