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,458,875
Community Members
 
Community Events
176
Community Groups

Is there a way to disable E-Mail Invitation?

We already linked our Azure AD to our Confluence Cloud Instance via User-Provisioning (Atlassian Access).

The user-synchronisation works perfectly, but our users still can't log in, because there is a invitation pending.

We configered the users password in our Azure AD, our users have no postboxes, so there is no way to activate their accounts via E-Mail.

 

Is there a way to auto-activate a user-account, without the E-Mail Invitation?

 

Thanks in advance!

1 answer

1 accepted

0 votes
Answer accepted

Hello Burak,

Welcome to Atlassian Community!

When we verify a domain and use user provisioning, even if it’s linked with an Identity provider, users still need to verify the Atlassian account in order to log in.

As they don’t use an email where they can access the mailbox to finish the account creation, you will need to implement SAML on your Atlassian access, so they will be able to login using SSO and their account will be automatically verified.

Also, I can see that there is only your user with a verified domain and it’s also the only user that was provisioned, but if you try to login using this account, it will also ask for a password. Please, confirm if all domains were verified before implementing SAML.

Please, check the documentation below to set up SAML:

SAML is available for Atlassian access, so you don’t need to pay anything else to implement it.

If you have any other questions regarding this matter, please let us know.

Regards,
Angélica

Hi Angélica,

thank you very much, it is working now!!

Like Angélica Luz likes this

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events