Dave Meyer Atlassian Team

Hi Johan, SAML SSO is supported, as is 2SV enforcement and strong password policies. As an Atlassian Access customer you also benefit from priority support. Dave

Hi @jonlasser , Our SSO offerings are tied to verified domains, so if your customers are on a different domain than your internal accounts, then it should be possible. You would create an organization, verify the domain(s) of your customers, and configure SAML SSO. This requires an Atlassian Access subscription (you can…

Hi Simon, Unfortunately we don't currently support provisioning into Bitbucket team's. You can automatically provision accounts from your identity provider using Access and users can use these accounts to log in to Bitbucket, but you will need to add them to your Bitbucket team manually. We're definitely aware that this is…

Hi @Michael Arruda yes, please create a support request and we can help you out.

@Michael Arruda what is preventing the existing organization that has already claimed the domain from configuring SAML SSO? There's nothing stopping you form claiming the domain and setting up SAML SSO, as long as the other organization is OK with you having control over all accounts on the domain.

Hi @Michael Arruda, got it. Domains can only be verified for one organization at a time. It's independent of any Jira Cloud subscriptions you might have. Organizations (and domain verification) goes across all Atlassian cloud products and services. So if Organization A has claimed example.com, all Atlassian accounts…

@Michael Arruda is this for a subdomain? You should be able to place a second TXT record for foo.example.com alongside example.com.

Hi @Brian Yanosik I recommend following the instructions here: https://confluence.atlassian.com/cloud/enable-or-disable-g-suite-integration-873918510.html We're working with Google to update and standardize their instructions. This does not require an Atlassian Access subscription. Regards, Dave

Hey James, We actually do provide an API for you, as an admin, to update users' email addresses in your organization: * You can use the organizations API to get the account IDs of members in your organization * Then you can use the user management API to update the email address of the user (you can only update one user…

Hi James, Unfortunately as best I can tell, this doesn't work. Okta does not allow users to authenticate with the secondary email. So if the user attempted to log in to with Atlassian with jane.doe@example2.com and you had verified the example2.com domain, it would certainly be redirected to Okta. However, the user would…

Hi @[deleted] If users already have an Atlassian account with the same address as their Office 365 account, the accounts are "linked" automatically – we link existing accounts and only invite new users if an existing account isn't found for a given email address. If you're setting up SAML SSO, you shouldn't expect any…

Great summary @Andy Heinzer We definitely plan to support this feature at the organization level as part of Atlassian Access in the future.

Hi @[deleted] If you can confirm with that user that her account is disabled for all Atlassian properties (for example, she can't even use it to log in to community.atlassian.com) then it means that her "differentdomain.com" Atlassian administrator has disabled her Atlassian account globally. If she knows who the Atlassian…

Hi @[deleted] Currently Atlassian Access is required to set up any kind of password policy. As a site administrator, you can prompt individual users to reset their password from the user's page, but you cannot set a password policy until you have verified your domain and configured Atlassian Access. One option would be to…

Hi @Val Terebizh , Unfortunately we haven't been able to deliver a fix for this bug yet, but you can contact Atlassian support and they will be help to resolve it for you. Don't forget that you get priority support from Atlassian as part of your Atlassian Access subscription 🙂 Regards, Dave

Hi @Kostiantyn Baran, This is a bug that we have identified. Unfortunately the only solution right now is to create a support request so that we can fix this for you. See more details here: https://jira.atlassian.com/browse/ACCESS-609 Regards, Dave Atlassian Access Product Management

@Esther Strom that's correct. Your managed accounts is just a list of all Atlassian Cloud accounts with an email address that belongs to the domain(s) that you have verified. So if you invite someone that doesn't already have an Atlassian account to your Jira, we will create an account and it will be added to your Jira…

Hi @Esther Strom, That's a great question. We're still working on improving the integration between your Managed Accounts and your Jira and Confluence products. In the meantime, you will need to re-invite them and add them to the groups. It will not create a new account as long as you use the same email address to invite…

Hi @Kevin Delord, Do I still understand correctly that SAML SSO is possible with Google as Identity Provider when using Atlassian Access and configure an "unsupported identity provider" ? Yes I believe this should be possible. It also appears that SSO + G Suite sync makes everything easier and faster, but what kind of SSO…

Hi @Kevin Delord, Unfortunately it's not possible to combine G Suite provisioning with SAML SSO. If you configure G Suite syncing, your users will also need to sign in with their Google account. To achieve both user syncing and SSO, there are two options: 1. Configure SAML SSO and use SCIM to sync users from your identity…

Hi @Jake Slack, Yes HIPAA is definitely on our radar – we don't have a timeline we can share right now but we are actively assessing the steps we need to take to offer this.

Hi @shaynec, If you add the new domain to your current G Suite organization and update the relevant users email addresses, the email address change will be synced to their Atlassian accounts. Then you can move the new domain and those users over to the new G Suite organization. Hope this helps, Dave

Hey @niles davis, If you are just creating your own trusted certificates, we don't expect any problems, but without more information about your configuration it will be difficult to diagnose the the issue. Regards, Dave

Hi @niles davis, This isn't currently possible, but it's in our backlog. We do plan to support this in the future: https://jira.atlassian.com/browse/ACCESS-115 Regards, Dave

Hi @KimHutchinson, Yes, we renamed independent projects to "next-gen projects" since I originally wrote this comment. Cheers, Dave

Hi @Andrew Hatch, Hopefully the answer to your question is pretty simple. When you create an organization (on admin.atlassian.com), sign up for Atlassian Access, and configure SAML, all your managed accounts (which you can see at admin.atlassian.com after you have verified a domain) will have SSO applied. You are…

Hi @Jesse Johnson, You can either purchase Access as a monthly or annual subscription. When I said "pay once" I meant that you only pay for each account once, regardless of the number of Atlassian products or sites a user has access to. Pricing is progressive and annual prices include a discount, there's a calculator at…

Hi @Solomon Razvan, Your question looks related to the Atlassian Marketplace license REST API. This topic is for Atlassian Access, which is a product to manage security, SSO, and users across an organization's Atlassian Cloud products. I would recommend asking your question in our developer community forum and tagging it…

Hi @Aleksey Shchukin, That's correct. Atlassian Access is the successor to our Identity Manager Early Access Program and provides SAML SSO functionality across the entire Atlassian Cloud suite. It's separate from your Jira Cloud subscription – you pay once for each user in your organization and they are continuously…

Hi @Brian R, We will provide updates on ID-6305 and ACCESS-33 when this feature is ready. Cheers, Dave