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?
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.
Hi Community! Thank you to all who joined our ongoing monthly Atlassian Access demo! We have an engaging group of attendees who asked many great questions. I’ll share a recap of frequently ask...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events