Dave Meyer Atlassian Team

Hi @Marco Delgado , If all of the users of your service desk are internal, you can accomplish what you’re looking for using the user provisioning feature of Atlassian Access. In the organization that your Jira Service Desk site is a part of, you can set up user provisioning for all users on your domain from your identity…

Hi @Jonny Klaas , Jira and Confluence are featured apps for Microsoft Conditional App Access Control. Did you follow the instructions here? https://docs.microsoft.com/en-us/cloud-app-security/proxy-deployment-aad#portal If so, we can review this with our partners at Microsoft to understand what's going wrong. I agree…

Thanks @Peter Walker we hear your feedback and we're doing our best to offer this as soon as possible

Hi @[deleted], You can follow these instructions to transfer your products from the organization that was automatically created to the one that you have verified a domain for: https://confluence.atlassian.com/cloud/transfer-products-to-another-organization-967318518.html Cheers, Dave

Hi @Lucid Admin We don't actually support multiple external directories at this time. You can go to the "Directory" tab on the User provisioning page, click "Remove" to remove the Onelogin API key (all users and groups that have been synced from Onelogin will remain). Then you can generate a new API key to use with Okta…

Hi @David Zahler Are the email addresses for those that have created their accounts via social accounts on your domain? Unfortunately SSO will not work for users that are not managed (i.e., not on your domain).

Hi Tony, Can you confirm that the users that are asked to enter a password have account email addresses on the domain you have verified? If you have enabled SAML SSO, users should always be directed to your SSO provider if they are one of your managed accounts. If this isn't the case, I recommend contacting support. Dave

Hi @Rohan Bardekar Did you follow the instructions here to create your API key? It's important to note that the API key for the admin API is not the same as the ones you create under your Atlassian account.

Hi @Fred Padilla Go to admin.atlassian.com and click the name of your organization. Then you should find the Settings menu item.

Great question @Keri Miriello ! We've designed identity and user management in Atlassian cloud products with native cloud standards top of mind. Since Crowd was designed for on-premises software, it's not available for our cloud products. Crowd provides single sign on across multiple Atlassian server products. With…

Hi @[deleted], That’s a very fair question. Frankly, we’re not where we would like to be in terms of user management across all our cloud products. Just to be clear, we support a number of free capabilities today: any admin can create an organization and verify a domain. This gives you visibility into who has an account at…

Hi @Chris_Naurois! That’s a tough one. The answer is probably not in the short term – we’ve worked hard on supporting user impersonation for Atlassian Connect apps and 3-legged OAuth (3LO) for Jira, however these implementations are tightly tied to Atlassian accounts. In all honesty, I don’t think we’ve seen enough demand…

Never say never @Chris Johnson 🙂 Realistically, Atlassian Access was designed from the ground up on top of Atlassian’s global identity system of Atlassian accounts. For the Data Center editions of our products (Jira Software, Jira Service Desk, Confluence, Bitbucket, Crowd) that support SAML SSO, we’ve discussed…

Hey @Andy - PTC Redundant, The most important update is around encryption. We now offer encryption at rest and in transit for our cloud products. Data drives on servers holding customer data and attachments in Jira Software Cloud, Jira Service Desk Cloud, Jira Core Cloud, Confluence Cloud, Statuspage, OpsGenie, and Trello…

Hi @Jarek Krochmalski Fair question. Currently user provisioning and group sync from external identity providers such as Azure AD requires an Access subscription. Our syncing is based on Atlassian’s implementation of the SCIM protocol. This API and the integrations that identity providers have built with it are only…

Great question @Sam Caldwell. We have considered TLS certificates and may go down this route in the future. We’re following a “walk before you run approach”: * Support a network-based perimeter based on IP addresses. This is commonly known as IP whitelisting. We already support this for Bitbucket Cloud and we have started…

Hi @Kevin Dietz, Unfortunately this won't work – once you enable SSO for your organization, it will apply to all accounts on any domains you have claimed. What we recommend is first verifying a subdomain (like test.yourdomain.com, or just another domain entirely), then setting up a user in Azure AD on that subdomain, then…

Hi @Sarah Dawson I'm not sure I understand your question. An organization allows you to see Atlassian users and products in one place, but your tickets are for an individual Jira Cloud instance. You can follow the instructions here to make sure your Jira Cloud instance is linked to your organization:

Hi @Carlos Paternain I would recommend contacting our support team if you continue to experience this issue. Sometimes you may need to refresh the page a few seconds after clicking 'remove'.

Hi @Francis Vidal Not at this time. Once SSO is enabled, all managed accounts under your organization will login via your configured SSO provider. Regards, Dave

Hi @Darryl St. Pierre I lead Premium editions across all products at Atlassian. I would love to chat with you in more detail about your decision making process around Premium and what is coming in Jira Software Premium. If you email me at dmeyer@atlassian.com, we can set up a time. Cheers, Dave

Hey Neil, This might be a better suggestion for Okta, as they control the behavior of the Atlassian application on the Okta dashboard. We have raised the limitations of the current Atlassian tile with them but don’t have a timeline on a potential solution. The best solution today is to set up a bookmark app for that points…

Hi Harry, Apologies for the delay in getting back to you. Yes, you’re correct that creating a separate test site won’t have any effect since SAML is configured for your organization based on n the domains that you have claimed. Our recommended method for testing is to verify a test domain for your organization, like…

Hi David, No, Atlassian Access doesn't include any IP-based access restrictions today; however, we are listening carefully and evaluating how we could support this in the future. Follow https://jira.atlassian.com/browse/CLOUD-2636 to receive updates. Most customers I've spoken with implement this through their SSO…

No need to apologize. If you currently have G Suite login enabled and you disable it, users will log in with their Atlassian account password. If a user has only ever logged into their Atlassian account via Google, they might not have set one. If that's the case, they can simply click "Forgot password?" on the login screen…

Hi @Alan Zall , If you allow your domain to become unverified, your "Managed accounts" will no longer be managed. The users will be able to change their email addresses, but you must verify the new domain to manager their accounts again. If you can verify both the current domain and new domain, then you can change the…

Hi @Marlo Atlassian Account, if you have configured Site Access to allow any user to join the site from the domain, you should not need to delete existing users. However it is a "just-in-time" joining, so users need to actually visit the site for the first time before they will be added. You can assign them manually by…

@Patrik Fontana Users are notified when you verify a domain, but not when you enable SSO. However, in order to enable SSO, you must first verify the domain, and once you have verified the domain, you have access to all user email addresses on that domain (and that will be covered by your SSO configuration). This gives you…

@Johan Eckerstrom - {Eficode} we use Atlassian cloud to refer as a generic term to refer to all of our hosted products, including Jira Software Cloud, Jira Service Desk Cloud, Jira Core Cloud, Confluence Cloud, Bitbucket Cloud, Trello, Opsgenie, and Statuspage.

Hi @Joel Hasan, Unfortunately it's not possible to progressively enable SSO. Once you enable your SSO configuration, all user login attempts will be delegated to your SSO provider. However, users' local Atlassian account passwords are not deleted. If you were to disable your SSO provider, users could once again log in…