Dynamics 365 Performance Probe measures what users actually experience

Original article from September 2, 2026: Dynamics 365 Performance Probe Browser Extension, on Power Pete. Read the original

Source may be outdated. The original article is more than 60 days old. Dates and availability refer to the state of the source.

This is our own summary, not a republication or full translation.

Schematic view of the steps described by Power Pete, not a screenshot.

TL;DR

The Dynamics 365 Performance Probe browser extension measures model-driven app performance from the user's seat. It separates blocking, post-render, and background requests, reports usable time alongside fully loaded time, identifies eleven likely causes, assigns ownership buckets, and creates offline PDF or HTML reports after at least 30 interactions.

Why it matters

• Makers: Install the Edge or Chrome extension, start it before reloading the model-driven app, and capture normal work for ten minutes so measurements include the full boot sequence.
• Admins/IT: Use the request categories and ownership buckets to route slow interactions to custom build, client systems, Microsoft platform, or shared causes instead of treating every delay as one problem.
• Leadership/Business: Read usable time separately from fully loaded time because a screen can be ready before background detail finishes, preventing misleading performance discussions.