Dave Meyer Atlassian Team

Hi @Soumyadeep Mandal - SaM , We recently increased the per instance (site) user limit for Confluence to 20,000, regardless of plan. Here’s an article on this in case you missed it. That said, we strongly recommend our Enterprise plan as the most cost-effective option to meet the complex support, reliability, and security…

Hi @Fabienne Gerhard! Thanks for joining. Currently we support up to 20,000 users per instance for Jira Software and Confluence with plans to raise this limit to 35,000 by next year. We do have a fair use policy on the speic number of instances, but we expect to be able to support any number that can be reasonably planned…

Hey @Suvradip Paul , I assume "NFRs" are "non functional requirements" ? 😄 We target the same performance and availability baselines for all instances, regardless of plan, size, or customers. Sometimes meeting these baselines requires some variation in how we utilize our infrastructure, but that’s relatively rare. We…

Hey @Bill Sheboy , We introduced the concept of an Atlassian organization, which is a “parent” for multiple Jira or Confluence instances. At the organization level, we aggregate key activities from individual instances (like user management events) into a single log, as well as changes that happen at the organization level…

Hi @James Yoon , That’s a great question. As you confirmed, we currently don’t have a specific report for the use case you mentioned. However, we plan to introduce a Data Lake, which allows cloud customers to access their Atlassian data by querying our optimized data lake with their own BI tools or extract and load that…

Hi @Alessandro Mazza The reason for the thresholds not being aligned is it’s not an apples to apples comparison. Pricing for Jira Service Management (JSM) is based on number of agents i.e. users who service customer (end-user) requests. On the other hand pricing for Confluence is based on end-users who collaborate across…

If you haven't already subscribed to Atlassian Access, verifying your domain has no licensing or billing impact. If you already have an Atlassian Access subscription, then verifying domains will result in new managed accounts being added to your default authentication policy. For Atlassian Access customers, we require that…

Hi @[deleted] , You can claim a domain and take basic actions on the users that become your managed accounts without an Atlassian Access subscription. You can see which features require an Access subscription and which don't…

Hi @Jennifer Osborn , Unfortunately removing the app in Azure AD and deleting the directory won't remove the accounts on the Atlassian side. If you remove all of these non-"users" from the app in Azure AD, then the accounts will get deactivated on the Atlassian side (so at least you won't get billed for them) If you would…

Ah, right. You can point the user to this tool to transfer their personal content to a new account under their personal email address: https://help.trello.com/article/1104-how-to-transfer-boards-to-a-new-account And then deactivate the user's account with the company address.

Hey @Ben , Nothing to worry about. The same user will still be assigned the issue. Think about it this way: * Fred is a user who has an Atlassian account where he logs in with his email address and password. He is assigned an issue. * Under the covers, the value of the "Assignee" field for that issue is populated with his…

@Matt Russell it's definitely possible. You can use groups that are synced from Azure AD just like any other group in Jira. Follow these instructions for assigning groups to top level admin roles, just click the "add group" button instead of directly assigning a user to one of the built-in…

Hi @Eric Roetenberg , Check out the instructions here: https://support.atlassian.com/user-management/docs/make-changes-to-a-managed-user-account/ This assumes that you are an administrator of the organization that claimed the email domain of the user.

I would add that if you create the second instance from www.atlassian.com then it will be provisioned as part of a separate organization by default.

Hi @Aravind Gopalakrishnan , I don't believe so. SSO and user provisioning, which are the main features Atlassian supports, are included with all plans for Azure AD: https://azure.microsoft.com/en-us/pricing/details/active-directory/

@Carmen Nadeau apologies for the confusing language. I was trying to summarize what the documentation already says, it is correct. Customers that are users in the site with Atlassian accounts with no application access can have SSO enforced, but are not billable for Atlassian Access. JSM also has a feature called…

This is correct. You can verify as many domains as you need under one organization.

Hi @Carmen Nadeau , Yes you can set up 2 organizations with separate domains and separate identity providers, and users in both organizations can access the same JSM Cloud instance for SSO purposes. The only caveats I would note are: * You can only configure SCIM user provisioning with the organization that the JSM Cloud…

@Arun Gupta Yes. Your Jira and Confluence site can have both internal and external users. The internal users will log in to their accounts using the Azure AD SSO policy that you define, while the external users will continue to login with their own credentials. Nothing about their login experience would change. > Can I…

@Arun Gupta if you have an active Atlassian Access evaluation license you should be able to to contact our support team via support.atlassian.com There are detailed instruction guides depending on your identity provider, we have links to the major ones…

Hi @Arun Gupta > Q1. We currently have multiple confluence pages, workspaces, JIRA boards, etc. How will it impact the users when we move from Standard Credentials to SSO ? Enabling SSO only affects users' login experience. There is no impact to user's actual permissions/authorization within the product or association…

Can you confirm that the email address the user has entered in the login form exactly matches the one that you see for the user on the Managed Accounts admin screen? This error can happen when SSO is enabled but a user's email address has been changed.

Hi @Mel Brooker , Try checking the "You can temporarily exclude users from two-step verification" section of the page here: https://support.atlassian.com/security-and-access-policies/docs/enforce-two-step-verification/

Hi @Hannes , For the JSM customers question, what you have configured is correct, based on the screenshot. "No product access" means members of that group are not JSM agents, (or using JSW or Confluence) but they can still be JSM customers. In your JSM global settings, make sure that public signup is disabled, so only…

If you've already created accounts in Azure AD for the users that have been invited with their personal email, the easiest way to solve the problem is to have each user change their Atlassian account email address to their company email (https://support.atlassian.com/atlassian-account/docs/manage-your-personal-profile/)…

@Catherine Svendson you only pay for accounts as part of an Atlassian Access subscription. You can claim and take basic administration actions without an Access subscription. 

Hi @Elijah Wolf , So I think your diagnosis of the problem is correct – we initially do a check on the domain to recognize that you should log in with SSO, but on the next login screen, that user doesn't actually haven an Atlassian account yet so they aren't automatically sent to the SSO provider. I think the simplest way…

Jira Service Manager customers (non-agents) do not count towards your Atlassian Access bill. There is more information here: https://support.atlassian.com/subscriptions-and-billing/docs/manage-your-bill-for-atlassian-access/

@Geert Peter as an org admin, you can edit the accounts of the managed accounts in your organization via the org administration console. We're working on integrating the site-level product access management screens and the org-level account management screens, but here are the specific instructions for editing managed…

@Heberto Lorenzo unfortunately we don't support importing into Okta via the user provisioning integration at this time. However, you should be able to export a CSV of your existing users and import that into Okta.