Login - email not recognized

Question

Until today I could log in to Jira. But today it does not recognize my GM email. Then I thought it could be my personal they have on file. So I entered my person email. But no lock. I spend more time updating Jira than the actual issue. I wish it could be better.

Josh · Answer

When Jira suddenly “doesn’t recognize” an email that worked yesterday, it’s almost always the Atlassian account side (id.atlassian.com), not the project.

Try this sequence:

* Go directly to id.atlassian.com and attempt login with the Google/work email you used before (use “Log in with Google” if that’s how the account was created — typing the address into the password form can look like “not recognized” for SSO/Google accounts).
* If Google login works but the site still rejects you, you may have lost site access (admin removed you) while the Atlassian account still exists — ask a site admin to check admin.atlassian.com → Directory → Users.
* If neither work/personal email works, use “Can’t log in” / account recovery on id.atlassian.com with every address you might have used; Atlassian accounts are per email and don’t always merge.
* Corporate Google Workspace changes (alias, suspended user, forced SSO) also break recognition overnight — your IT admin is the other place to check.

Once you can open id.atlassian.com and see your profile, browse to the Jira site URL again; if access was removed, only an admin can re-add you.

Anwesha Pan · Answer

Hi @Jawed Asrar👋🏻

You could try the below steps to resolve the issue:

* Clear cache to remove the conflict between a personal Atlassian account and a corporate identity & then retry to login.
* Use Incognito browser:* Open a Private / Incognito window.
* Go directly to your organization’s dedicated URL (e.g., https://<your-company>.atlassian.net or https://id.atlassian.com).
* Enter your corporate email directly.
* If your organization uses SSO (Okta, Azure AD, Ping), it should immediately redirect you to your company’s login portal rather than asking for an Atlassian password.

* Launch Jira from Your Company SSO / Apps Dashboard* Instead of starting at jira.atlassian.com or id.atlassian.com:
* Log into your corporate application dashboard (e.g., Okta, Microsoft My Apps / Azure Portal, or internal intranet launchpad).
* Find the Jira / Atlassian Cloud tile and launch it from there.
* Why this works: This forces the identity provider (IdP) to push a fresh SAML token directly to Atlassian, bypassing manual email lookup errors.

If the above steps do not resolve the issue, please contact your internal IT/ Atlassian Admin team.

I hope this helps & resolves your issue. 🙂

Thanks,

Anwesha