title: Does Azure B2C provide "true" single sign-on between multiple applications
body: <p>I'm currently experimenting with Azure B2C and have created a tenant that is acting as a single identity server with 2 applications registered to it (on different domains).</p>
  
  <p>The <a href="https://docs.microsoft.com/en-us/azure/active-directory-b2c/active-directory-b2c-token-session-sso" rel="nofollow noreferrer">Azure B2C documentation</a> suggests that is supports "Single sign-on (SSO) behavior across multiple apps". </p>
  
  <p>The documentation gives the following as an example:
  "once a user signs into an application, Contoso Shopping, he or she can also seamlessly sign into another one, Contoso Pharmacy, upon accessing it."</p>
  
  <p>Whilst researching the meaning of single sign-on I came across <a href="https://security.stackexchange.com/questions/13803/what-is-the-difference-between-federated-login-and-single-sign-on">a question on StackExchange</a> where an answer describes 2 meanings of the term "single sign-on":</p>
  
  <p><em>(1) the user only has to provide credentials a single time per session, and then gains access to multiple services without having to sign in again during that session. But sometimes it's used to mean</em></p>
  
  <p><em>(2) merely that the same credentials are used for multiple services; the user might have to login multiple times, but it's always the same credentials.</em></p>
  
  <p>Can anyone tell me  which of those 2 meanings is appropriate for Azure B2C? Does it or does it not provide/support "true single sign-on"?</p>
  
  <p>Thanks in advance for your help</p>