Hi,

I wonder if anyone can help please?

We are going through a migration of changing our users email domain. We currently have SSO enforced for users (Azure AD).

As the migration process will take a few weeks, I'm looking for advice on how we can migrate users from first.last@olddomain.co.uk to first.last@newdomain.co.uk with a minimum of disruption.

For the period of the migration we could revert to username/password rather than SSO as I understand we can only have a 1:1 relationship with the certs.

What I would like to understand is, is there a way a user could login say today with old email address and password and as we roll out new laptops, when they get their new one they can just login with their new email address without us having to change users primary email address in genesys with each new bunch of laptops we deploy?

I assume you got through this from over a year ago.

For others, I like to setup a secondary SSO using the API to create the same type so users can be authenticated on either domain.  Then I use a workflow that changes all the Email addresses to the new one.  Eventually, I get rid of the original one.  

Hi,

I wonder if anyone can help please?

We are going through a migration of changing our users email domain. We currently have SSO enforced for users (Azure AD).

As the migration process will take a few weeks, I'm looking for advice on how we can migrate users from first.last@olddomain.co.uk to first.last@newdomain.co.uk with a minimum of disruption.

For the period of the migration we could revert to username/password rather than SSO as I understand we can only have a 1:1 relationship with the certs.

What I would like to understand is, is there a way a user could login say today with old email address and password and as we roll out new laptops, when they get their new one they can just login with their new email address without us having to change users primary email address in genesys with each new bunch of laptops we deploy?

Thanks Robert, are you saying using the API you can setup a second ADFS/Entra/Azure SSO integration without needing to use the generic SSO one?

I assume you got through this from over a year ago.

For others, I like to setup a secondary SSO using the API to create the same type so users can be authenticated on either domain.  Then I use a workflow that changes all the Email addresses to the new one.  Eventually, I get rid of the original one.  

Hi,

I wonder if anyone can help please?

We are going through a migration of changing our users email domain. We currently have SSO enforced for users (Azure AD).

As the migration process will take a few weeks, I'm looking for advice on how we can migrate users from first.last@olddomain.co.uk to first.last@newdomain.co.uk with a minimum of disruption.

For the period of the migration we could revert to username/password rather than SSO as I understand we can only have a 1:1 relationship with the certs.

What I would like to understand is, is there a way a user could login say today with old email address and password and as we roll out new laptops, when they get their new one they can just login with their new email address without us having to change users primary email address in genesys with each new bunch of laptops we deploy?

Thanks Robert, are you saying using the API you can setup a second ADFS/Entra/Azure SSO integration without needing to use the generic SSO one?

I assume you got through this from over a year ago.

For others, I like to setup a secondary SSO using the API to create the same type so users can be authenticated on either domain.  Then I use a workflow that changes all the Email addresses to the new one.  Eventually, I get rid of the original one.  

Hi,

I wonder if anyone can help please?

We are going through a migration of changing our users email domain. We currently have SSO enforced for users (Azure AD).

As the migration process will take a few weeks, I'm looking for advice on how we can migrate users from first.last@olddomain.co.uk to first.last@newdomain.co.uk with a minimum of disruption.

For the period of the migration we could revert to username/password rather than SSO as I understand we can only have a 1:1 relationship with the certs.

What I would like to understand is, is there a way a user could login say today with old email address and password and as we roll out new laptops, when they get their new one they can just login with their new email address without us having to change users primary email address in genesys with each new bunch of laptops we deploy?

I guess answering year-old questions can have some value

Thanks Robert, are you saying using the API you can setup a second ADFS/Entra/Azure SSO integration without needing to use the generic SSO one?

I assume you got through this from over a year ago.

For others, I like to setup a secondary SSO using the API to create the same type so users can be authenticated on either domain.  Then I use a workflow that changes all the Email addresses to the new one.  Eventually, I get rid of the original one.  

Hi,

I wonder if anyone can help please?

We are going through a migration of changing our users email domain. We currently have SSO enforced for users (Azure AD).

As the migration process will take a few weeks, I'm looking for advice on how we can migrate users from first.last@olddomain.co.uk to first.last@newdomain.co.uk with a minimum of disruption.

For the period of the migration we could revert to username/password rather than SSO as I understand we can only have a 1:1 relationship with the certs.

What I would like to understand is, is there a way a user could login say today with old email address and password and as we roll out new laptops, when they get their new one they can just login with their new email address without us having to change users primary email address in genesys with each new bunch of laptops we deploy?