Changes to the sending domain and IP-addresses for critical emails

[#1]

TL/DR

We are in the process of changing the sending domain for email notifications that are currently sent from am.atlassian.com. Some will migrate to id.atlassian.com and some to atlassian.net.

The change will be rolled out to selected domains for further testing during May 2024 and ramp up to all recipients during June 2024.

Depending on the way receiving domains are configured this may result in emails being marked as spam.

What do I need to do?

When sending emails from a new domain or new IP address(es), there is a risk that the receiving mail servers or inbox provider will not recognise the email as legitimate and classify them as spam - to ensure this does not happen, the domain and IP address(es) can be added to your allow list.

Why are we doing this?

We want to ensure that account management related emails (e.g. password resets, 2-factor authentication 2FA) are sent via a separate sending domain and IP addresses.

How are we doing this?

We are moving sending of account management emails (e.g. password resets, 2FA) from am.atlassian.com to a new sub-domain id.atlassian.com with a dedicated pool of IP addresses.

Other emails (e.g. invitations) will move to atlassian.net. If the email has a tenant scope, it will be sent from either <tenant>.atlassian.net otherwise from id.atlassian.net.

The change will not introduce IP addresses beyond the ones listed on IP addresses and domains for Atlassian cloud products | Outbound-email.

The change will be rolled out gradually to allow receiving systems to adopt the change.

Before		After
Domain	IP address	Domain	IP address
am.atlassian.com	156.70.150.16 156.70.150.17 156.70.150.19	id.atlassian.net <tenant>.atlassian.net	156.70.150.16 156.70.150.17 156.70.150.19
		id.atlassian.com	192.174.81.97 192.174.81.101 192.174.81.103

For any further questions or support, we request that you open a support ticket.

Thank you
The Identity Team