Uploaded image for project: 'Atlassian Guard'
  1. Atlassian Guard
  2. ACCESS-605

Allow Atlassian Access security policies to a subset of the managed accounts in an organization

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      May 2021 Release Update

      Hi,

      We are excited to announce that we have shipped the Authentication policies feature. You can now apply Atlassian Access security policies on a subset of managed accounts using this feature (https://www.atlassian.com/software/access/guide/elements/authentication-policies#why-apply-multiple-authentication-policies). We are still in the last leg of the rollout. If your organization doesn’t have the feature yet, file a support ticket (https://support.atlassian.com/contact/#/) and we will enable the feature for you.

       Thanks,

      The Atlassian Access team.

      Problem definition

      Currently when a domain is verified Atlassian accounts become managed accounts for all users using emails under the claimed domain. If an Atlassian Access feature such as SAML SSO or two-step verification is enabled/enforced it will impact all managed accounts across ALL Atlassian Access supported products such as Jira Software, Jira Service Desk (agents), Jira Core, Confluence, Bitbucket, Opsgenie, or Trello.

      Suggested resolution

      Org administrators must be able to apply Atlassian Access security features to a subset of the managed accounts in the organization and only pay for these accounts.

            [ACCESS-605] Allow Atlassian Access security policies to a subset of the managed accounts in an organization

            Narmada Jayasankar made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 552763 ]
            Narmada Jayasankar made changes -
            Description Original: {panel:title=May 2021 Update}
            Hi,

            We are excited to announce that we have shipped the Authentication policies feature. You can now apply Atlassian Access security policies on a subset of managed accounts using this feature ([https://www.atlassian.com/software/access/guide/elements/authentication-policies#why-apply-multiple-authentication-policies]). We are still in the last leg of the rollout. If your organization doesn’t have the feature yet, file a support ticket ([https://support.atlassian.com/contact/#/]) and we will enable the feature for you.

             Thanks,

            The Atlassian Access team.
            {panel}
            h3. Problem definition

            Currently when a domain is verified Atlassian accounts become _managed accounts_ for all users using emails under the claimed domain. If an Atlassian Access feature such as SAML SSO or two-step verification is enabled/enforced it will impact all managed accounts across *ALL* Atlassian Access supported products such as Jira Software, Jira Service Desk (agents), Jira Core, Confluence, Bitbucket, Opsgenie, or Trello.
             * Further details and clarifications are available here: [Atlassian Access for Cloud FAQs|https://www.atlassian.com/licensing/atlassian-access]

            h3. Suggested resolution

            Org administrators must be able to apply Atlassian Access security features to a subset of the managed accounts in the organization and only pay for these accounts.
            New: {panel:title=May 2021 Release Update}
            Hi,

            We are excited to announce that we have shipped the Authentication policies feature. You can now apply Atlassian Access security policies on a subset of managed accounts using this feature ([https://www.atlassian.com/software/access/guide/elements/authentication-policies#why-apply-multiple-authentication-policies]). We are still in the last leg of the rollout. If your organization doesn’t have the feature yet, file a support ticket ([https://support.atlassian.com/contact/#/]) and we will enable the feature for you.

             Thanks,

            The Atlassian Access team.
            {panel}
            h3. Problem definition

            Currently when a domain is verified Atlassian accounts become _managed accounts_ for all users using emails under the claimed domain. If an Atlassian Access feature such as SAML SSO or two-step verification is enabled/enforced it will impact all managed accounts across *ALL* Atlassian Access supported products such as Jira Software, Jira Service Desk (agents), Jira Core, Confluence, Bitbucket, Opsgenie, or Trello.
             * Further details and clarifications are available here: [Atlassian Access for Cloud FAQs|https://www.atlassian.com/licensing/atlassian-access]

            h3. Suggested resolution

            Org administrators must be able to apply Atlassian Access security features to a subset of the managed accounts in the organization and only pay for these accounts.
            Narmada Jayasankar made changes -
            Description Original: {panel:title=January 2021 Update}
            Hi Everyone,

            We are actively working to ship this solution. Our current ETA is end of April 2021. We will update this issue as soon as we make the solution generally available.

            Thank you,
             The Atlassian Access team
            {panel}
            h3. Problem definition

            Currently when a domain is verified Atlassian accounts become _managed accounts_ for all users using emails under the claimed domain. If an Atlassian Access feature such as SAML SSO or two-step verification is enabled/enforced it will impact all managed accounts across *ALL* Atlassian Access supported products such as Jira Software, Jira Service Desk (agents), Jira Core, Confluence, Bitbucket, Opsgenie, or Trello.
             * Further details and clarifications are available here: [Atlassian Access for Cloud FAQs|https://www.atlassian.com/licensing/atlassian-access]

            h3. Suggested resolution

            Org administrators must be able to apply Atlassian Access security features to a subset of the managed accounts in the organization and only pay for these accounts.
            New: {panel:title=May 2021 Update}
            Hi,

            We are excited to announce that we have shipped the Authentication policies feature. You can now apply Atlassian Access security policies on a subset of managed accounts using this feature ([https://www.atlassian.com/software/access/guide/elements/authentication-policies#why-apply-multiple-authentication-policies]). We are still in the last leg of the rollout. If your organization doesn’t have the feature yet, file a support ticket ([https://support.atlassian.com/contact/#/]) and we will enable the feature for you.

             Thanks,

            The Atlassian Access team.
            {panel}
            h3. Problem definition

            Currently when a domain is verified Atlassian accounts become _managed accounts_ for all users using emails under the claimed domain. If an Atlassian Access feature such as SAML SSO or two-step verification is enabled/enforced it will impact all managed accounts across *ALL* Atlassian Access supported products such as Jira Software, Jira Service Desk (agents), Jira Core, Confluence, Bitbucket, Opsgenie, or Trello.
             * Further details and clarifications are available here: [Atlassian Access for Cloud FAQs|https://www.atlassian.com/licensing/atlassian-access]

            h3. Suggested resolution

            Org administrators must be able to apply Atlassian Access security features to a subset of the managed accounts in the organization and only pay for these accounts.
            Narmada Jayasankar made changes -
            Resolution New: Fixed [ 1 ]
            Status Original: In Progress [ 3 ] New: Closed [ 6 ]
            Matt Shelton made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 548591 ]
            Narmada Jayasankar made changes -
            Description Original:
            {panel:title=January 2021 Update}
            Hi Everyone,

            We are actively working to ship this solution. Our current ETA is April 2021. We will update this issue as soon as we make the solution generally available.

            Thank you,
            The Atlassian Access team

            {panel}



            h3. Problem definition
            Currently when a domain is verified Atlassian accounts become _managed accounts_ for all users using emails under the claimed domain. If an Atlassian Access feature such as SAML SSO or two-step verification is enabled/enforced it will impact all managed accounts across *ALL* Atlassian Access supported products such as Jira Software, Jira Service Desk (agents), Jira Core, Confluence, Bitbucket, Opsgenie, or Trello.

            * Further details and clarifications are available here: [Atlassian Access for Cloud FAQs|https://www.atlassian.com/licensing/atlassian-access]

            h3. Suggested resolution
            Org administrators must be able to apply Atlassian Access security features to a subset of the managed accounts in the organization and only pay for these accounts.

            New: {panel:title=January 2021 Update}
            Hi Everyone,

            We are actively working to ship this solution. Our current ETA is end of April 2021. We will update this issue as soon as we make the solution generally available.

            Thank you,
             The Atlassian Access team
            {panel}
            h3. Problem definition

            Currently when a domain is verified Atlassian accounts become _managed accounts_ for all users using emails under the claimed domain. If an Atlassian Access feature such as SAML SSO or two-step verification is enabled/enforced it will impact all managed accounts across *ALL* Atlassian Access supported products such as Jira Software, Jira Service Desk (agents), Jira Core, Confluence, Bitbucket, Opsgenie, or Trello.
             * Further details and clarifications are available here: [Atlassian Access for Cloud FAQs|https://www.atlassian.com/licensing/atlassian-access]

            h3. Suggested resolution

            Org administrators must be able to apply Atlassian Access security features to a subset of the managed accounts in the organization and only pay for these accounts.
            K. Yamamoto made changes -
            Link New: This issue is related to ACCESS-88 [ ACCESS-88 ]
            Yumi Nakajima (Inactive) made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 534277 ]
            Eddie Webbinaro (Inactive) made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 527681 ]
            Narmada Jayasankar made changes -
            Link New: This issue is duplicated by ACCESS-141 [ ACCESS-141 ]

              njayasankar@atlassian.com Narmada Jayasankar
              grahimi Yahya (Inactive)
              Votes:
              64 Vote for this issue
              Watchers:
              80 Start watching this issue

                Created:
                Updated:
                Resolved: