Taking over a Microsoft 365 tenant from a previous MSP: a handover checklist
When a customer changes providers, you usually inherit the same Microsoft 365 tenant, not a new one. The risk is not only missing a setting. It is also leftover partner access, unknown admin accounts, mail-forwarding rules, and devices still enrolled in someone else's management tool. This checklist is for that same-tenant handover, not a tenant-to-tenant migration.
Get access the supported way
Do not ask the customer to email you a Global Administrator password. Have the customer grant access through one of the supported paths:
- Granular delegated admin privileges (GDAP) from Partner Center, which the customer must explicitly approve. GDAP is time-bound and least-privilege: you request only the Microsoft Entra roles the work needs, not standing Global Administrator on every customer. See Microsoft's GDAP introduction.
- A customer-created account in their tenant, assigned only the admin roles required for the engagement, with MFA registered to your team and a named owner.
The customer can review and remove partner access in the Microsoft 365 admin center. Microsoft documents how a customer removes a GDAP relationship and how partners and customers manage admin privileges and reseller relationships. Walk the customer through managing partner relationships so the previous provider loses admin roles once you are in and the work is agreed.
Inventory before you change anything
Work read-only at first (Global Reader plus Security Reader covers much of this). Write down what you find. You are building a map, not "cleaning up" on day one.
| Area | What to record |
|---|---|
| Partner relationships | Every GDAP or reseller relationship, roles granted, expiry dates, and whether the previous partner still has access. |
| Privileged roles | Every Global Administrator and other privileged Entra role assignment, including guests, synced accounts, and eligible PIM assignments. Microsoft recommends fewer than five Global Administrators. |
| Emergency access | Whether two or more cloud-only break-glass accounts exist and are excluded from blocking Conditional Access policies. If they do not, create them before you change sign-in policy. See our emergency access checklist and Microsoft Learn, Manage emergency access accounts. |
| Security defaults vs Conditional Access | Which one is in effect (they cannot both be on), every Conditional Access policy, its state (on, off, report-only), and every exclusion. See security defaults vs Conditional Access. |
| Enterprise apps and consent | Apps with admin or user consent, permissions granted, and whether user consent is still open. Review and tighten using Microsoft's guidance on configuring user consent and the admin consent workflow. |
| Domains, DNS and mail flow | Accepted domains, DNS (SPF, DKIM, DMARC, Autodiscover), connectors, journal or archive rules, and transport rules. |
| Forwarding and inbox rules | Mailbox forwarding, outbound automatic forwarding policy, and transport rules that send mail outside the tenant. Use the forwarding and inbox rule audit. See email forwarding and outbound spam policies for external forwarding. |
| Devices and MDM | Join type for each device (Microsoft Entra joined, hybrid joined, or registered), current MDM authority, Intune enrollment, Autopilot profiles, and any previous third-party MDM still managing devices. Microsoft's device deployment plan and device join types explain the differences. |
| Licenses and billing | Who owns the billing (customer direct, previous CSP, or you), which licenses are assigned, and what happens to subscriptions when the reseller relationship changes. |
| Guests and shared access | Guest users from the previous partner, shared mailboxes, site owners, and Teams ownership that would break if those accounts are deleted carelessly. |
Devices: do not assume you can "convert" a join type in place
Microsoft Entra joined, hybrid joined and registered devices are different states. There is no supported push-button that converts a hybrid-joined PC into a cloud-native Entra joined device while the user keeps working on the same Windows installation. Planning a move to cloud-native endpoints is a project of its own, often involving a reset or Autopilot reprovision after user data is in OneDrive or another known location. Record the current state, keep existing management working, and schedule any join-type change as a later, communicated wave. If you will use Autopilot for new or reset devices, follow the user-driven Autopilot checklist.
If devices are still enrolled in a previous MDM, coordinate unenrollment so users are not left unmanaged, and do not wipe a device unless the customer has approved it. Intune remote actions such as retire or wipe are destructive if used on the wrong device.
Offboard the previous provider
Once your access is proven and the inventory is written down:
- Remove the previous partner's GDAP roles and, if appropriate, the reseller relationship, with the customer present or clearly approving each step.
- Disable and later delete the previous provider's guest accounts, named admin users, and any "shared" admin mailbox they used.
- Revoke refresh tokens / sign out sessions for those accounts, and review their MFA methods and app passwords if any existed.
- Remove their enterprise apps, consent grants, Exchange connectors, and forwarding rules, after you have a rollback note for each.
- Rotate secrets that they could have known: DNS registrar access is outside Microsoft 365 but often sits with the same provider; so do backup, RMM and documentation tools.
- Confirm emergency access accounts still work and that alerts fire.
Then run a security baseline and a proper audit
After handover, put the tenant on a known baseline (security defaults or a starter Conditional Access set) and run a full control review. Start with our tenant security baseline and the quarterly audit checklist. The Tenant Security Audit Kit gives you a 50-control workbook to record evidence and score what you inherited.