Thank you for posting this in Microsoft Q&A.
Based on the information provided, it seems like the issue could be related to the browser caching the previous authentication information and not redirecting to the correct IDP login screen.
Here are some potential causes:
1.When the user authenticates with the external partner's IDP, a cookie is set in the browser. This cookie might not be properly cleared when the user closes the browser or clears browser information. As a result, the application might be relying on the existing cookie, which is causing the login failure.
2.Similar to cookies, the application or IDP might be storing session information in the browser's local storage or session storage. This data could be persisting even after the user clears browser information, leading to the login failure.
3.The application or IDP might be caching authentication tokens or access tokens, which are not being properly invalidated when the user clears browser information. This could cause the application to attempt to reuse an invalid token, resulting in the login failure.
Are you using any specific authentication protocols (e.g., OAuth, SAML, OpenID Connect) with the external partner's IDP? Check the browser's developer tools (e.g., Chrome DevTools) to see if there are any errors or warnings related to cookies, sessions, or redirects.
Hope this helps. Do let us know if you any further queries.
Thanks,
Navya.