Hi @Ranjitha S
Welcome to the Microsoft Q&A Platform! Thank you for asking your question here.
We will test the migration in a passive environment to see if there are any issues with OneLogin SSO before performing the actual migration.
And also ensure that all OneLogin settings are correct and updated if any changes occur, such as domain names or network settings. If any changes are necessary, we will make those changes and notify OneLogin immediately to resolve any connection issues.
To minimize risk, we run the platform in stages rather than all at once. That way, if something goes wrong, we can fix it quickly. To avoid any inconvenience to users, we will also be moving during off-peak hours.
We will check if the network settings on the new subscription are compatible with the old one. If anything changes, like DNS or IP addresses, we’ll update them and make sure everything stays connected.
During migration, we monitor login activity to capture the OneLogin event. In the event of an unexpected event, we have a backup system to restore resources quickly and reduce downtime.
Finally, we ensure that users do not lose their sessions when migrating. If necessary, we will guide them back inside so things can run smoothly.
We are confident that with careful planning and communication, the migration will go smoothly, and users will experience minimal disruption.
For reference, please review this documentation:-
https://zcusa.951200.xyz/en-us/entra/identity/app-proxy/how-to-configure-sso
If you have any further queries, do let us know.