Change Business Central CSP Partner: What Actually Moves

When a company decides to change Business Central CSP partner, the first worry is usually the system itself: the environments, the data, the extensions that took months to build. Microsoft keeps those things separate from billing. A partner-to-partner transfer moves billing ownership of the subscriptions from one Cloud Solution Provider to another. The Business Central environments live in the customer's own Microsoft Entra tenant, and nothing in Microsoft's transfer documentation describes moving them. This article covers what the transfer does, what the customer supplies, and the access cleanup afterward, based on Microsoft Learn as checked on 2026-10-28.

Three things that are easy to confuse

A Business Central customer has three separate assets in Microsoft's model.

• The tenant. The customer's own Microsoft Entra tenant, identified by a tenant ID.

• The environments. Production and sandbox environments, administered in the Business Central administration center for that tenant. Companies, data, and installed extensions sit inside them.

• The subscriptions. The licenses, bought through a CSP partner who is the billing owner.

A partner change touches the third item and the partner access around the second. Microsoft does have an operation that moves environments: an environment transfer relinks an environment to a different Entra tenant, and Microsoft states that it doesn't move subscriptions. Microsoft's examples for it are tenant consolidations and mergers. A customer that keeps its tenant has no reason to run it.

How a partner-to-partner transfer works

Microsoft documents the process in Transfer billing ownership from one partner to another. The mechanics decide who has to act.

• The new partner initiates. Customers don't start the transfer. The target partner creates the request in Partner Center, inside the customer's account, under Transfers.

• Both partners must approve. The current partner selects the subscriptions to move and submits them. Microsoft will not override a transfer without the current partner's approval and does not mediate disputes. A request the current partner ignores expires after 30 days.

• The relationship comes first. Before any request, the customer notifies the current partner, signs a Microsoft Customer Agreement with the new partner, and accepts the new partner's relationship request. The new partner also needs the current partner's Microsoft ID, which is that partner's tenant ID.

• The customer is notified. The request names a customer email address. Microsoft sends that contact an email when the transfer is created and when it completes.

• Completion is usually quick once approved. Microsoft says most transfers complete in under an hour and some take up to 72 hours while failed line items are retried.

Indirect resellers add one layer. Microsoft supports transfers between direct bill partners and indirect providers. If the current partner is an indirect reseller, its indirect provider is the billing owner and has to send or approve the request. Transfers are CSP to CSP only. Subscriptions bought directly from Microsoft are out of scope for this feature.

Check Business Central eligibility before anyone promises a date

Microsoft's documentation carries a Business Central caveat. The marketplace and software transfer page states that partners can't transfer 3PP (third-party marketplace) Business Central at this time. The overview page lists "business central items" among the items this capability can't transfer. The new partner should confirm how each Business Central line on the account was sold, and whether it is eligible, before the request goes out. Anything that isn't eligible stays with the current partner until the parties agree on another route.

What changes and what does not

The new commerce license-based transfer article is specific about the commercial effects.

What changes

• The billing owner. Microsoft bills the new partner for the rest of the term. The previous partner is responsible up to the transfer date and is credited pro rata if it prepaid.

• The subscription ID. The transfer creates a new subscription under the new partner, with a new ID.

What stays the same

• The term. Transfers happen mid-term and aren't treated as new subscription terms, so there is no new cancellation window.

• The price. The new subscription carries the original subscription's price, and promotions applied to it carry over.

• Quantities and renewal settings. User counts, renewal properties, and scheduled changes are preserved.

One timing rule matters: upgrades can happen before a transfer is accepted or after it completes, not during it. A customer planning a license change at renewal should sequence it around the transfer. The Essentials vs Premium vs Team Members comparison is a useful reference for that review.

On the Business Central side, Microsoft's own documentation shows that billing and administration are separate relationships. In delegated admin access to Business Central online, Microsoft notes that a partner whose delegated permissions are removed can still manage the subscription in Partner Center but can no longer sign in to the customer's environments. The same applies to the new partner: Microsoft states that a reseller needs a separate admin relationship to manage the customer's services.

Two approvals the customer gives

The customer approves two different things, usually from two different emails.

The reseller relationship. The new partner generates a reseller relationship request in Partner Center. The customer opens the link and accepts it in the Microsoft 365 admin center, which includes accepting the Microsoft Customer Agreement. Microsoft's partner relationship guidance requires at least the Billing Administrator role for this step. This relationship lets the partner buy on the customer's behalf. It grants no admin access.

The GDAP relationship. Granular delegated admin privileges give the partner time-bound access limited to the Entra roles the customer approves. A Global Administrator approves the request in the Microsoft 365 admin center. For Business Central work, Microsoft recommends the Dynamics 365 Business Central Administrator role as the least-privileged role that grants access to the admin center and environments. Roles can't be added to an existing GDAP relationship, so a partner that needs more creates a new request. A customer that does not want to give admin roles can decline the GDAP request. The reseller relationship does not depend on it.

The customer checklist

Bitta Apps asks for these items at the start of every partner change, so that each request and each admin center URL points at the right tenant.

1. Tenant ID. A Global Reader or higher can find the tenant ID in the Microsoft Entra admin center under Entra ID > Overview > Properties. Microsoft also notes that the tenant ID appears on the Help and Support page in Business Central.

2. A written subscription list from the current partner. Product names, quantities, term lengths, billing frequency, and renewal dates. Microsoft expects partners to exchange subscription details outside Partner Center, so this list is the reference both sides check against.

3. Admin contacts. Who holds Global Administrator (GDAP approval and Business Central partner access settings), who holds Billing Administrator (the reseller relationship), and which mailbox should receive transfer notifications.

4. Written notice to the current partner. Microsoft lists this as a prerequisite, and agreement up front keeps a request from expiring unanswered.

5. GDAP review. On Settings > Partner relationships in the Microsoft 365 admin center, the customer can see every partner and which ones hold GDAP. Approve only the roles the new partner's scope requires.

6. Removing the old partner's access afterward. See the next section.

Close out the old partner's access

Removing admin roles and ending a reseller relationship are separate actions. A customer removes a partner's GDAP by selecting the partner on Partner relationships, choosing Remove roles, and confirming. Microsoft notes that this does not remove the partner relationship. To end that, the customer contacts the partner.

Business Central has its own layer. In the admin center, the Partner access setting on each environment controls which partner tenants can reach it. Only internal Global Administrators can change it. Microsoft points out that this setting is preserved when a GDAP relationship ends, so a partner whose tenant-level access is later restored regains access to the environment. Microsoft's guidance is to change the setting after tenant-level access is removed, for example by turning off access for all partner tenants and allowing only the new partner.

Microsoft also lists settings to clean up when switching partners: the support contact on each environment, the tenant's notification recipients, any Application Insights key the old partner configured, and any Microsoft Entra apps the old partner authorized, including revoking their consent in the tenant.

A short environment review after the transfer gives the new partner a documented baseline of extensions, integrations, and settings. Customers still comparing options can use the questions for choosing a Business Central partner before any request is sent.

Under Microsoft's transfer rules, a partner change does not start a new term, does not reprice the licenses, and does not migrate the system. The remaining work is coordination and access hygiene, and both are easier with a checklist than without one. Customers planning a move can contact Bitta Apps to review their subscription list and access before the request goes out.