Set the standard once, roll it out to everyone
Until now every person configured their own analytics — their own team scopes, WIP rules, thresholds, work item types. Fine for one team; painful for an organisation running twenty. The new Enterprise section in Configuration lets an admin define organisation-wide defaults and, separately, apply them to every existing user in one click. The rollout is deliberately polite: each person sees exactly which settings changed and can keep their own with one click, personal additions are merged rather than overwritten, and the admin sees the change reflected in their own session immediately. New joiners start from the organisation baseline automatically.
Locks you can actually see, and governance over people metrics
Admins can mark selected settings as organisation-managed. As of this release those locks are visible everywhere the setting appears — the control shows as locked with a note saying your organisation manages it, whether that is the WIP Monitor configuration, the metric work item types, or the Count/Points display toggles inside the views themselves. Separately, the User Metrics view — the one place the product shows named individuals — is now governed: it is off for members by default, an admin decides whether to enable it, exports are role-gated, and admin actions land in an audit log.
Forecasts that tell you how sure they are
Monte Carlo forecasts now describe their results as what they are: a range the team’s own history supports at a stated confidence, not a promise. The wording changed across every surface that shows a forecast, in all six supported languages, and the aging chart was redesigned from the ground up so a calm sprint looks calm instead of alarming. A built-in metrics glossary now explains every measure the product shows, in plain words, one click from where you read it.
Dashboard widgets, now actually configurable
Agile Analytics has shipped Azure DevOps dashboard widgets for a while — team health, cycle time, throughput, sprint forecast, DORA at a glance. What it had not shipped, embarrassingly, was a working Configure panel: the widget could be placed but never told which team to show. The follow-up release 6.43.1 fixed the wiring, so the Configure dialog now opens the team picker it always should have. The same release also made views recover automatically when a network hiccup interrupts loading, instead of staying broken until the next full reload.
Since our last post here
This blog fell behind the product for a few releases; the short version of what you may have missed. 6.39 introduced annual Team and Business plans and made seat usage visible to admins. 6.41 gave epic forecasts honest ranges — a likely landing date plus a date the epic’s own delivery history supports with 85% confidence — and taught scheduled reports to say when their pipeline setup is unfinished instead of showing “not delivered yet” forever. Along the way past sprints stopped being rewritten by later work, silent chart gaps became visible notices, and the error messages between you and a working GitHub Copilot connection started naming the actual problem.
Updating
Azure DevOps updates the extension automatically — nothing to install. Everything above works with your data staying inside your Azure DevOps organisation: no PAT, no data sent to us. If anything reads wrong after the update, use Ask Henry in the top bar and a real person replies within one business day.
Related: Service status