Dave Meyer Atlassian Team

For most organizations if you had multiple Active Directory or LDAP external directories connected to your Atlassian server products, these directories would be connected to a single cloud identity provider like Azure AD as a universal directory. There's some basic architecture diagrams for how this works in Azure AD here…

Hey @Dave Mathijs We actually launched support for multiple identity provider connections for customers with our Cloud Enterprise plan last week. https://community.atlassian.com/t5/Enterprise-articles/Multiple-identity-provider-support-now-available-in-Cloud/ba-p/2093719 However, for this scenario, it's much more common to…

@Wyatt Pegram this message is triggered based on the fact that by claiming the domain, you as an administrator now have control over these users' accounts. Users will not see the popup if their account is not managed. Their account would no longer be managed if you remove the domain claim. The presence of an Access…

@Wyatt Pegram verifying a domain and claiming accounts does not require an Access subscription, so if your evaluation for Access expired without you subscribing, the state of your managed accounts would not change and you would still retain the ability to administer them (including deactivate, delete, edit, etc).

This is correct for the old user management experience. If you are on the new user management experience, the process has changed somewhat. Just follow the documentation here: https://support.atlassian.com/user-management/docs/give-users-admin-permissions/

Hi @akshay sharma , Check out this document for ADFS: https://support.atlassian.com/security-and-access-policies/docs/configure-saml-single-sign-on-with-ad-fs/ When you set up SSO for your managed accounts with Atlassian Access, it only affects how users log in. There is no change to what repos or other content their…

Thanks for pointing that out @Jeremy Cupps, I'll follow it up with our migrations team :)

Hi @Jeremy Cupps , apologies I think my phrasing from last year was a little incomplete. It's often valuable to test a data migration from server or Data Center on a separate site than the one you intend to use for production, but generally we recommend having both the "test" site and your main production site in the same…

Hi everyone, We've just posted an update on the availability of data residency. To reduce confusion, I've posted it as a replacement of the text of the original announcement. Thank you again for your patience as we worked to improve on what we know is a critical requirement for so many of our customers.

@Jair Bakhuis this thread is out of date. Users are no longer notified via email during the user claim process. https://support.atlassian.com/user-management/docs/verify-a-domain-to-manage-accounts/#Notify-claimed-user-accounts

This is correct, unfortunately :) Just to add context, we removed the ability to transfer sites to reduce risk and manage expectations as we progressively roll out the new user management experience, but we are working on a new version of the feature. Going through support is not intended to be permanent.

Hi @Justin Cziganek , We are working on an update to share next week. In the meantime, feel free to contact our support team and we will help you out. Regards, Dave

@Carlos Sancho Écija the work that we are doing to support multiple SAML and SCIM configurations for an organization will be applicable whether it's multiple connections to the same IdP or if the organization is using different IdPs. From the Atlassian perspective, it's irrelevant.

@kurby we renamed the item on our roadmap to be more clear, apologies that the original link no longer worked. Attached is a screenshot from the roadmap as of this month. We suffered some delays as we focused portions of our team on reliability improvements and are currently expecting to offer an initial solution towards…

@John Hadaway implementing SSO with Atlassian Access does not change what user accounts have permissions to access, but we do see customers misconfigure SSO and get locked out of their account. The best way to avoid this is to use authentication policies. Set up a new authentication policy to test out your SSO configure…

@James Clark yes that's the scenario this feature is intended to address.

@MartinHerren I understand the concern. We're making substantial progress and are planning to make data residency more widely available this month. If your production migration is coming up, feel free to contact our support team and we should be able to get it enabled for you relatively quickly.

We're actively working on this feature and it's in early access. Check out: https://jira.atlassian.com/browse/ACCESS-572?focusedCommentId=3005741&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-3005741

Hi @Rasmus Breyer @Florian Franke , I understand your frustration and sincerely apologize on behalf of Atlassian. We're working as quickly as possible to improve the capacity of the systems in question while also processing as many Data Residency requests as possible on an exception basis. If you need an exception, please…

Hi @Malin Rathjen , Groups that are synced from your external IdP (using the user provisioning feature) are available to be used in permission schemes just like any other group. So once the group is synced, you can assign it to the correct role following the instructions…

Hi @andy_pawl , You can make the user a member of the site-admins group on your sandbox site (or directly grant them access to the sandbox product) without making the user an org admin. Just follow the instructions here: https://support.atlassian.com/user-management/docs/update-product-access-settings/ This will allow the…

@Nathan Yang there is an explanation of "Managed accounts" here: https://support.atlassian.com/user-management/docs/what-are-managed-accounts/ Basically, any Atlassian account that was created with an email address belonging to your company will show up on the Managed Accounts list. On the Product page in user management,…

Hi @JiraYo , You can sync users from your identity provider as JSM customers without them being automatically billable in Atlassian Access. There's more information on how to set this up in the discussion thread…

Hi @Nathan Yang , If it says the account is managed and you're logging in with Google, it means the user's email address needs to be update via Google, or the administrator of the organization that configured the G Suite SSO set up with Atlassian needs to update the email address (following these instructions). It sounds…

Hey @JD Lobue , I’m not entirely sure what you mean. My best interpretation is that you’re asking if you can only allow users in a certain role to see a given field on an issue. This idea of “field-level visibility” isn’t supported in Jira and likely never will be. The most common way to work around this is to maintain two…

@JD Lobue for JSW and JSM you can do this in two ways: 1. For company-managed projects, you would change the permission scheme that a given project is using to grant the "Browse Project" permission to the role you created, and remove whichever other entities you might not want to be able to have access to the project. 2.…

Hi @Aleksandra Kakol , it's currently in early access. You can contact a member of our team to request to be enrolled. See the message here: https://jira.atlassian.com/browse/ACCESS-572?focusedCommentId=3005741&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-3005741

Fair points @Ed Letifov _TechTime - New Zealand_ 🙂

There's nothing to configure at the instance/tenant level. The SSO flow happens when a user is logging in to their Atlassian account, irrespective of their "destination." So whether a user was going to their specific Jira instance at example.atlassian.net, or to trello.com, or even to community.atlassian.com...it doesn't…

Hey Tom, It sounds like you are planning to have one or more Jira/Confluence trial instances, in addition to Atlassian Access. It's important to understand that Atlassian Access is associated with your organization, which can be the parent to multiple instances of Jira and Confluence Cloud. So what I would recommend is…