Your Best ERP Person Is a Single Point of Failure

Most organizations running Microsoft business apps have one. They know why the posting profile looks the way it does. They wrote the integration nobody has opened since. Nobody books a go-live in their holiday week.
Most firms treat key-person risk as a hiring problem. In an ERP estate it behaves like a control problem, and Microsoft documents most of the controls already.
What Does Key-Person Risk Look Like in an ERP Estate?
Like five dependencies that happen to share one name.
Admin access is the first. Approvals are the second. The close schedule is the third. Process knowledge is the fourth. The fifth is who owns the automations that person built.
Each fails at a different moment. That is why hiring a second person so often misses.
Who Else Can Sign In as an Admin?
Fewer than most leaders think, and Microsoft has a view on the number.
Microsoft recommends that you “assign the Global Administrator role to fewer than five people in your organization.” That is on purpose. Every extra admin widens the attack surface.
Which creates the tension. So Microsoft also recommends “two cloud-only emergency access accounts” holding the same role. They “aren’t assigned to specific individuals.” They exist for “break glass” cases where “all other administrators are accidentally locked out.”
Read that again. Microsoft has written down the day nobody who can run your tenant picks up the phone. The control exists. Has anyone created the accounts?
What Happens to Approvals When One Approver Is Away?
Less than most leaders fear, if somebody designed the workflow for it. Three controls cover it, and only one depends on the person who is away.
The first is assignment. A step can go to a Participant, which Microsoft calls “Users who are assigned to a specific group or role.” Point it at a role and the holiday stops mattering.
The second is escalation, built into the workflow. On the Time limit tab you set a Duration. Miss it, Microsoft says, and “the document is overdue.” Then “You can escalate an overdue document or automatically assign it to another user for approval.” A Use escalation path check box builds the chain, and an End action applies if nobody responds.
The third is delegation. The approver sets that one at Common > Setup > User options on the Workflow tab, with a scope and dates. Each user sets their own, so it falls to nobody.
One caution. Both hand approval rights to somebody else, so check the result against your segregation of duties rules. Microsoft notes that compliance “isn’t verified when you create a rule.”
Which Parts of the Close Sit With One Person?
Finance can answer this from a screen, which surprises most boards.
The Financial period close workspace runs it as named tasks. Microsoft defines one as work “you assign to an individual to complete as part of each closing process.” Not to a team. To a person.
That makes the exposure visible. The workspace shows “status by company, status by area, and status by person who is responsible.” That last view is a key-person risk report your controller can open today.
Dependencies make it sharper. Microsoft says “A task that is blocked by dependencies can’t be marked as completed.” So one absent owner holds up everything behind them.
You set the schedule up at General ledger > Period close > Financial period close configuration. If your close runs on a spreadsheet, that spreadsheet is the single point of failure.
Where Does the Process Knowledge Live?
In one head, mostly. It does not have to.
Task recorder captures a process as somebody performs it. One output is that process “as a Microsoft Word document that can optionally include screenshots.” Screenshots rely on a prerelease browser extension, so treat that part as preview.
Two limits matter. Since January 2026 you can only create or use task recordings in sandbox and production. And the Business process modeler page warns that “some” Lifecycle Services features “have been deprecated.”
Who Owns the Automations That Person Built?
Often nobody, once they go. The system has a word for it.
“An orphaned flow is a flow that no longer has a valid owner.” On what that means in practice, Microsoft is careful rather than alarming. Those flows “can fail if they use connections tied to that user account.”
The fix is documented. An admin opens the environment in the Power Platform admin center and looks at flows. A row with nothing in the Owners column flags one that might be orphaned, and Share assigns a new owner. Where there are many, Microsoft documents PowerShell cmdlets that assign a co-owner.
None of this happens on its own. Somebody has to go looking, and the moment is offboarding. Most firms never extended that checklist to the Power Platform.
What Should a Board Ask About Key-Person Risk?
Five questions. Each has a place to look.
- How many people hold Global Administrator, and do the emergency access accounts exist?
- Which approval workflows have no escalation path, and which approvers have no delegation rule?
- Sorted by person responsible, how concentrated is our close schedule?
- Who owns the flows we depend on, and what happens to them at offboarding?
- If our ERP lead gave notice today, what is written down, and who has tested the handover?
Question five is the one that usually has no answer.
Why Is This a Managed Services Question?
Because cover is a capacity problem, and few mid-market teams carry spare capacity.
Internal redundancy means paying for two people where the work needs one and a half. Some firms choose that. The other route is a second team that already knows the environment.
Either way the call sits with the board. People rarely nominate themselves as a point of failure.
Frequently Asked Questions
What is key-person risk in an ERP context?
Key-person risk here means one person holds access, approval rights, process knowledge or system ownership nobody else can use. It is several dependencies, not one.
How many Global Administrators should we have?
Microsoft recommends fewer than five. It also recommends two cloud-only emergency access accounts that are not tied to named people.
Can approvals be covered when someone is away?
Three ways. The step can go to a group or role. An overdue document can escalate on a time limit. And users can set their own delegation.
Can a close task be assigned to a team?
Microsoft describes a closing task as work you assign to an individual. The workspace shows status by person responsible, so concentration stays visible.
What happens to flows when their owner leaves?
Microsoft calls them orphaned flows, and says they can fail if they use connections tied to that account.
What to Settle This Quarter
Naming a successor does little on its own against key-person risk. Moving each dependency off one person is what reduces the exposure, and none of these checks takes long.
So start with the cheapest. Count your Global Administrators and check the two emergency accounts exist. Then open your close schedule by person responsible, and see how much of it carries one name.
We have written before about what happens when ERP change outruns the calendar. Key-person risk is the same problem seen through one name.
Microsoft’s documentation moves, and one tool above sits on a platform carrying a deprecation notice. Confirm the position for your own environment.
At DAX Software Solutions, our Dynamics 365 Managed Services and Application Support Services provide ongoing support, monitoring and enhancement from a team that already knows the environment. If one person is holding your ERP together, talk to our team.