# MSP exit access log - blank working copy

Prepared by MSP Shortlist, 19 October 2026. Version 1.0.
Guide: https://mspshortlist.com/guides/msp-outsourcing-exit/#check-each-path-of-access

Use this supplement with the exit and handover log. These are proposed checks for your authorized team, not a completed access-removal test. Agree the sequence before changing live access. Keep the permitted continuity route available until its receiving owner accepts it.

## Scope and authority

Buyer, outgoing provider and exact service / package:
Client / tenant / queue / asset boundary:
Applicable agreement and approved change reference:
Action-stop owner and receiving service owner:
Agreed access-change window, timezone and fallback route:

Use non-secret identifiers and links to approved systems. Do not place passwords, API keys, tokens, raw client data or confidential attachments in this file.

## A01. Named people and application sessions

For named Entra users, agree both sign-in removal and how sessions in each downstream application end. Microsoft explains that an application's own session cookie follows that application's controls. Refresh-token revocation alone is not universal proof that every session has ended.

Ask for the affected identity, application owner, approved action, actual completion time and an authorized check of the old access path.

System, tenant and non-secret identity / relationship reference:
Accountable owner, cooperating party and replacement service owner:
Approved action, scope and change authorization:
Planned window and timezone / actual completion time:
Authorized old-path access check, observed outcome and supporting link:
Replacement access / coverage check and supporting link:
Open issue, next action, owner and due date:
Review state: Not reviewed

Manufacturer guidance, checked 19 October 2026:
- https://learn.microsoft.com/en-us/entra/identity/users/users-revoke-access

## A02. Delegated partner administration

Identify the exact customer, partner and GDAP relationship. Microsoft's customer-led process removes the administration granted through that relationship. Its FAQ separately explains that ending GDAP does not end the reseller relationship; settle subscription and commercial work independently.

Obtain the relationship confirmation and an authorized check of the agreed administrative scope. List any separately granted access that still needs its own owner and action.

System, tenant and non-secret identity / relationship reference:
Accountable owner, cooperating party and replacement service owner:
Approved action, scope and change authorization:
Planned window and timezone / actual completion time:
Authorized old-path access check, observed outcome and supporting link:
Replacement access / coverage check and supporting link:
Open issue, next action, owner and due date:
Review state: Not reviewed

Manufacturer guidance, checked 19 October 2026:
- https://learn.microsoft.com/en-us/partner-center/customers/gdap-customer-terminate
- https://learn.microsoft.com/en-us/partner-center/customers/gdap-faq

## A03. Enterprise application permissions

List each enterprise application or service principal and whether it uses delegated or application permissions. Microsoft treats these grants, user/group assignments and other authorization systems separately. Removing a current grant also does not, by itself, prevent a later consent grant.

Ask the application owner to document the agreed permission change, remaining roles, consent controls and a permitted check of the old integration. Keep the replacement integration assigned to its own owner.

System, tenant and non-secret identity / relationship reference:
Accountable owner, cooperating party and replacement service owner:
Approved action, scope and change authorization:
Planned window and timezone / actual completion time:
Authorized old-path access check, observed outcome and supporting link:
Replacement access / coverage check and supporting link:
Open issue, next action, owner and due date:
Review state: Not reviewed

Manufacturer guidance, checked 19 October 2026:
- https://learn.microsoft.com/en-us/entra/identity/enterprise-apps/manage-application-permissions

## A04. RMM, PSA and other service access

For your own systems, separately inventory RMM agents, remote-access accounts, PSA API users, service identities and vault entries used for this purchase. Ask each system owner how the old provider will stop acting while the replacement keeps the agreed coverage.

Agree the tool or agent owner, intended scope, action-stop time, approved disable or rotation step, old-path access check and replacement monitoring check. Keep an unverified path open in the plan.

System, tenant and non-secret identity / relationship reference:
Accountable owner, cooperating party and replacement service owner:
Approved action, scope and change authorization:
Planned window and timezone / actual completion time:
Authorized old-path access check, observed outcome and supporting link:
Replacement access / coverage check and supporting link:
Open issue, next action, owner and due date:
Review state: Not reviewed

## Handover decision

Decision: Not reviewed
Authorized decision maker and decision time / timezone:
Confirmed old access paths and accepting replacement owner:
Remaining access paths, owners, restrictions and next review:
Separate notice, reseller/subscription and financial work still open:

Keep earlier observations when adding a correction or a retest. An action request, termination email or elapsed wait time alone does not complete every access path. This file does not send notice, revoke permissions, remove agents or terminate subscriptions.
