Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,462,865
Community Members
 
Community Events
176
Community Groups

Removing verified domain while retaining user provisioning

Hello, 

In our current setup we have verified our domain, and added a user provisioning to it. 

The problem we're experiencing with this is that i load close to 500 accounts with the domain, but only 70 of these should be loaded for our current setup. 

It also affects our billing, because some of these users are added to a Trello board, and are now suddenly billed! 

 

The idea now is to remove the verified domain, but RETAIN the user provisioning. 

That way i don't have 500 accounts in my system, and only the 70 i need are added to the environment. 

will the user provisioning work correctly without the verified domain? 

 

 

1 answer

1 vote

Hi,

Without domain verification, you cannot manage the users and they will become unmanaged, so provisioning via any identity provider won't work. Also, with Atlassian access there are billable accounts and non billable accounts. When you claim a domain and manage users, it doesn't necessary make all the accounts billable expect you've explicitly provided one or more applications to those users.

If that's the case, you might want to disable those 430 users since 70 are only required. However, if any of those users use your domain and have application access to one of your product within your organisation then they become billable. 

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
TAGS

Atlassian Community Events