How to export

Once an audit is completed, the "Export to Excel" button appears in the main toolbar. Click it to open a file save dialog box. Choose the location and filename, then confirm.

The export generates a .xlsx file containing two worksheets: Results and Findings.

The export is available only after an audit has been executed in the current session. If you have just started the application without running an audit, the export button is disabled.

Results sheet

The Results sheet presents an audit summary:

  • The audited model name and the date/time of the audit.
  • The global score out of 100.
  • For each analyzed domain: the domain score, the weight in the global score and the number of findings detected.
  • Non-analyzed domains (for example, Performance if trace rights are missing) are indicated as "Not analyzed".

This sheet is designed to be shared quickly with a manager or client; it provides a synthetic overview at a glance.

Findings sheet

The Findings sheet contains the full detail of all detected problems, with the following columns:

Column Description
DomainThe concerned analysis domain (Modeling, DAX, VertiPaq, etc.).
RuleThe ID of the triggered rule (e.g., MOD005, DAX003).
SeverityHigh, Medium or Low.
ObjectThe name of the concerned object: table, measure, column or Power Query query.
DescriptionExplanation of the detected problem.
RecommendationConcrete action to take to fix the finding.

The sheet is formatted with row coloring according to severity (red for high, orange for medium, yellow for low) to facilitate reading and prioritization.

Recommended uses

Sharing with the team

The Excel file is the ideal format for sharing audit results with colleagues or stakeholders who do not have access to Power BI Audit. The Results sheet is sufficient for a quick review; the Findings sheet allows for detailed analysis.

Tracking over time

Export results at regular intervals (after each development sprint, before each production release) and keep the files. Comparing global scores and number of findings from one export to another will allow you to objectively measure the improvement in your model quality.

Fixes backlog

The Findings sheet can serve as a basis for a fixes backlog. Import it into your task management tool (Azure DevOps, Jira, Planner...) by filtering by severity to prioritize high corrections first.

An uncorrected high severity finding represents up to 15 penalty points on its domain score. Always prioritize high findings before treating medium and low ones.