Dave Meyer Atlassian Team

Hi @Simon Goffaux , A domain can only be claimed by one organization at the time, so normally we would recommend sharing a single organization with an SSO configuration and simply managing the instances underneath with different admins. But if it's a strict requirement that the admin teams cannot have access to each…

Yes, we support group syncing with a number of major cloud identity providers. See https://support.atlassian.com/provisioning-users/docs/understand-user-provisioning/

Hi @Peter , You should be able to get this from my.atlassian.com. Dave

Hi @WPG , We've made quite a bit of progress since my comment from 18 months ago. The guidance on our public roadmap for this capability is Q2-Q3 of calendar year 2022.

We're working on this and will share updates on this ticket: https://jira.atlassian.com/browse/ACCESS-102

Hi @Girish_Shenoy , Any user with a seat on a product under the Jira/Confluence Enterprise plan is not considered a billable user for Atlassian Access, that's how the "inclusion" of Atlassian Access with Enterprise works. So if all 200 of your Bitbucket Premium users also have access to Jira or Confluence Cloud Enterprise,…

@David Griffiths if you have access to the SEN, you can create the support ticket under another email address and our support team will email you a recovery link.

This is correct. Removing an approved domain will simply prevent new users on @domain1.com from joining the site, it won't have impact on any existing users. I think this is what you want.

Hi @Fabian Lim , See my answer here on multiple sandboxes. I would also note that our Enterprise plan customers can add additional instances with the same users for effectively no additional cost.…

There's no special support for this right now in the Enterprise plan. Each instance can be administered and configured independently. We're working on improving project level export and import between cloud instances, which will make moving configurations easier. Targeted support for this scenario, like…

@Pramodh M yes it's something we're planning to do in some form. It's not on our public roadmap because our immediate priority for sandboxes is to improve the speed, reliability, and coverage of the data copying functionality, but we discuss it regularly. We're tracking interest…

Hi @Ryan Gibbons > Is there a way to enable Atlassian Access for a single tenant or a subset of users? Atlassian Access is a subscription for an organization, which can span many tenants, so it's not possible to enable it for a single tenant. But you can set up different authentication policies for different subsets of…

Hey @Koen Bins Yes, you can set up different authentication policies for internal users (i.e. "managed accounts" or accounts with an email address on a domain you have claimed). External users (users with accounts with an email address on a domain you cannot claim) can still be granted access to your Jira/Confluence…

Hi @Koen Bins , Unfortunately this will not work. We don't currently support SSO for users with Atlassian account email addresses on domains that you cannot verify. We recognize users based on the email address of their Atlassian account. If that email address has a domain that has been claimed by an organization, then we…

@Logan Scarpace yes, you should be able to do this. Just follow the steps for each separately https://docs.microsoft.com/en-us/azure/active-directory/saas-apps/atlassian-cloud-provisioning-tutorial https://support.atlassian.com/security-and-access-policies/docs/configure-saml-single-sign-on-with-ad-fs/ One thing to note:…

Hey @John Gilbert , Atlassian doesn't support this level of configuration on native Atlassian accounts, but every major identity provider (like Azure AD, Okta, Google, or Onelogin) does. And typically it's configurable by application (so you can set up specific policies for when users are authentication to Atlassian…

Unfortunately it's not possible to connect a single Atlassian organization to multiple identity providers (each tenant of Azure AD would be a different IdP) for SSO purposes at this time. This is on our roadmap though. In the meantime, the workaround would be to maintain two separate organizations, but this would come with…

We do have plans to address the API gaps in this area. We'll provide updates on this feature request: https://jira.atlassian.com/browse/ID-6965

Hey James, I know you saw my answer on the AMA page, but just linking to it here for clarity https://community.atlassian.com/t5/Enterprise-Questions/Re-Re-AMA-Jira-and-Confluence-Cloud-Enterprise-with-Da/qaq-p/1788326/comment-id/40#M40

Hey @Bill Sheboy , I think I actually misunderstood your question originally. I think the direct answer is that Jira automation SLAs and usage tracking is currently per-instance and we don't have any immediate plans to centralize it.

Hi @Vero Rivas , We don't currently have a vehicle for collecting feedback on the roadmap directly. The public roadmap is the outcome of all the complex roadmap decisions we make across the numerous channels through which we listen to customer feedback, plus our company and product strategies, and all the other factors…

Hey @JimmyVanAU thanks for joining! Yes we are currently running an Early Access Program for our new Atlassian Analytics, which is designed to report and visualize on product data across multiple instances. You can learn more about the program and sign up here to test drive the features and share your ideas with the team.…

Hey @Laura Holton _ACE Manchester_ We don’t have a public roadmap that we can share on specific reporting and analytics features, but we recommend signing up for the EAP mentioned on other questions to stay in the loop. I am confident that as we make concrete progress in this area, we'll share more details.

Hi @Svenja Lorenzen - Great questions Re: guest users - for our first version of external collaboration, it was important to us that these users were truly collaborators, and not just view-only readers, so they will use a paid license. We are considering an additional user role for view-only guests in the future. Re: time…

Hi @Kishan Sharma , The setup steps for SAML SSO in Cloud Enterprise (and Atlassian Access specifically, which is included at no cost for Cloud Enterprise users) will be different from Data Center. You can review this support article to learn more, specifically the section “Set up SAML single sign-on for other identity…

Hey @Huwen Arnone _Deiser_Devoteam_ , Re: enabling data residency and offline time – It’s highly variable, in many cases it takes much less than 24 hours, in rare cases it can take more. We’re actively investing in both improving the overall speed as well as the accuracy of downtime estimates. That said, the unfortunate…

Hey @John Funk , very reasonable question. Unfortunately, while we’ve invested substantially in integrating Jira Service Management and Confluence for knowledge base use-cases, it still requires a separate Confluence subscription. However we do have a free Confluence plan that can be used by up to 10 agents to help you…

Hi @Vero Rivas , thanks for the feedback. We're working hard every day to make Confluence a better product. Personally, as someone who uses Confluence Cloud all day, every day I think we've made incredible progress on the design and performance of the product. Check out the…

Hey @Brant Schroeder ! Thanks for joing. On release tracks: since Marketplace apps from third-party developers run independently from Atlassian products, in separate infrastructure, we don’t have the technical capability to bundle apps. The ability to expose the release tracks configure to Marketplace apps so that they can…

Hi @Aswin Achuthan , Yes, this is coming soon. If you are planning a large Jira Service Management Cloud deployment, I would encourage you to get in touch with team already, we can discuss how we can support you. Contact Atlassian for Enterprise Solutions