Hi Amit,
Welcome to the community!
The SSO is configured for the Atlassian Organization so if you transfer the product for the Organization that already have the SSO configured you do not need to setup a new SSO.
You can check more information about it in the following below:
Please let me know if it helps.
Best regards,
Carlos
Thanks carlos,
But what if current organization have google authentication and I want to change it to azure authentication after product transfer, is it possible to do?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Amit,
You would need to change the authentication method for the entire organization.
Unfortunately, support for multiple IDPs is work in progress, think it makes sense to watch https://www.atlassian.com/roadmap/cloud?&search=sso and https://jira.atlassian.com/browse/ACCESS-572.
Does this answer your question?
Kind regards,
Carlos
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Carlos,
Will we be able to rollback to source organization if we are not able to implement azure AD authentication after the product transfer?
Is there any chances of migration failure during product transfer?
How can admin user access the source organization for verification after completion of product transfer?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello, @Amit Sharma
SSO authentication in Atlassian Access is not to the product but to the whole Atlassian Cloud.
As such what you should do is create a test site in the target organisation, configure your SSO, test that you can access this test site i.e. prove that your Azure AD SSO works.
Then transfer.
This way your need for a rollback is significantly reduced.
Access to the products is defined by Product Access in the site – this is where you may need to replace or add Azure AD groups (if you have groups being pushed by User Provisioning from Azure AD)
As I said in my answer on your other question – there is very low risk in transfer itself.
You have to be admin in both orgs to enact the transfer. You will be able to access the target right away.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @Ed Letifov _TechTime - New Zealand_ ,
Thanks for your great response,
Can you provide me demo on Azure AD configuration?
Also a demo on step by step for product transfer
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Unless you are in New Zealand, where I represent TechTime, a Platinum Solution Partner, currently the only one with Cloud Specialization – the "demo" request should be directed to a Solution Partner near you https://partnerdirectory.atlassian.com/
Atlassian support most likely will refer you to these official Atlassian's tutorials published to Azure AD documentation site:
I suggest you also read answers I've provided here to understand how to configure SSO, and User Provisioning *correctly*, as well as touching on the point of groups and product access based on groups coming from Azure AD
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.