SSO using microsoft causing strange behaviour


I've been setting up SSO for a customer, as i've done many times before. But this time it's rather strange.

The behaviour i'm seeing, is, if the customer logs on using their alias email like they gets redirected to microsoft authentication, logged in, and then back to superoffice, where they are then prompted to receive a welcome email, like if the user was new - bear in mind they signed in to the user 5 minutes earlier before sso was enabled.


If i then change their username to the actual username in AD, they are prompted for their password in SuperOffice, and never redirected to the microsoft login. 

The email username is now initial based, like


But despite the domain being registered for SSO, it is not regocnized.


I used this article to set it up, like i've done many times before: 


Anyone know what i can do, and what's causing this?

9 Jan 2024 | 09:55 AM

All Replies (1)

Their UPN in Microsoft needs to match the username in SuperOffice, otherwise you get strange results. (

9 Jan 2024 | 11:59 AM

Add reply