Problem
Some customer may utilize the Microsoft UPN value (can receive emails) as their identifier when integrating with the Atlassian Access SSO and User Provisioning.

Microsoft UPN = user@domain.com
Microsoft Email = user@otherdomain.com

The Microsoft Social Login always utilizes the Microsoft Email attribute and so the end users will be logged in to a duplicate that may not be enforced with SSO on Atlassian side.

Suggestion
Allow the Microsoft Social login to be tied in with the SSO enforcement via Microsoft.

• ie. Allow the Microsoft application for social login to utilize the same identifier (ie UPN) used by the Microsoft application for SAML-SSO.