From MConfig, APU/TPU application and the Deltek Software Manager to Visual Studio with D365 development tools, models and packages, Azure DevOps pipelines, deployable packages, environment lifecycle through the Power Platform admin center, and Application Insights telemetry — including the LCS freeze on 16 February 2026.
Maconomy's development and deployment toolchain — MConfig, the Deltek Software Manager, environment topology management, Workspace Client compatibility testing, and APU/TPU application — is entirely customer-managed. The customer owns the servers, controls the update cadence, and operates the release process.
The transition from this topology to D365 eliminates the infrastructure layer entirely. There are no servers to patch, no databases to back up, no web servers to configure. The operational focus shifts to:
D365 X++ development happens in Visual Studio with the Dynamics 365 Finance and Operations development tools extension. This replaces any ad-hoc MScript editing, Java IDE setup, or Extender configuration tools used in Maconomy development.
A model declares its dependencies on other models (e.g., "MyModel depends on ApplicationSuite"). The compiler enforces these dependencies — a model cannot reference artefacts from models it does not declare as dependencies. This prevents the circular and implicit dependencies that can accumulate in less-structured customisation estates.
The Azure DevOps pipeline replaces Maconomy's manual or lightly-scripted release process:
The Power Platform admin center (PPAC) is the primary management interface for D365 environments. It replaces MConfig's role in environment provisioning, update scheduling, and deployment management.
Maconomy operational monitoring typically relies on server-side log files, database monitoring tools, and job-status dashboards — all requiring direct infrastructure access.
Maconomy source control practices vary widely by organisation — from file-system copies to commercial version-control systems, with no platform-prescribed model.
A dimension that Maconomy teams must communicate clearly to their user base: D365 has no desktop client. Every user accesses D365 through a web browser.
The playbook's warning bears repeating: cloud/on-premises choice, PPAC/LCS posture, Dataverse solution lifecycle, dual-write maps, X++ packages, Power Platform pipelines, ISV releases, and interface deployments must share one coordinated release calendar.
The tooling and ALM transition from Maconomy to D365 is not a tool-for-tool replacement. It is a shift from customer-managed infrastructure with discretionary updates to a Microsoft-managed platform with mandatory cadence and automated deployment. The operational model changes as fundamentally as the code language.