Example:
If we have 100 users in Azure AD for ourdomain.com, and we have 3 Atlassian Confluence sites, let's say 20 users in each site for a total of 60 licenses. Additionally, of those 60, only 40 are unique users and the extra 20 come from the same users being in multiple sites.
If I Verify ourdomain.com and Claim the users, I will have 100 users in the Managed users.
Do we now get charged for 100 licenses? Or, just the 60? Or, if all sites are added/verified to our Atlassian Organization (domain), do we get the duplicates removed and only pay for 40 licenses?
Hey @David Clark _IT Guy_ ,
Let's start with what you said. So you have three sites. These are separate entities for which you have individual subscriptions and will be billed for later. Did you come across the official pricing page for Confluence yet? Using Azure AD as an identity provider, user provisioning will require an Atlassian Access subscription. That will be paid per-user globally (organization level) afaik. For each Confluence product, you will pay the respective users who have product access. So you will pay for all users you manage using Atlassian Access and then only per site what you're using (product access). Does that answer your question? Best, Max
First, yes I'm very aware of the official pricing and how it's associated with each site.
Second, I'm aware that Atlassian Access would be needed if wanting to create automatic user provisioning between Atlassian products and Azure AD.
My initial reading on the Verify and Claim processes was not related to trying/wanting to setup automatic user provisioning.
My question was more directed as to whether the pricing structure changed at all after implementing the Verify process of a Domain and the Claiming of the associated users. From your answer, I get the impression the answer to that is No; you still pay multiple times for one user to have access to multiple sites.
Additionally, and please correct me if I'm stating this incorrectly, it seems your answer suggests that the only purpose to Verify a domain and Claim users is to create an Atlassian Organization that is then used for implementing automatic user provisioning and synchronization. If not wanting to implement the user provisioning, then there's no purpose or benefit to do so.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.