DMV Query Extraction in DAX Studio

Problem Context

You have five fixed DMV queries that need to be automatically extracted to a file.
The source is a .pbit report (Power BI template), not a web service or an exposed Tabular model.
The execution environment will be non-interactive (CLI/script) in Azure (VM or container).
DAX Studio is the usual manual tool for this, but it’s designed for GUI use and doesn’t provide a command-line interface to “open file → execute DMVs → export”.

Acceptance Criteria (what “unblocked” means)

Given a valid .pbit file, the non-GUI process is capable of materializing or accessing a Tabular model suitable for DMV queries.
The five DMV queries execute without human intervention.
A single Excel file with five correct and complete sheets is generated.
The process fails gracefully with auditable logs if the .pbit cannot produce a model or if any DMV query fails.
The same behavior is maintained across re-runs and clean deployments in the Azure environment.

That’s the full picture of the problem.
If you manage to solve it, you move from a desktop-only workflow to a scriptable pipeline that extracts your five DMV queries into Excel—no buttons, no GUI, fully automated.