Changing your Dynamics 365 partner: a checklist

Leaving your ERP partner is prepared before it is announced. Three things determine whether a takeover goes smoothly:

1. The Azure DevOps repository: your extensions' code, its history and the build pipelines. Check which Azure DevOps organization it lives in and who administers it. If it sits with the provider, ask for a transfer or a full copy.
2. Customization documentation: specifications, the list of extensions, integrations and ISV solutions in place. Whatever is not written down leaves with the provider.
3. Environments and access: Microsoft lists among the customer's responsibilities providing user access to the service and access to the Lifecycle Services (LCS) project used to manage environments (source at the end of this article). Make sure your own administrators hold this access before the provider leaves.

It is also the moment to reread the reversibility clause of your contract: what must be handed over, in which format and within what time frame.

A repository in your own Azure DevOps organization changes the balance of power: code, history and pull requests stay with you, whichever provider you use. One simple rule to set now: everything that goes to production goes through a pull request approved by your CIO. That is already how Skalp AI delivers, and it is a criterion to demand from any provider (see the selection criteria in Dynamics 365 F&O partner: do you still need one?).

The Pro plan includes analysis of the customer's Azure DevOps repository: the AI starts from your existing extensions, not from a blank page, to specify and generate new developments. The process:

1. Free qualification of the need in the Skalp AI chat.
2. Analysis of your Azure DevOps repository (Pro plan).
3. Specification, X++ code and tests generated; the credit is only consumed at this step.
4. Delivery as a pull request, approved by your CIO before merge.

For tests/UAT, documentation, training and go-live, the Max plan adds an expert from the Skalp AI network, in-house or partner. To choose: which Skalp plan to choose and plans and pricing.

Platform support stays with Microsoft whatever your provider: service incidents are opened in Lifecycle Services. For your customizations, compare the options (AMS, in-house team, Skalp AI) in Dynamics 365 F&O support: options and cost.

• Microsoft Learn, "Service description for finance and operations apps", updated 26 Mar 2026, accessed 8 Nov 2026.
• Microsoft Learn, "Get support for finance and operations apps or Lifecycle Services", updated 10 Mar 2026, accessed 8 Nov 2026.