List the people and relationships
Start with the contract dates and the services each provider operated. Ask who owns identity, mail routing, endpoint policy and alert review after cutover. An account that looks obsolete might still support an essential workflow; the reviewer needs that context before recommending removal.
Reconcile human administrators
Compare the handover list with current privileged identities and role assignments. Distinguish internal accounts used by contractors from external guest identities. For each discrepancy, identify the sponsor, operational reason and intended expiry.

Check delegated administration
Review partner administration separately from named user accounts. Removing an individual account does not establish that the commercial partner relationship or delegated privileges have ended. Request a record of the relationship, scope and business owner.

Inventory non-human access
A backup connector or reporting application can retain permissions after staff leave. Ask the assessor to link each material application to its owner, credential lifecycle and business function. Where ownership is unclear, validate dependencies before planning revocation.

Trace alerts to a person
An alert still routed to the previous provider can create a response gap even if the underlying control works. Use an agreed benign test or existing evidence to confirm that a representative notification reaches the new team and is acknowledged.

Separate removal from assurance
The independent auditor can identify residual authority; your authorised operators should own the removal plan. Test the legitimate workflow after each material change. Record what would be restored if a critical integration fails, and who can approve that action.

Ask for a handover register
Request an exception register with each access path, operational dependency and acceptance decision. Use the audit to close disagreements with evidence rather than asking the incoming provider to attest broadly that the outgoing provider has no access.

A change-of-provider acceptance test
An outgoing MSP confirms every engineer account has been disabled. Your administrator still finds an application with directory permissions and a notification rule pointing to the old service desk. These observations do not prove misuse. They identify two handover decisions that the account checklist missed: who owns the integration, and who receives an alert after hours?
| Object | Check before removal | Closure evidence |
|---|---|---|
| Former engineer identity | Is privileged access still assigned indirectly? | Dated role and group reconciliation. |
| Reporting application | Does a live operational job depend on it? | New credential owner or approved retirement. |
| Alert destination | Will the new team receive and triage it? | Agreed test event and acknowledgement. |
Published by Atlant Security. Sources, editorial policy and corrections.

