Skip to content

purview-v1.11.5

Choose a tag to compare

View all tags
@Rance9 Rance9 released this 12 Jun 11:21
purview-v1.11.5
4bb93e7

PAX Purview Audit Log Processor v1.11.5

Version 1.11.5 adds support for the new AI Business Value (AIBV) Power BI dashboard and fixes a large-tenant reliability problem in the Entra user directory export. The headline change lets a single CopilotInteraction rollup run target either the existing AI-in-One (AIO) dashboard or the new AIBV dashboard from the same audit + Entra/MAC licensing data, selected by a new -Dashboard parameter. Existing rollup commands are unchanged — the default is AIO and produces byte-identical output to v1.11.4. Everything else is a reliability fix and its supporting tweaks; no existing switch is removed.

What's new in v1.11.5

  • AI Business Value (AIBV) dashboard support. PAX now produces rollup input for two Copilot Power BI dashboards from the same CopilotInteraction run: the existing AI-in-One (AIO) dashboard and the new AI Business Value (AIBV) dashboard. A new -Dashboard <AIO|AIBV|M365> parameter (default AIO) chooses the target. AIO and AIBV both run the embedded CopilotInteraction processor — upgraded from v3.1.0 to v4.0.0 — with the appropriate output profile, while M365 continues to route to the existing M365 Usage Bundle processor. The data PAX collects is identical for AIO and AIBV; only the shape of the rolled-up output differs, so no other switch or collection behavior changes. Smart defaulting keeps the command line minimal: omitting -Dashboard reproduces today's behavior exactly (AIO for a CopilotInteraction rollup, M365 when -IncludeM365Usage is present), -Dashboard M365 auto-enables -IncludeM365Usage, and supplying -Dashboard without a rollup switch auto-enables -Rollup. Cross-run append (-AppendFile / -AppendUserInfo) is supported for both the AIO and AIBV paths, and the selected dashboard is persisted in the checkpoint so a resumed AIBV run stays AIBV.

  • Reliable Entra user directory export on very large tenants. A failure that silently dropped the EntraUsers / MAC licensing file on tenants with very large directories (hundreds of thousands of users) is fixed. Previously the directory fetch aborted partway through with an internal paging-safety stop, the error was swallowed as a warning, and the run still printed === Enterprise Export Complete === while no EntraUsers file was written — making total data loss look like a clean success. The directory fetch now scales to large tenants, reports a failed or partial fetch loudly (in the end-of-run summary and via a new non-zero exit code), and still emits whatever was collected when a fetch stops early. Manager / org-hierarchy columns are unaffected.

The attached script is the v1.11.5 release build. See the documentation in the repository for full configuration details.

Assets 3
Loading