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

Features › Developer tools

AL graph

GA · 5 min in 2 videos · dev relevance high · documented as Audit AL app accessibility and debugging boundaries high match

AL graph

A graph command in the AL tool builds a static call graph across an extension and its dependencies. You or an agent can query who calls whom, external integration points, and public entry points.

Area: Developer tools. Status: GA. Developer relevance: high. Airtime: 5 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

  • 1:10 "one big one um, that we're quite focused on is the non-debuggable to debuggable boundary." - Names the main security use case the AL team built the tool for.
  • 1:24 "because, you know, you can inadvertently expose secrets that way." - Explains the risk behind crossing from non-debuggable to debuggable code.
  • 27:34 "Counter to the LSP which is actually looking at the project as it is now." - Explains how the graph analysis differs from the language service protocol tool.
  • 27:46 "This is a static thing that we can do offline as long as we extract uh the information that we need to query on beforehand." - States the call graph is an offline static analysis that needs an up-front extraction step.

Caveats mentioned

  • Extraction compiles all specified apps and takes time, so it was done in advance for the demo
  • Static analysis works on the extracted data, not on the project as it is now like the LSP
  • A separate full session on the graph tool will cover querying and visualizing the graph in more detail; a link is in the description

Prerequisites mentioned

  • al .NET tool, where the agentic tools live
  • Run the extraction first over the apps you specify (compiles them)
  • AL tools package

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: al, call-graph, static-analysis, cli, security, agents, code-review, developer-tools, auditing, vs-code

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