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

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

Avatar

1 badge earned

Collect

Participate in fun challenges

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

Challenges
Coins

Gift kudos to your peers

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

Recognition
Ribbon

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!

Leaderboard

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
4,414,377
Community Members
 
Community Events
170
Community Groups

SSO using Microsoft Account

We're in the process of migrating our on premise Confluence server environment to Atlassian Cloud. Currently we use Okta as our identify provider for logging into Microsoft 365. When logging into Atlassian cloud we're presented with the option to use a Microsoft account to login. When this option is selected I'm able to to enter my same credentials I use to log into Microsoft 365.

I'm then redirected to our Okta page just as I am when logging into M365. After my creds are entered and I verify my identify via the okta app, I'm then able to access Confluence cloud. Atlassian Access has not been configured at all but SSO via Okta seems to be working just fine. So my question is, does Atlassian Access also need to have Okta configured as an identity provider?

0 comments

Comment

Log in or Sign up to comment
TAGS

Atlassian Community Events