Is there a way to disable E-Mail Invitation?

[Burak_Bakir]

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!

[Dave Meyer · Accepted solution]

Hi @Carmen Nadeau ,

Yes you can set up 2 organizations with separate domains and separate identity providers, and users in both organizations can access the same JSM Cloud instance for SSO purposes.

The only caveats I would note are:

• You can only configure SCIM user provisioning with the organization that the JSM Cloud instance that is directly linked to.
• We don't currently support SSO for JSM portal-only customer accounts. (But we do support it for customers using Atlassian accounts)

[Carmen Nadeau]

I read your comment and the link document in reference in it.

Your answer surprised me and I re-read this page:

https://confluence.atlassian.com/cloudkb/saml-single-sign-on-and-provisioning-for-service-desk-customers-1027113836.html

In my mind what you are saying and what it is written is completly at the opposite. In the article it is imply that a customer do not use a licence and can be manage in Atlassian acces and can log with SSO, 

Wich one is it ? It does have an impact for us.

[Carmen Nadeau]

Those 2 pages says basically the same thing, one was for JSD and the other for JSM

https://confluence.atlassian.com/cloudkb/saml-single-sign-on-and-provisioning-for-service-desk-customers-1027113836.html

https://confluence.atlassian.com/cloudkb/configure-atlassian-access-saml-single-sign-on-and-user-provisioning-for-customer-accounts-in-jira-service-management-1038778740.html

Our employes should be able to login with SSO to the portal once their accounts exist, no?

[Dave Meyer]

@Carmen Nadeau apologies for the confusing language. I was trying to summarize what the documentation already says, it is correct.

Customers that are users in the site with Atlassian accounts with no application access can have SSO enforced, but are not billable for Atlassian Access.

JSM also has a feature called "portal-only customer accounts" that cannot use SSO today. This distinction is better explained in that second link you referenced above.

[Eurora Solutions OÜ]

I have the same question - is it possible to use SSO\SAML IdP provider only for the one of our site or organization?