I'm currently facing some serious hurdles with management regarding the migration away from legacy MFA and SSPR. Despite my repeated warnings about the impending September 30 deadline, I've yet to get the necessary approvals to proceed with the migration. Our change management process is complicated, and I need everything thoroughly documented and tested in our development tenant to get through it without issues. It's frustrating because all the risks of not migrating could potentially lead to severe consequences for me, including termination, so I can't just go ahead without green lights from above. Could anyone share some clear Microsoft documentation outlining the repercussions if we don't complete our migration by the deadline? It's causing me a lot of stress, and I'm even considering looking for another job because of it.
2 Answers
You know, you can actually extend your deadline to July 2026! Just make sure to keep that under wraps within your company, lol.
There's a Microsoft guide that explains everything you'll face. Once October hits, MFA will be handled by a new system, so if you haven't migrated, you could run into real issues with user access. They even have a wizard now to assist with the migration process and help configure everything based on your current settings. I'd suggest using that and documenting what Microsoft suggests you set up. Then, when October rolls around and things go sideways, you can tell your management you warned them.
Thanks for this! I found it, but I wish it spoke more to the management level instead of just the technical side. I might need to take some time off that week and go somewhere without cell service to avoid the chaos!
Really? Is it just a matter of calling support to request that extension?