The MCP server you wired up last year is about to vanish — here's the good news
So I went to add a tool to one of my agents last week and Microsoft Learn quietly informed me that the static Dynamics 365 ERP MCP server is being retired this calendar year. My first reaction was, honestly, mild panic — I have agents in production leaning on that thing. My second reaction, after actually reading what's replacing it, was: oh, this is better. A lot better.
What's actually changing
If you connected an agent to F&O over the last year, you probably wired it to the static MCP server — a fixed set of tools, pointed mostly at OData. It worked, but it was rigid. You got what you got.
The new dynamic ERP MCP server is the replacement, and the word "dynamic" is doing real work here. Instead of a frozen tool list, it exposes three living categories — data tools, action tools, and metadata tools — that let an agent do nearly anything a user can do through the UI. No custom connector, no bespoke API, no glue code you'll be maintaining at 2am.
The part that made me sit up: the data tools are moving operations off OData and onto SQL under the hood. If you've ever watched an agent grind through a chatty OData query against a big table, you know exactly why that matters. Faster responses, and — this is the underrated bit — better responses, because the agent can navigate ERP data intelligently instead of guessing its way through entity relationships.
Why you should care this week
Two reasons. One, if you've got anything pointed at the static server, the clock is ticking — migrating to the dynamic server isn't optional, it's a "do it before it's an incident" item. Put it on the board now.
Two, and more fun: agents can now open the actual record or attachment behind a Copilot response. That sounds small. It isn't. It's the difference between an agent that asserts something and an agent that shows its work — and trust is the whole ballgame when you're letting AI touch financial data.
Takeaway: Go check whatever you built on the static MCP server, plan the move to the dynamic one, and while you're in there, lean into the SQL-backed data tools. The migration is a chore. What you get on the other side genuinely isn't.
So I went to add a tool to one of my agents last week and Microsoft Learn quietly informed me that the static Dynamics 365 ERP MCP server is being retired this calendar year. My first reaction was, honestly, mild panic — I have agents in production leaning on that thing. My second reaction, after actually reading what's replacing it, was: oh, this is better. A lot better.
What's actually changing
If you connected an agent to F&O over the last year, you probably wired it to the static MCP server — a fixed set of tools, pointed mostly at OData. It worked, but it was rigid. You got what you got.
The new dynamic ERP MCP server is the replacement, and the word "dynamic" is doing real work here. Instead of a frozen tool list, it exposes three living categories — data tools, action tools, and metadata tools — that let an agent do nearly anything a user can do through the UI. No custom connector, no bespoke API, no glue code you'll be maintaining at 2am.
The part that made me sit up: the data tools are moving operations off OData and onto SQL under the hood. If you've ever watched an agent grind through a chatty OData query against a big table, you know exactly why that matters. Faster responses, and — this is the underrated bit — better responses, because the agent can navigate ERP data intelligently instead of guessing its way through entity relationships.
Why you should care this week
Two reasons. One, if you've got anything pointed at the static server, the clock is ticking — migrating to the dynamic server isn't optional, it's a "do it before it's an incident" item. Put it on the board now.
Two, and more fun: agents can now open the actual record or attachment behind a Copilot response. That sounds small. It isn't. It's the difference between an agent that asserts something and an agent that shows its work — and trust is the whole ballgame when you're letting AI touch financial data.
Takeaway: Go check whatever you built on the static MCP server, plan the move to the dynamic one, and while you're in there, lean into the SQL-backed data tools. The migration is a chore. What you get on the other side genuinely isn't.
No replies yet. Be the first to respond!
