Qlik Cloud/Enterprise Saas - Changing O365 Tenant for IdP.

[jmcy2408]

Hi,

Our business is moving to a new O365 tenant in the coming months  (aligning all child companies under a single parent company) and we are currently authentication users using Azure AD on our current tenant (specific to our company).

What implications / setup requirements will be needed by us to be able to authenticate users on our new tenant when this becomes available?  Also how does it work with existing users, Tenant Admin, Ownerships etc.

We are due to have a test build of our new tenant next week, are we able to have multiple IdP's  active at one time?

I'm not and IT person by any means so if this is going to be a problem then we need to know sooner rather than later so we can engage external support.

Thanks

[Vinay_B]

Hi @jmcy2408,

I am not sure what you mean by O365 tenant. Do you mean integrating Qlik Cloud with your Outlook for login?

Currently at any given point of time, a Single IDP can be active. If users are across different IDP then you would need to merge them under a single IDP or use Qlik Account to login.

FYI: https://help.qlik.com/en-US/cloud-services/Subsystems/Hub/Content/Sense_Hub/Admin/mc-create-idp-conf...

Tenant admin process is same and if you need to update the tenant admin then out customer support team assist on changing the admin. 

FYI: https://community.qlik.com/t5/Knowledge/Qlik-Cloud-Services-Service-Account-Owner-and-Tenant-Admin-F...

I hope this helps!

[Leigh_Kennedy]

You can not configure multiple IDPs at once, but this is generally not the best approach for this anyway.  What you probably want to look at is federation.  This is where the multiple backend domains are federated at the IDP level.  Many IDPs support this, including Azure AD.  

In terms of user migration, as long as the email address is the same, it should be handled automatically.  This is covered in #2 here: https://help.qlik.com/en-US/cloud-services/Subsystems/Hub/Content/Sense_Hub/Admin/mc-change-corporat...

If the email address is not the same, then there will be treated as new users.  I would recommend speaking to your Azure AD experts about this first as most of the work here is on the Azure side.

Regards.