I recently went through an acquisition and we're moving our Microsoft tenant from "[email protected]" to "[email protected]." Most of our SaaS applications are set up with Single Sign-On (SSO), and I'm looking for the best way to handle changes to the SSO configuration during this transition. I've heard there are transformation features available for SSO, but I've never actually tried them out. Any advice or suggestions would be really helpful! Also, how can I test everything before the cutover?
1 Answer
It's awesome that you're helping with the transition—it really makes everything smoother! From my experience with a similar acquisition, I recommend setting up calls with your SaaS vendors to get their support during the cutover. They can assist with remapping user IDs and ensuring a seamless switch. Download the existing access configurations to know how to set up the new ones. This way, you won’t lose any user data or profiles. If you don't care about the data, you could just create new profiles, but collaborating with vendors is usually the better route!
Totally get what you're saying! I added that just because I wanted to avoid negativity here. I've begun those vendor calls but was curious if there's anything I could handle without them. Did you ever use the transformation features with the enterprise applications?