How to Switch Microsoft CSP Providers

Four changes that are often confused

Partner relationship The customer accepts a relationship with the new partner and, where required, the Microsoft Customer Agreement. This enables the partner to transact for the customer. It does not by itself move existing subscriptions.

• Subscription ownership or transfer Eligible subscriptions can follow Microsoft’s partner-to-partner transfer process. The target partner initiates the request, and both the source and target partner must approve it. Microsoft states that the source partner is not obliged to accept and that Microsoft will not override the decision.
• Delegated administration
• Granular delegated admin privileges, support roles, security contacts, and automation are separate from billing. They need their own inventory, approval, and removal plan. Tenant migration
• A migration moves identities, domains, or workload data between tenants. That is a separate project and is unnecessary when only the provider changes and the tenant remains the customer’s existing tenant.

What happens in a new-commerce subscription transfer

For supported new-commerce licence-based subscriptions, Microsoft’s transfer documentation says that scheduled changes, seat counts, renewal properties, the original price, and promotions carry to the target partner. The target receives a new subscription ID, so integrations and reports that rely on the old ID must be updated. The source and target partners must be in the same region. Specialised offers transfer only when the target partner has access to them. A transfer request expires after 30 days if the required actions are not completed. These details make a transfer more than an invoice switch. A customer should reconcile every source subscription with its target record and verify quantities, term dates, billing plans, renewal settings, promotions, and scheduled changes after completion.

Not every purchase follows the same path

Before agreeing a cutover date, classify the estate: new-commerce licence-based subscriptions;

• legacy licence-based subscriptions, if any remain; Azure plan subscriptions and reservations;
• Marketplace products;
• software subscriptions and perpetual software; support plans and third-party managed services;
• subscriptions bought directly from Microsoft or through another channel. Microsoft’s documented CSP-to-CSP transfer process does not mean every item can move in the same request. For example, a Web Direct purchase is not automatically converted through the partner-to-partner flow. Some products may need to remain with the source until renewal, be cancelled within an allowed window, or be repurchased through the target.

Practical checks

Never cancel a subscription merely to “clean up” the estate before the replacement and continuity plan are verified. New-commerce cancellation rights are time-limited, and an early cancellation may not be available.

A controlled transfer plan

Confirm that the customer controls

• global administrator break-glass accounts, domains,
• billing contacts, and recovery methods. A provider change is
• a good time to remove the dangerous assumption that
• the partner is the only route into the tenant.

1. Establish tenant ownership

Confirm that the customer controls global administrator break-glass accounts, domains, billing contacts, and recovery methods. A provider change is a good time to remove the dangerous assumption that the partner is the only route into the tenant. 2. Build a subscription ledger For each item, record subscription ID, product, quantity, term, billing plan, renewal date, autorenew state, scheduled changes, promotion, channel, and current owner. Mark whether Microsoft documents it as transferable. 3. Map operational dependencies List GDAP relationships, Azure Lighthouse delegations, partner admin links, service accounts, APIs, ticketing integrations, backup services, security tooling, and billing exports. Decide which should be recreated, transferred, or retired. 4. Agree responsibilities The customer, source partner, and target partner should agree who initiates and accepts each request, who monitors service continuity, how open support cases are handled, and when old delegated access is removed. 5. Reconcile after transfer Do not treat “approved” as proof of completion. Verify the target subscription records, seat counts, renewal dates, billing, service availability, Azure access, support path, and removal of obsolete permissions.

What should not change

When the tenant stays the same and coverage is continuous, users should not need new identities solely because of the CSP

• change. Their mailbox addresses, Teams memberships, SharePoint URLs, device enrolment, and
• domain configuration should not be moved merely to change partner.
• There can still be disruption if someone cancels the wrong
• subscription, leaves a coverage gap, removes administrative access too early,

Practical checks

or overlooks a third-party service. The absence of a data migration does not remove the need for change control.

Red flags

The provider proposes a new tenant without a documented technical reason. No one can produce a complete subscription and renewal inventory.

• The plan assumes Microsoft will force the source partner to approve a transfer.
• Direct, legacy, Azure, and Marketplace items are treated as one identical transaction.
• Old delegated permissions will remain indefinitely “just in case”.
• The customer does not control emergency administrator accounts.

Practical checks

Subscription IDs are used in automation, but no one plans to update them.

Questions to ask the new provider

Which exact products can transfer and under which Microsoft process? Which items must wait for renewal or be repurchased?

• Will current term, price, promotion, seat count, and autorenew settings carry?
• How will Azure, reservations, Marketplace, support, and third-party services be handled?
• Which GDAP roles are requested, for how long, and why?
• What evidence will prove the transfer and access cleanup are complete?

Practical checks

Switching CSP providers should be a controlled commercial transition around the customer’s existing tenant—not an excuse for an unnecessary data migration. If you need a neutral inventory before changing partners, contact Axeti .

Sources and scope: The process described here follows Microsoft’s documentation for partner-to-partner transfers , new-commerce licence-based transfers , and Azure plan transfers . Eligibility and procedures change; verify every product against the current documentation and customer agreement before execution.