nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Creating organizations accidentally

Veronika Makendzhieva

Hello, everyone!

I have the following question: sometimes my customers accidentally create organizations while trying to log in to the portal. These sites are usually free, but since Guard is used on this instance, the costs add up.

Currently, I delete these manually, but I am looking for a more permanent solution, such as restricting customers from creating such sites.

Do you have any experience with this?

Accepted answers

Arkadiusz Wroblewski

Hello @Veronika Makendzhieva

It depends on your plan.

If your organization has the Enterprise app-request controls, you can change the setting to Require admin review in Atlassian Administration → Apps → Shadow IT → Shadow IT controls. That is the closest thing to a permanent prevention mechanism.

If you are only on Premium (Thats your Use Case) + Guard, I do not see Atlassian documenting that same control as generally available there, so I would not assume you can fully block it in the same way.

Enterprise = review/limit is possible
Premium = as you see, greyed out

2026-03-24 10_06_33-Greenshot.png

All comments

Arkadiusz Wroblewski

Hello @Veronika Makendzhieva

It depends on your plan.

Enterprise = review/limit is possible
Premium = as you see, greyed out

2026-03-24 10_06_33-Greenshot.png

Veronika Makendzhieva

Hi Arkadiusz Wroblewski,

Thank you for you reply.

Yes, the instance in on Premium.
Is there any way through Azure policy that I can restrict this?

Arkadiusz Wroblewski

@Veronika Makendzhieva

Not really. Azure controls the provisioning flow, but not the app creation itself.

The easiest approach would probably be to tighten your provisioning policy. If you’re referring to Azure, I assume your users are being provisioned from your side.

On the Entra side, you can reduce the SCIM provisioning scope so that only the users and groups that really need to be managed in Atlassian are synced.

Veronika Makendzhieva

Ok, thank you.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-service-management-cloud

jira-service-management