This issue has been fixed now

It is working for us, SPF record is not required anymore, please try again and give it sometime to validate your record, once done, add your custom email and boom !!!!

SPF record lookup and validation has been disabled. See updated documentation on adding dns records to your domain provider: https://support.atlassian.com/organization-administration/docs/copy-and-add-dns-records-to-your-domain-provider/

If you face any issues, please contact support: support.atlassian.com

I have got some update from Atlassian as this would be implemented by end of this month

Arjun Ganapathy30/Sep/22 08:59 AM

 
Hello Shankar,

Hope you are doing great!!
This is a follow up to make sure you have received my previous communication. As I did not hear back, I thought I will check back with you.

I have received another update from the Product Team, and we are looking at releasing the fix before the end of October.

Best Regards,
Arjun Ganapathy
Atlassian Cloud Support

We have been waiting for some progress on this for a long time, there is a big mail chain with Atlassian but it seems they just don't understand the importance of the issue, I still get the same answer that there is no workaround, please vote this issue...I just don't understand why Atlassian cannot make it optional for those who do not want it. I got the message from network team as they just open all AWS incoming for this and this is not acceptable as well ! this is not properly designed and I think this should just be removed. Also, hope Atlassian change their priority selection of a project like voting or whatever, there is nothing Premium being a service like this, it just looses the objective of being a premium service.

Chiming in here so everyone knows there's some movement on this. We've been communicating back & forth with Atlassian on this issue in a support ticket. As it turns out, the SPF check for the root domain isn't needed at all (mail systems look at the bouncename record), so Atlassian informed us they're planning on removing the check entirely, which should hopefully eliminate the need for macro services, etc.

+1 from from our company. SPF TXT records validation presents an issue for our domain provider due to various limitations, and since it is not directly related to email addresses it would make sense to simplify domain verification for TXT and CNAME records only 

It will be helpful if this issue is available in Atlassian Documentation or Support page because we have jumped so many hoops to address the "verify your DNS domain" message, only to be told at the end that SPF macro is not supported by Atlassian. 

Should Atlassian postpone this email verification until they are able to support SPF macro?

Same here, this is a post migration to AutoSPF. AutoSPF says they support you natively, however it seems your systems do not support them. Please update this asap. Thanks!!

One more - our company is finding this out post-migration. Please provide support for SPF macros, or a way for Atlassian Support to bypass the check and get domains validated.

Our company also has the same problem. We use SPF macros in our DNS TXT record to handle the SPF limitation. I would really like to see Atlassian add support for SPF macros to validate our domain.