Custom Domains in Cloud - Development Update

[Aniceto Goñi Díaz de Cerio]

Totally agree with @Magnus Nordstrand 

We need absolute freedom in deciding which is the subdomain we want for our company. As I said earlier, a mandatory subdomain like wiki or support does not work for us, as we're a non-english-speaking company and need our subdomains to be in our own language.

I can understand that some of you might have enough with support.company.com, but please have in mind that other people may have a different perspective, and may need one or more (or none) subdomains, or different subdomains (support.company.com, help.company.com, ayuda.company.com, soporte.company.com, aide.company.com, client.support.company.com, or even companysupport.com)

[Dave Liao]

For those not watching the Enterprise section in Community, a new article was posted "Custom Domains in Cloud - Our Approach". (And if you're not watching the Enterprise section, go here, then click "Join group". If you see "Unwatch" on the side, you're in!) 🙌

@Luke Liu - hopefully your team has time to review the comments here - there's a lot of passionate users here! 🙏

[Jimmy Trivedi]

I'm still not able to get access for this. Does anyone get?

[Jimmy Trivedi]

I'm still not able to get access for this. Does anyone get?

[Dave Liao]

@Jimmy Trivedi - this feature is still in development, so no one has access yet. (Status = Future: https://www.atlassian.com/wac/roadmap/cloud/custom-domains?&p=fc1cebe9-4f)

[Jimmy Trivedi]

Hi @Dave Liao  But when I go to link it is saying this:

[hbunjes]

@Jimmy Trivedi It says "Future" and not "Released".

[Dave Liao]

@Jimmy Trivedi - the custom domains feature is NOT available yet.

We are all waiting eagerly… 👀 

[Jimmy Trivedi]

But why it is saying "The update "is" available, it should be The update "will be" available.

[Dave Liao]

@Jimmy Trivedi - It’s awkward wording.

If the feature was released, it would be available in those products. 😅 

[Mark_Hattersley]

Wow just googled to see how to do this very surprised how long this has been going. Not really got the time to read through it all which will likely infuriate those working on this. But surely this is just a CNAME to the existing endpoint. So customer adds what they plan to CNAME in the portal and then creates the CNAME? (i.e. confluence.acme.com. IN CNAME anm123a.atlassian.net.) Same as CDN's have been doing for years on multitenant cloud platforms.

[Matt Reiner _K15t_]

For better or for worse, we summed up the current custom domain situation, in case you want something shareable with teammates: https://www.youtube.com/shorts/FzWqjGDsiSM

[Gaber]

Please listen what we want!

https://support.acme.com or help.acme.com or portal.acme.com and knowledge.acme.com even if you limit these prefixes, but we can not understand why you need this... users do not remember 3 parts URL

[Cosmo Denger]

Echoing what everyone else said.  The subdomain keyword is limiting and a non-starter for us.  We just want services.acme.com. 

[kissinger]

Hello,

The current method is not really helping me at all... I want to make easy portals for my clients, like support.juniz.energy.
I still cannot do this - and have to find an odd naming convention... 

Plus, even worse!, I want to be able to add a CNAME entry for specific projects.
You gave me the option now to give OWN CNAME entry for the complete Atlassian Site with all projects...

I don't understand how this should help at all ... 

[Patrick Kraus]

The planned implementation of this feature request is useless.
Nobody wants this to be done the way you suggest.
This is a joke!