Custom domains for Jira and Confluence

[#1]

Update July 15, 2024: Custom domains for Confluence are now generally available on Premium and Enterprise plans. As a reminder, we also launched custom email addresses for Confluence notifications in June. 

Hi everyone,

My name is Moinak Chatterjee and I’m a Senior Group Product Manager at Atlassian. We have a few important updates on custom domains.

Custom domains for Jira and Confluence

Custom domains are now generally available for Jira and Confluence and will be available on Premium and Enterprise cloud plans. 

Custom domains are an administrative capability that allow organizations to use their own domain name to host Atlassian products. For example, using go.jira.acme.com instead of acme.atlassian.net. Using a customer-branded URL instead of an Atlassian-branded URL helps make sites more discoverable, accessible, and uniquely yours, since they’re based on the organization’s domain rather than Atlassian’s. Custom domains join the family of advanced administrative capabilities that are the foundations of our Premium offering and are also included in Enterprise plans, alongside features like sandbox and release tracks.

Custom domains for Jira Service Management help centers

For Jira Service Management (JSM) help centers, discoverability and branding are of the utmost importance so that your customers can get the help they need as quickly as possible. Custom domains for JSM help centers enable better customer service rather than better administration, which is why they will continue to be available on all paid cloud plans.

Getting started with custom domains

If you’re ready to get started with custom domains, follow these instructions. 

If you are not already using a Premium license(s), you will need to upgrade to Cloud Premium to enable custom domains for Jira or Confluence. If you’re also looking for advanced scale, security & compliance, analytics, and support, we recommend you evaluate the Cloud Enterprise plan.

URL redirects for even more flexibility

We’ve heard your feedback and understand that many of you are looking for more flexibility in how you configure custom domains, which is why we also support URL redirects.

In designing the custom domains solution, we’ve been intentional about balancing security, customization, and open collaboration. Having a two-level domain plays a critical role in making our solution resilient to potential man-in-the-middle (MITM) attacks. At this point, we do not have plans to revisit the two-level subdomain construct, but customers who would like to use a shorter URL can set up a URL redirect. If you choose to use a redirect, you can create links with a shorter, fully customized base URL that redirects your users to the full URL.

What’s next?

If you have questions about how to access or use custom domains, please raise a support ticket. 

We know many of you have given feedback about custom domains in the past. If you have additional feedback, the Atlassian Community is an open forum and we welcome you to share your candid feedback and concerns, keeping our rules of engagement in mind. We’ll be listening! But as a way to keep the dialogue productive, please note that we will prioritize addressing comments related to the functionality of custom domains and how to use them.

Best,

Moinak Chatterjee
Senior Group Product Manager, Atlassian

[Peter_DevSamurai]

Thank you for your update notice!

[vlad_puhach]

This is so cool! I love this feature. Before, it was only possible to rename instances, but still under the atlassian.com domain. Now, you can rename the entire thing!