Skip to content
BC 2026 release wave 2unofficial launch event map, by waldo

Features › Developer tools

Profiling MCP for agents

GA · 6 min in 2 videos · dev relevance high · documented as Profile slow Business Central sessions with AI agents high match

Profiling MCP for agents

A coding agent can start, monitor and stop a sampling profile through the AL tool proxy or the Business Central MCP server, given a session ID. It returns CPU profile files and an overview of duration, SQL and HTTP calls, and the demo found a background codeunit producing 30,000 rows.

Area: Developer tools. Status: GA. Developer relevance: high. Airtime: 6 min across 2 videos, demoed.

Status evidence

  • Nothing said about status; launch event convention: generally available unless stated otherwise.

Where they talk about it

Quotes

  • 11:26 "To start a profiling schedule, the agent needs the numeric business central session ID that it should target." - Key difference from snapshot debugging: profiling needs a known session ID.
  • 12:22 "It also returns an overview of activity duration, CQL calls, HTTP calls and only for the MCP server memory information." - Lists what the profiling output contains, including the memory information limit to the MCP server.
  • 12:35 "The permissions are again checked by Business Central for the signin user." - Agents run with the signed-in user's permissions, with the same rules as the manual workflow.
  • 12:51 "To profile another user session, you need the D365 attach debug permission set." - Names the permission set required to profile someone else's session.
  • 30:48 "coding agents can now capture the performance profiles and the snapshot recordings themselves through dedicated MCP uh tools with no active debugging session" - Core announcement: agents can start profiles and snapshots without a debugging session set up by the developer.
  • 31:01 "You still need to judge uh what the evidence that it find means" - Sets the limit: the agent captures evidence but the human interprets it.

Caveats mentioned

  • No actual profiling was run in the demo, only the command and its parameters were shown
  • The developer still has to judge what the captured evidence means
  • Work happens on the server, the proxy is only an interface for the client
  • The agent needs the numeric Business Central session ID to start a profiling schedule, unlike snapshot debugging.
  • The session ID can come from the help and support page of the web client or be inferred from telemetry.
  • The brief overview depends on the prompt; a detailed result needs a detailed prompt.

Prerequisites mentioned

  • The AL tool
  • An agentic framework that can use the MCP proxy
  • A target environment
  • To profile your own session: permission to create profile schedules and read the performance profile
  • To profile another user session: D365 attach debug permission set
  • MCP server configured with environment and environment type

Documented features match

Docs checked on 2026-10-02: the match is against Microsoft's what's new pages for the wave as they were on that date. Microsoft keeps filling the documentation, so "no documented item" can go stale. The wider product documentation on learn.microsoft.com was searched for this feature on the same date; the feature's data lists an article when one was found.

Tags: mcp, profiling, performance, agents, al, vs-code, permissions, copilot, sql, demo

Generated by pipeline step 06. Source: YouTube auto-captions of the launch event videos, see the deep links. Not official.