Content reviewed: 12 October 2026

Eligible CSP subscriptions can move to a new partner while the customer keeps the existing tenant. Transferring billing ownership does not move email, files or identities into a new tenant. The Microsoft process requires a relationship with the target partner and approval from both transacting partners. Verify subscriptions, billing, supporting services and administrative access in advance.

Separate four parts of the transition

What changes with the partner
AreaOutcomeEvidence
Partner relationshipThe new partner can serve the customer under the applicable modelAccepted relationship request and agreement records
Subscriptions and billingBilling ownership of eligible items changesCompleted transfer items and new subscription IDs
Delegated administrationAppropriate new roles and retired old accessGDAP and other roles verified separately
Support services and integrationsOperational ownership is handed overOwners of support, backups, automation and reports

Accepting a new partner relationship does not transfer an existing subscription by itself. A billing transfer likewise does not prove that all old access has ended. Keep evidence for each area rather than only an email saying the new partner is connected.

Who creates and approves the request

The target partner initiates the request. The source selects and submits the transferred items; both parties must agree. Microsoft states that it will not force source approval and an unprocessed request expires after 30 days. An indirect reseller needs its indirect provider, the billing owner, to handle the request. See the general transfer process.

If approval is refused, do not treat a new tenant as the automatic technical solution. First identify contractual commitments, available dates and an alternative plan to preserve entitlement in the same tenant. A new order and transfer of an existing commitment have different effects; early cancellation or overlapping purchases can add costs. Base the decision on the actual contract and supported procedure.

What changes for an NCE subscription

The NCE documentation describes a new subscription ID under the target partner, carrying supported scheduled changes, the original price point and promotion. The source is responsible to Microsoft until transfer, and the target for the remaining term. Any prorated refund of prepayment described here concerns Microsoft-to-partner billing. Confirm customer pricing and settlement in the partner quotations and contracts.

Record old-to-new ID mapping. Billing exports or custom automation may otherwise reference the obsolete record. Within the European CSP region, Microsoft also permits transfers between partners using different billing currencies; the target must verify the converted price point and new billing. This is not a data move between Azure regions.

Item limits and completion status

Microsoft sets a maximum of 25 licence-based items per billing plan in a transfer. A hypothetical 32 subscriptions sharing the monthly billing plan therefore need at least two requests. Subscription count is different from user or seat count. See the limit and example in the NCE transfer documentation.

Partially Complete means some items succeeded and others failed. Do not blindly re-transfer completed items; reconcile subscription-level outcomes first and address failures. The Microsoft status overview describes normally quick processing, but problems can extend it to 72 hours. A service plan should not promise immediate completion of every item.

GDAP, reseller relationships and Azure roles

Customers can remove old GDAP roles from Partner relationships in the Microsoft 365 admin center using Remove roles. The Microsoft GDAP FAQ also states that terminating GDAP does not itself end the reseller relationship or remove Azure RBAC. Check licence transfers, purchasing relationships and permissions separately.

Before ending old administration, confirm customer-owned access, working support from the new partner and dependent integrations. Inventory service accounts, app registrations, backups, monitoring and Azure delegations. Assign an owner, required role and retain-or-remove decision to each access path.

Checks before and after transfer

  1. 01

    Build the inventory

    Record tenant ID, subscription ID, product, quantity, term, billing plan, renewal, promotion, scheduled changes and channel

  2. 02

    Confirm eligibility

    Check every item under its own process; do not treat NCE, Azure, Marketplace and direct purchases as one category

  3. 03

    Agree consent and responsibility

    Identify initiator, billing owner, approvals, contacts and partial-failure handling

  4. 04

    Reconcile each result

    Verify new ID, quantity, dates, scheduled changes, pricing, reports and service availability

  5. 05

    Complete access and handover

    Verify new support and separately retire unnecessary GDAP, RBAC and other access

Microsoft does not describe this CSP-to-CSP procedure as a transfer of Web Direct subscriptions into CSP. Apply the appropriate rules to other purchase types. The final outcome should be documented transfer of eligible items and operational handover around the same customer tenant.

Frequently asked questions

Must we move data to a new tenant when changing CSP?

Not for an eligible CSP subscription transfer that retains the customer tenant. Verify specific purchases and separate any independent migration project.

Can the target transfer without source approval?

No. Microsoft requires approval by both transacting partners and will not compel the source to accept.

Does the subscription ID stay the same?

The documented NCE transfer creates a new subscription ID. Update reporting and integration references.

Does removing GDAP end the reseller relationship and Azure RBAC?

No. Microsoft describes separate behaviour for those relationships and permissions; check them independently.