Every week I'm finding Doman users have created a new organisation, added products and started trials. If it wasn't for the email notifications I receive as an Atlassian admin these things would go unnoticed. I then have to join that new organization, kick the users off, delete all the product trials, wait 30 days for the deletion period and then follow up in 30 days to make sure it has been deleted or needs further attention. It's insane that I cannot restrict users from having this ability. I see why from Atlassian's view is that having domain users with tis ability encourages a wider use or a wider range of product possibility. 

Please Atlassian, we already pay for premium products, pay for add-ons, we control our domain, we control our security, our internal and external users, yet any domain user can come in and create their own space/organisation and add multiple products

Joining the chorus of folks who think it's unacceptable that this feature does not already exist.  It is also unacceptable how I have to create a support ticket to try to expedite deletion of these incorrectly created organizations AND I also have to have sustained back and forth with support folks to convince them that I need these deleted faster.  "We recommend users manage deletion themselves" but we can't just outright delete them.  How can you implement a feature that requires 15 seconds of errant clicking by clueless users but multiple hours of sustained effort from administrators to remove?

Seems pretty ridiculous that issue was brought to attention over two years ago and there still has not been a remedy to it. A lot of companies who use your products are not big enough to want to use the enterprise plan. We are currently using Premium Jira and Confluence and Atlassian Guard. We should be able to stop our managed accounts from being able to create new "apps". 

This has been an ongoing issue for our Organization. Enterprise licensing requires 800+ user seat counts. This is costing everyone time and money including Atlassian support. This flaw seems like its only purpose is to artificially inflate Atlassians new account numbers for its investor conferences.

Totally agree ff86e46de495 . It seem$ an excu$e to get more $$$ (on enterpri$e $ub$cription or on product$ user$ can create without admin permi$$ion)

ff86e46de495 , you are 100% correct!

We are paying high 5 figures per year to Atlassian for various products (including guard), with most saas vendors this qualifies as enterprise-level and provides a way to protect users from creating unrelated products. It feels unfair we have to buy all underlying subscriptions to enterprise level to get this very basic security feature working. Not to mention that people do this out of confusion, not because they wanted a new confluence setup.

This issue NEEDS to be addressed. It is a constant bad experience for admins and the people that (mostly) inadvertently create the organization.

The answer cannot be "simply purchase the enterprise version of every Atlassian product your company uses to prevent this from happening." It is unrealistic.

This should be a standard feature especially when you pay for Guard and have control/management of a domain.

Adding to the long list of persons wishing they didn't have to regularly clean their organizations....