title: using third-party identity provider with Azure AD and MSAL.js
body: <p>I have created a Single Page Application with Angular and authentication/authorisation is managed by Azure AD. I have used MSAL.js to initiate the implicit flow.</p>
  
  <p>Everything is working fine, but now my client wants to use her own identity provider (IDP) so that users have a single point of entry for all apps (including mine). This IDP is not mainstream, it is built in-house by the client;</p>
  
  <p>I want to keep using Azure AD to manage authorisations (groups, roles...). I also want my application and its dedicated backend API to be registered in Azure AD, not in the third-party IDP.
  Azure AD should remain responsible for providing the Access Token to the SPA in order to call the API.</p>
  
  <p>Somehow, I should redirect the user to the third-party IDP login form and upon successful login it will redirect to my SPA, which should then associate the tokenID with an AzureAD account and retrieve the Access Token (I suppose I will have to create an account in Azure AD for users identified in the third-party provider) </p>
  
  <p>However I'm having a hard time figuring out how to achieve this and if it is at all possible ?</p>
  
  <p>What would be the recommended approach for this scenario ? Can I still use MSAL.js or do I have to rely on something else ? </p>