I don't want to link the company domain, but do want security features.

[Atom Coffman]

We have a small team with a niche usecase for a disconnected cloud instance for issue tracking and documentation. Everything works well, but we do not have the ability to enforce 2FA, set a password policy, or retrieve access audit logging. That is a problem for us. There is an option to add "Atlassian Access" to our JIRA software/confluence Premium plans, but it looks like it requires the domain from our email addresses, which we don't want to merge with our Enterprise tenant. Any idea's how we can get around the domain linking?

Thanks!

[jeremiah_landi]

@Lianghai Xie(Atom) Why do you not want to link the email and the JIRA instance? Is it a rights based issue or something else (eg. may I gain some context to the reason)?

I would assume the answer you will get is similar to what @Angélica Luz has listed previously with a similar question but I am not Atlassian and ... my "no" probably doesn't carry the same weight.

• Use MFA without purchasing Atlassian Access
• Enforce security policies for users not on verified domains (On Road Map Q4 22')
• Enforcing 2 factor authentication without claiming domain (DUP)
• 2FA / MFA

[Atom Coffman]

We "could" potentially link the domain, if we know that it will maintain a separation between our niche instance and the enterprise instance, but I do not see those details in the documentation. We want this completely independent to the Orgs Enterprise license and administration.