Domain-based login flow made account inaccessible

[Ryan Govostes]

Previously, we had a service account user@domain.edu. This is an e-mail alias that forwards to our development team.

At some point, Atlassian began intercepting logins ending with @domain.edu and sending them to Microsoft's login flow.

So when I try to sign into our user@domain.edu account, it authenticates against Entera ID, where no such account exists because, as stated, this is just an e-mail alias.

Effectively we have been locked out of our account by this change. I don't see a way to continue using our old password based sign-in.

[Arkadiusz Wroblewski · Accepted solution]

Hello and welcome to the Community @Ryan Govostes 

Are you Org Admin ?

The issue here is that Microsoft can’t authenticate a simple forwarding alias. For SSO to work, there has to be a real, login-capable identity behind that address in Entra ID.

You’ll need to have your admin either create a legitimate account for that email in Entra, update the Atlassian email to a real address, or move the account to an authentication policy that doesn’t enforce SSO. Once a domain is claimed, those "ghost" alias accounts won't function properly because they need a real home in your identity provider to pass the authentication check.