This week I looked at what Microsoft has on the roadmap for Dynamics 365 Finance and Supply Chain Management with preview or general availability in November and December 2026. Most of it is about how environments are managed and how agents get access to the ERP. Roadmap months are plans and can move, so read them as planned, not promised.
1. Environment management moves from LCS to Power Platform admin center
A self-service migration of existing F&O environments from Lifecycle Services to the Power Platform admin center is in public preview and planned for general availability in December 2026 (roadmap item 573244). Migration is done per environment, and the database is not moved.
The documentation is clear on the details. Migration is one-way: afterwards the environment is read-only in Lifecycle Services. Plan for roughly 15 minutes of downtime per AOS instance. During preview Microsoft recommends sandboxes first and not production, and environments using Commerce functionality are not supported. Cloud-hosted developer environments are not supported either. The migrated environment consumes capacity under the Power Platform capacity model. See Migrate finance and operations environments from Lifecycle Services to Power Platform admin center.
What to do: do not start with the migration button. Start with the parts around it: unified developer environments, Azure Pipelines that build and deploy unified packages, and a check of your storage capacity. Then migrate one low-risk sandbox, run an environment copy and validate a customization deployment before you plan anything for production.
2. Role-based access controls for ERP agents
Security administrators will be able to apply restrictions that only take effect when a user reaches the ERP through an agent. They use the existing model of roles, duties and privileges, scoped by legal entity, so an agent session can have narrower permissions than the same user has directly in the ERP. The roadmap lists preview from October 2026 and general availability planned for December 2026 (roadmap item 571677).
What to do: if you are piloting agents against F&O, ask who decides what an agent may do on a user's behalf. Map the few processes where the agent should only read or only prepare, and test the restrictions in a sandbox once the preview is available to you.
3. MCP for ERP analytics, and a note on the ERP MCP server
The roadmap lists MCP for ERP Analytics, which gives agents access to analytics data, metrics, dimensions and the semantic model, with general availability planned for December 2026 (roadmap item 576762). Separately, the guidance for building agents with the Dynamics 365 ERP MCP server notes that the older version with 13 static tools is retired, and that the current server uses a dynamic set of tools. See Build an agent with Dynamics 365 ERP MCP.
What to do: if an agent prototype still uses the static-tools server, plan to rebuild it on the current one. For analytics, hold off on design work until the preview content is documented; I would rather wait than build on assumptions.
My take
These items point the same way: the control plane for F&O is moving into the Power Platform world, and agents are being treated as a separate kind of user that needs its own security design. For most customers the practical work is not technical. It is deciding who owns environment management after LCS, and who signs off on what an agent may do. I would start both conversations now, in a sandbox, and leave production for later.
