Forum Discussion
Standardized succession planning process in Microsoft 365?
You can probably build most of this with Microsoft 365, but I’d use Entra mainly as the source for employee and role data rather than trying to make it the succession planning system itself.
Things like job title, department, manager, hire date/tenure, etc. can come from Entra, and then Power Automate could trigger a form or workflow for the relevant employees. You could store the responses in SharePoint and use that to track nominated successors, readiness, notes, and so on. The part that gets messy is when succession planning becomes more than just “name a successor.”
You usually end up wanting multiple candidates, readiness levels, development gaps, review dates, comments, maybe 9-box data, etc. At that point SharePoint can still do it, but the setup starts getting fairly custom. I’d probably keep Entra as the source of truth for the employee attributes and handle the actual succession workflow somewhere else.
That could be SharePoint/Power Automate if you want to build it yourself, or something like Teamflect if you want that layer to already exist inside the Microsoft environment. So yes, definitely possible. I just wouldn’t store the actual succession plan as Entra attributes unless the requirement is very basic.