This doesn't really solve the issue...

498c3fe158a3 correct, this first cut at the issue works for one unit operating on a shared domain, but still locks a domain to a single org when verification is done. We are exploring what the next phase might look like and how to add additional flexibility for customers like you - I'm forwarding your comments to the team.

Hi @radydeano, I work for USC and i just opened an issue which might interest you.

https://jira.atlassian.com/browse/ACCESS-1450

@jonathan Yu  Thank you for making the change however I am trying to make sense of the change because we have this scenario where we have multiple organizations for a single domain and we want the individual organization to claim the account separately. I tried the change but it only allow one organization to claim a domain.

For Example, the institution has domain x.edu 
Org1 has 80 accounts and billed separetely

Org 2 has 10 accounts and billed separately

Org 3 has 20 accounts and billed separately

So Org1 claimed the domain x.edu and then claim 80 accounts.

Org2 and Org 3 tried to claim the domain x.edu so that they can claim their individual accounts but was unsuccessful. Jira would complaint that the domain x.edu has already been claimed.

So my question is, how do i claim the domain for Org2 and Org3?

We're pleased to announce that the ability to selectively claim specific users on a domain (instead of all users at once) is now available to all Atlassian Cloud organizations!

When proceeding with a domain claim, admins will now see an option to upload a CSV file with a specific set of users to claim on a verified domain. Detailed documentation on usage of the feature can be found here: https://support.atlassian.com/user-management/docs/verify-a-domain-to-manage-accounts/

Please can you add me to the pool of customers. The ability to do this will enable us to keep the tool, otherwise it will become too expensive. Thanks

any eta? if not please add us too to the pool

We at ucsd.edu would like this too.

rady.atlassian.net (rady.ucsd.edu) and ucsdlibrary.atlassian.net got swept up when our main campus instance was migrated this week, and we've been running in the cloud since last Summer for Rady and for a couple of years for the Libraries.

Other cloud service providers handle this much more elegantly than the all-or nothing setup we've got now.  

I'd understand it if I was trying to take advantage of services that required a 'verified' domain setup, but we purposely did not choose to use those features for that reason.

@Jonathon Yu, i am with PwC and we have been waiting for this feature for the last 1-2 years. Please add us to the pool of customers with access. Thank you!

0cafa6498e3c we started rollout early December, but have proceeded cautiously because 1) that intersected with the holiday and new year period and 2) the changes involved in making this happen are enormously complex on the backend, with many intersecting affected systems.

If you're eager to make use of the feature or otherwise need it urgently, please reach out and I can add you to the pool of customers with access. Otherwise, I expect we will reach 100% availability sometime soon in the coming weeks.