Change Domain verification method

[Japs Almasol]

Hi All,

What is the most efficient way to change the specified domain verification in Atlassian with the least amount of downtime if any? We are using DNS verification right now and we are experiencing some issues because we cannot create the SPF records for Office 365. The TXT record for Atlassian's domain verification has the same name as the TXT record for O365's SPF, thus we're looking at changing the verification method to HTTPs.

[Riley Venable (Atlas Bench)]

The most efficient way to change the domain verification in Atlassian is to add the new HTTPs verification method and remove the DNS verification method. This can be done by adding the necessary HTTPs records to your domain provider and updating the Atlassian email domain settings to reflect the change. Once the HTTPs verification method is in place, you should no longer receive emails about DNS record mismatches. There should not be any downtime during this process.