Consolidating Providers in Work 365: Move Subscriptions from Provider B to Provider A

Modified on Mon, Mar 9 at 10:52 AM


Applies To: Work 365 Provider Integrations, Microsoft Partner Center (CSP transfers)
Audience: Work 365 Admins, Billing Admins, Partner Center Admin Agents


Overview

If you want to consolidate Microsoft CSP subscriptions from one provider to another, handle it as a transfer-and-reconcile process, not as a simple Provider-field edit on active subscriptions. Microsoft’s supported upstream method is the Partner Center transfer workflow for Azure plan items and new commerce license-based subscriptions. In Work 365, subscriptions are part of a billing relationship and should be tied to both a Customer and a Billing Contract, so the downstream work is to reconcile the new target-side records after the Microsoft transfer finishes.


Before You Begin

Before starting, define your providers clearly:

  • Target Provider = the provider you want to keep long term

  • Source Provider = the provider you want to retire

Also confirm these prerequisites:

  • The customer already has a relationship with the target partner before the transfer can proceed.

  • Microsoft’s current partner-transfer flow covers Azure subscriptions, reservations, and savings plans under Azure plan, plus new commerce license-based subscriptions.

  • For Azure transfers, the future partner must already have an active Azure plan, and Microsoft notes the future partner can cancel the default subscription that is automatically created when acquiring that Azure plan after the transfer completes.

  • Microsoft’s transfer steps require Admin agent permissions for creating and approving these transfers.

  • In Work 365, a Billing Contract is required for invoicing, and subscriptions should be associated with the customer’s Billing Contract.


How It Works

The clean operating model is:

  1. Complete the Microsoft transfer in Partner Center

  2. Wait for the transfer to reach a finished state

  3. Reconcile the resulting target-side subscriptions in Work 365

  4. Retire the old source-side records only after you confirm the new records are the ones you want to keep billing

That sequence aligns with Microsoft’s transfer model and with Work 365’s billing model. It also avoids risky in-place edits, because Work 365 warns that changing the Provider on billed subscriptions can have adverse or unintended consequences.


Resolution Steps

Step 1: Pause source-side cleanup until the Partner Center transfer is finished

Do not start cleanup in Work 365 while the Microsoft transfer is still Pending or In Progress. Microsoft says most transfers complete in less than an hour, but some can take up to 72 hours. Microsoft also documents these relevant statuses: Pending, In Progress, Complete, Partially Complete, Failed, Expired, and Canceled.

Step 2: Complete the supported transfer in Partner Center

Use Microsoft’s documented partner-to-partner transfer flow:

  1. Confirm the customer has accepted the relationship with the target partner

  2. Have the target partner create and send the transfer request

  3. Have the source partner review, accept, and submit the request

  4. Monitor the request until it reaches Complete or Partially Complete

For new commerce license-based subscriptions, Microsoft states that the transfer creates a new subscription under the target partner with a new subscription ID, while preserving the original subscription price and carrying over scheduled changes and core subscription properties.

Step 3: Validate Provider Account mapping in Work 365

After the transfer finishes, sync and validate the Provider Account mapping for the Target Provider. Work 365 defines Provider Account as the mapping between a provider and the CRM Account record. Work 365 also documents Sync Provider Accounts as the process that imports customer records from an automatic provider so you can complete the mapping from the Provider Account list.

If this mapping is wrong, transferred subscriptions can land against the wrong customer or appear orphaned during reconciliation. That is why this check should happen before subscription cleanup.

Step 4: Pull the transferred subscriptions into the correct Billing Contract

Open the customer’s Billing Contract and run Sync Subscriptions. Work 365 documents this as the standard method for bringing automatic-provider subscriptions into a Billing Contract. Work 365 also states that subscriptions must be associated with both a Customer and a Billing Contract, and that a Billing Contract is required for invoicing.

Step 5: Review the target-side records for billing readiness

After sync, confirm the new target-side subscriptions have the correct:

  • Customer

  • Billing Contract

  • pricing / price-list context

  • any other billing-critical values needed in your environment

Work 365’s Exceptions Dashboard specifically notes that automatically synced subscriptions can arrive with missing billing data such as Billing Contract, Customer, and Subscription Price Data, and those issues should be corrected before billing.

Step 6: Retire the old source-side records carefully

Once the target-side subscriptions are correct, stop the source-side records from continuing to affect billing.

Preferred option — use provider sync plus controlled review
If the source provider no longer returns those subscriptions, Work 365’s Deactivate Missing Subscriptions setting can deactivate subscriptions that are missing from the provider. Work 365 recommends this setting as Yes.

Manual option — deactivate only after confirming provider-side impact
Be careful with manual deactivation. Work 365 documents that deactivating a subscription creates a deactivation changelog that syncs with Partner Center and deactivates the subscription there. Work 365 also warns that activation/deactivation behavior for automatic-provider subscriptions should be reviewed carefully because some provider-side actions can be rejected or behave differently.


Important Notes

Do not use Change Provider as the main migration method

This is the main guardrail. Work 365 documents Change Provider for deactivated subscriptions, not as the standard method for moving active CSP subscriptions between live provider integrations.

Do not treat this like a simple Provider-field update

Work 365’s Subscription Management guidance says changing the Provider after a subscription has been billed can have adverse or unintended consequences. Work 365 also recommends not deleting subscriptions and instead deactivating them when they are no longer needed.

Expect new target-side records in some Microsoft transfer scenarios

For new commerce license-based transfers, Microsoft states the target partner receives a new subscription record with a new subscription ID. That is why reconciliation should focus on validating the new target-side records, rather than trying to repoint the old source-side record.


Best Practices

  • Reconcile in a planned window after the Partner Center transfer has finished, not while it is still pending.

  • Validate Provider Account mapping before you sync subscriptions into Billing Contracts.

  • Use the Exceptions Dashboard after sync to catch transferred subscriptions missing Customer, Billing Contract, or pricing data.

  • Avoid using Change Provider as a shortcut for active migrated subscriptions. Reserve it for the cleanup scenarios it is actually documented for.

  • Be cautious with manual deactivation of automatic-provider subscriptions because Work 365 documents provider-side sync behavior on deactivation.


Summary

To consolidate providers safely, move the supported subscriptions in Partner Center first, then reconcile the results in Work 365. The control points are straightforward: confirm the target partner relationship, complete the Microsoft transfer, validate Provider Account mapping, sync the new subscriptions into the correct Billing Contract, fix any missing billing data, and only then retire the source-side records so they do not keep billing. 

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article