Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

2FA note required when on an approved work site / IP?


Hi Everyone,


My company is looking to harden our Atlassian cloud subscription by employing Atlassian Access.  I want to set up IP whitelisting so when a user signs in from our workplace, MFA is not required, but when they sign on from a location away from work such as home, MFA is required. Is there a way to accomplish this using Atlassian Access?





1 answer

1 vote
Dave Meyer
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Nov 01, 2021

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 cloud).

So what you would do is use Atlassian Access to configure SAML SSO with your identity provider. Atlassian then delegates authenticatino out to the identity provider, where these controls can be enforced.

Atlassian's native features like IP allowlisting and session duration limits can then become complementary controls that ensure that a user cannot authenticate on a secure network, and then continue to use Atlassian cloud on an insecure network without re-authenticating.

Here are some sample docs from Azure AD and Okta to show you what I mean:

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events