Bitbucket invite emails not arriving - is my Microsoft login creating a duplicate account on the sam

[Isabella Andrews]

I'm trying to accept a Bitbucket repository invite, but the invite emails never reach me. Jira notification emails to the same address arrive without any problem, so it doesn't look like a general deliverability issue.

Some things I've noticed while troubleshooting:

• My work admin can see the invites being sent, and their logs show them arriving in my email account. Despite this, I can’t find them anywhere in my mailbox, definitely not in Junk.
• My Jira login authenticates through Atlassian directly, not through Microsoft SSO.
• When I try to sign in via Microsoft instead, Atlassian shows "We were unable to verify the email associated with your Microsoft account" and asks me to verify with a code and create an account.
• Those verification codes arrive fine, which again suggests email delivery to my address is working.
• I've already added id.atlassian.com and id.atlassian.net to my safe senders.

I can see two possible explanations. The first is that there are two separate identities on the same email address: an existing Atlassian account, and a Microsoft-linked one that isn't connected to it. If the invite is being tied to the unverified Microsoft identity, that might explain why it never lands where I can see it. The second is that my address has landed on Atlassian's suppression list after a bounce, so invites are no longer being attempted even though everything looks fine at my end.

Questions:

1. How do I link my Microsoft login to my existing Atlassian account rather than creating a new one?
2. If a duplicate account exists on the same email, how do I merge or remove it?
3. Could the invite be attached to the unverified Microsoft identity, and if so, how do I redirect it to the correct account?
4. How can I check whether my email is on the Atlassian suppression list, and how do I get it removed for Bitbucket?

Any guidance on resolving the account link so the Bitbucket invite reaches me would be appreciated.

[Nishanthini Sathiyaseelan]

Hello Isabella,

A couple of thoughts based on your description:

1. The Microsoft login isn't necessarily creating a duplicate account. The "Verify your email" screen is expected if Atlassian can't yet associate your Microsoft identity with an existing Atlassian account. Verifying the email is the first step before the identity can be linked.
2. Since verification emails arrive but Bitbucket invites don't, this points to the issue being specific to Bitbucket invitation emails rather than a general email delivery problem.
3. I would have your Bitbucket administrator verify:
   1. The invite was sent to the exact email address shown on your Atlassian account (check for aliases or different casing).
   2. Any pending invitation is revoked and resent.
   3. You're already a member of the workspace under another Atlassian account, as this can prevent a new invitation from behaving as expected.
4. Regarding the suppression list, Atlassian Support is the only party that can confirm whether an address is suppressed for invitation emails. Your workspace admin can open a support ticket requesting that they check the email suppression status if the problem persists.
5. Before creating or verifying a Microsoft-linked account, I'd also recommend checking your existing Atlassian account:
   1. Go to https://id.atlassian.com/manage-profile
   2. Confirm the email address exactly matches the invitation recipient.
   3. If your organization intends to use Microsoft SSO, ask your organization administrator whether Microsoft is configured as an identity provider for your managed account.

If the invitation still doesn't arrive after being revoked and resent, I'd recommend opening an Atlassian Support ticket. Include:

• Your Atlassian account email.
• The Bitbucket workspace name.
• Approximate timestamps when the invitations were sent.
• A screenshot of the Microsoft verification prompt.
• Confirmation that verification emails are received but Bitbucket invitation emails are not.

That information should allow Atlassian to determine whether the invitation is tied to the wrong identity, blocked by an email suppression record, or affected by another account-related issue.

Thanks,

Nisha