Frontier Firm and ERP: what it changes for your D365 F&O backlog

"Frontier Firm" is a Microsoft term, introduced in its April 2025 Work Trend Index: an organisation "structured around on-demand intelligence and powered by 'hybrid' teams of humans + agents". At Ignite 2025, Microsoft tied it to business applications: Frontier Firms put Copilot, agents and "agentic business applications" at the core of their operating model, and Dynamics 365 is presented as a "system of action".

For a Dynamics 365 Finance & Operations backlog, the practical effect is not a big bang. It is new kinds of tickets: making data reachable by agents (data entities), exposing precise business actions (X++ classes), and securing what each agent may do (roles). The rest of the backlog does not go away.

Microsoft's 2025 Work Trend Index, "2025: The Year the Frontier Firm Is Born" (23 April 2025), describes three phases: AI as an assistant that saves time; agents joining teams as "digital colleagues" and taking on specific tasks at human direction; then humans setting direction for agents that run entire business processes and workflows, checking in as needed.

It is a lens from a study, not a certification or a product. Take it as such: useful to position your projects, not a mandatory stage.

In Bryan Goode's Ignite 2025 post, Dynamics 365 is presented as a "system of action": a system where agents do not just read data but trigger operations. The same post announced the public preview of the MCP server for Dynamics 365 ERP, which lets an agent read, write and call actions in Finance & Operations according to its security role. We cover that server in Dynamics 365 ERP MCP server: what F&O developers need to know.

In practice, four ticket families appear or gain weight:

1. Data entities: an agent reads and writes through entities first. A custom table with no entity is invisible to it.
2. X++ action classes: business logic with no button (calculation, composite operation, validation) must be exposed as an AI tool. See Copilot Studio agents for D365 F&O: what still needs X++.
3. Security: one role per agent, limited to its scope, with dedicated privileges and duties.
4. Label and description quality: agent orchestration relies on object names and descriptions.

What does not change: regulatory changes, reports, interfaces, fixes after updates. An agent does not remove these needs; it adds to them.

Start from two or three repetitive, well-bounded tasks, test an agent on a Tier 2 or UDE environment, and note what is missing: entity, action, permission. Those gaps form a short, measurable backlog. Also follow Microsoft's roadmap, now published continuously: release waves retired. Key terms are gathered in our agentic ERP glossary.

These short tickets are Skalp AI's core business: ERP context analysis, specification, X++ code and unit tests, delivered to your Azure DevOps and validated by your IT lead. See AI X++ development, the bigger picture in building X++ without a consultant in 2026, and the Basic, Pro and Max plans.

• Microsoft WorkLab, "2025: The Year the Frontier Firm Is Born", 23 Apr 2025, accessed 11 Oct 2026.
• Microsoft Dynamics 365 Blog, "Microsoft Ignite 2025: Powering Frontier Firms with agentic business applications", Bryan Goode, 18 Nov 2025, accessed 11 Oct 2026.