Dynamics 365 Finance environments and Lifecycle Services
How environments work in Dynamics 365 Finance and Supply Chain — Tier 1 through Tier 5, the role of Lifecycle Services, and the move to managed environments.
Environments in Dynamics 365 Finance and Supply Chain Management (collectively, the Finance and Operations apps) are more involved than in Business Central. They're sized as named tiers, provisioned through Lifecycle Services (LCS), and operated under a mixed responsibility model that customers and partners both need to understand.
Environment tiers. Sandboxes are sized by tier, where the tier indicates infrastructure scale rather than just function:
- Tier 1 — a single-box development environment running on one Azure VM. Suitable for code work, not for realistic data volumes or concurrent users.
- Tier 2 — a multi-box, high-availability sandbox close to production scale, used for UAT, load testing, and golden-config builds. Every Finance/SCM project gets at least one Tier 2.
- Tier 3, 4, 5 — progressively larger sandboxes for very large customers.
- Production — Microsoft-managed, high-availability, with a defined SLA.
Provisioning. Tier 1 sandboxes can be self-deployed from LCS in hours. Tier 2+ sandboxes and production are provisioned by Microsoft as part of FastTrack onboarding, with paperwork and lead times.
Lifecycle Services (LCS). LCS is the cloud portal where customers and partners manage F&O implementations — project workspaces, environment requests, deployment of code packages, application of platform updates, support ticket management, the Business Process Modeller, the BPM-Task Recorder integration, and asset libraries. Every Finance/SCM environment is registered to an LCS project.
Deployable packages. Custom code, configuration, and reports flow through LCS as deployable packages built from Visual Studio. A package is uploaded to LCS, then applied to an environment by an authorised user. There is no direct dev → prod publish; everything goes through the staged process.
Database refresh. LCS handles point-in-time copy of production to sandbox for testing with real data, with golden-record masking for sensitive fields. The reverse path (sandbox → prod) is limited and tightly controlled.
Managed environments. Microsoft is moving F&O toward a more managed model where customer self-administration shrinks and platform automation grows. Recent waves shift more lifecycle operations into the Power Platform admin centre and away from LCS, aligning F&O with the Power Platform's environment model.
Cost. Sandboxes beyond a minimum included set are paid add-ons. Plan environment topology and SKUs early in the project.
Related guides
- Financial dimensions in Dynamics 365 FinanceHow financial dimensions work in Dynamics 365 Finance — global dimensions, account structures, default dimensions, and the design choices that decide reporting flexibility.
- Number sequences in Dynamics 365 Finance and SCMHow number sequences work in Dynamics 365 Finance and SCM — scope, continuous vs non-continuous, manual override, and statutory gap-free requirements.
- Parallel currencies in Dynamics 365 FinanceHow Dynamics 365 Finance handles parallel reporting currencies — accounting currency, reporting currency, and tax currency, with the consolidation implications.
- Reporting tools in Dynamics 365 FinanceThe reporting stack in Dynamics 365 Finance — Financial Reporting, electronic reporting, Power BI, and where each one fits.
- Subscription billing in Dynamics 365 FinanceMicrosoft's Subscription Billing module — recurring contracts, revenue recognition, billing schedules, and where it fits in the F&O stack.