Clarify exact-window coverage, SQL fan-out and unmerged report fixes
Keep exact 90/180-day requests explicit even when weekly D7 evidence leaves a leading gap. Distinguish four report admissions from SQL command/connection fan-out, and identify draft follow-up fixes as excluded from the tested dev baseline and draft release. No readiness or candidate Azure-performance claim is added.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: b9a6835b-97dc-4e01-a9bd-1193fbd5fc53
Document actual Azure licence-report limits and unreleased status
Record the synthetic S4/S6 review, exact coverage limits and verified disposable-resource cleanup without identifying the benchmark environment.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: b9a6835b-97dc-4e01-a9bd-1193fbd5fc53
Document the Licence activity report (unreleased)
Adds a Licence activity guide and links it from the sidebar, Web Portal and
Security Model pages. The page is explicitly labelled as describing an
unreleased feature, because it is not in the current stable release.
The guide leads with interpretation rather than clicks, because almost every
way of getting this report wrong is a reading error: assigned users overlap
across SKUs and must not be summed; unknown coverage is not a measured zero and
must never place someone in the least-active list; supporting action counts are
snapshot averages, not manufactured daily totals; and the bands describe
frequency within available samples, not a common unit of work across products.
Also records the limits an operator will actually hit: 1-100 most/least and
page size, 100-character search, 1-10,000 pages, top-50 demographic breakdowns,
a 100-option-per-dimension filter catalogue that says when it truncates, the
five- and two-minute cache lifetimes, four concurrent shared report loads, the
30-second deadline and the 1 MiB response cap.
Includes the measured scale limit honestly: on a synthetic 300,000-user,
50-SKU database the 180-day window did not finish inside the 20-second command
timeout, so very large tenants should use shorter windows and will see a
retryable error rather than a slow page. That measurement was local rather than
Azure SQL and is labelled as such.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: b9a6835b-97dc-4e01-a9bd-1193fbd5fc53