SMSMC Blog

Changing MSPs: getting the admin accounts, domain and backups back before the old provider leaves

A step-by-step plan for leaving an MSP without losing access to your own systems: inventory, emergency admin accounts, Microsoft 365 partner roles, the domain, backups and remote tools.

By Jim Venuto

The handover that goes wrong

A dental group decides to change IT providers after a slow year of tickets. It gives the old MSP 30 days’ notice as the contract requires and signs with a new one. On day 31 the new MSP asks for the Microsoft 365 global admin login, the firewall password and the backup console. The old MSP sends a spreadsheet with half of them. The domain registrar account is in the old MSP’s name. The backups run to the old provider’s cloud storage, under its own account. Nobody is acting in bad faith; the old provider simply set things up the way that was easiest to manage across all its clients.

Leaving an MSP is a normal business decision. It becomes a security problem when the business discovers that its own systems are owned, in practice, by the provider it is leaving. CISA’s 2021 guidance for small and mid-sized businesses that use MSPs addresses the underlying issue: understand the supply chain risk your MSP brings, make sure MSP accounts are limited to what they manage and disabled when not in use, and write contracts that cover security controls, logging of provider-managed systems and notice of security incidents. A planned exit tests all of that at once.

The plan below assumes a friendly exit. If the relationship is strained, also finish step 2 before you give notice.

Step 1: build the inventory before giving notice

List every system the MSP touches and, for each one, who holds the owner or administrator account. Use invoices, the MSP’s monthly reports and your own memory. At minimum:

  • Microsoft 365 or Google Workspace, and any Azure or AWS accounts
  • Domain registrar and DNS host
  • Firewall, Wi-Fi controllers and switches
  • Backup software and where the backups are stored
  • Endpoint protection and device management consoles
  • Remote monitoring and management (RMM) and remote access tools installed on your computers
  • Line-of-business applications with admin users the MSP created
  • Software licenses: whether they are in your name or bought through the MSP

For each one, write down whose name the account is in, which email address receives recovery messages, and which phone or device approves sign-ins.

Step 2: create admin access that belongs to you

Before anything else changes, make sure the business can sign in to its own systems without the MSP.

For Microsoft 365, Microsoft’s emergency access guidance is a good model. It recommends two or more cloud-only emergency access accounts on the onmicrosoft.com domain, not tied to any individual and not connected to anyone’s phone, protected with phishing-resistant authentication such as a FIDO2 passkey, excluded from Conditional Access policies that block sign-in, monitored with alerts, stored in separate secure locations, and tested at least every 90 days and whenever IT staff change. Microsoft lists “the person with the most recent Global Administrator access leaves” among the situations these accounts exist for, and an outgoing MSP fits that description.

Do the same for the firewall and the backup console: a company-owned admin account, stored in your password vault, tested before the transition date.

Step 3: review the MSP’s access to Microsoft 365

Many MSPs administer Microsoft 365 through Microsoft’s partner program. In the Microsoft 365 admin center, Settings, Partner relationships shows which partners you have a relationship with and what roles they hold. Microsoft recommends reviewing those privileges quarterly in any case.

When the new provider is ready, remove the old provider’s roles there: select the partner’s Reseller row, choose Remove roles, then Yes. Microsoft says that after a customer removes a partner’s granular delegated admin relationship, the users in the partner’s mapped security group no longer have access to administer services, and both sides receive a confirmation email. Microsoft also cautions that even with the Global Administrator role removed, a reseller partner can still make purchases on your behalf, so ask them to remove that ability. If licenses are billed through the old MSP, agree on the license transfer before you cut access, so nothing lapses.

Also check for ordinary user accounts the MSP created for its technicians inside your tenant, and disable them on the transition date.

Step 4: take control of the domain

The domain is how your email and website work and how many password resets reach you. Log in to the registrar together with the old MSP and confirm that the registrant is your company, that the account recovery email is a mailbox you control, and that a second person in your business has access. If the domain sits inside the MSP’s own registrar account, it will need to move to an account of yours.

ICANN’s transfer policy explains how a move works: a transfer requires an authorization code from the current registrar, and registrars may deny a transfer in certain windows, including within 60 days of a change to the registrant’s contact information, unless the registrar offers an opt-out. ICANN’s Board adopted revised transfer rules in June 2026 that will change these locks once they take effect, so ask the registrar which rules apply before you change contact details, and start this step early so a lock does not land on your transition date.

Step 5: make sure the backups are yours

Ask three questions in writing:

  1. Where are our backups stored, and whose account owns that storage?
  2. Will the backups be kept, exported or deleted when the contract ends, and when?
  3. Can we restore from them without your software?

If the answer to the first is “our account,” arrange for a full copy in storage you or the new provider own, and test a restore before the old service ends. CISA’s guidance for small businesses says to perform and test backups, including regular partial and full restores. A backup you can no longer reach after the contract ends cannot be restored.

Step 6: remove the old tools from your computers

The old MSP’s RMM agent and remote access tools stay on your computers until someone removes them. CISA, the NSA and MS-ISAC recommend auditing which remote access tools are in use and authorized, and using application controls to stop unauthorized ones from installing or running. After the transition, the old provider’s tools fall into the unauthorized group.

Ask the new provider to confirm, device by device, that the old agent is gone and that its own tools are the only remote access left.

Step 7: close out and rotate

On the transition date:

  • Disable every account the old MSP used, in every system on your inventory.
  • Change shared passwords the old provider knew: Wi-Fi, firewall, service accounts and any shared logins.
  • Review sign-in logs a week later for any use of old accounts.
  • Collect the documentation you are owed under the contract: network diagrams, configurations, licensing records.

Put it in the next contract

The easiest exit is the one written into the contract at the start. Ask the new provider to agree in writing that:

  • every account and license is held in your company’s name,
  • you hold your own admin access at all times,
  • backups are stored in an account you own or can take over,
  • on termination, the provider hands over documentation and access within a stated number of days, and
  • the provider notifies you of security incidents on its own systems, as CISA recommends.

When to get help

If you are planning a change of provider and are not sure what the current one controls, an independent inventory before you give notice is the cheapest step in the whole process.

Want to talk it through? Book a free 30-minute call with Security Medic Consulting.

Sources