Repository navigation
Analytics Hub installer 0.6.7
Install from PowerShell
Paste this into PowerShell. It needs no admin rights: it downloads this release's installer as a zip, checks its SHA-256 and opens the installer in your browser.
irm https://github.com/microsoft/AnalyticsHub-Dashboard/releases/download/installer-v0.6.7/install.ps1 | iexTo keep the files, download install.ps1 and AnalyticsHubInstaller.zip from this release and, where your execution policy allows scripts, run .\install.ps1 -ZipPath .\AnalyticsHubInstaller.zip. With a Node.js your IT team has approved, add -UseInstalledNode: https://github.com/microsoft/AnalyticsHub-Dashboard/blob/main/docs/INSTALL.md#it-approved-nodejs. More: https://github.com/microsoft/AnalyticsHub-Dashboard/blob/main/docs/INSTALL.md#from-powershell
Or download the exe
Download AnalyticsHubInstaller.exe and open it. Steps: https://github.com/microsoft/AnalyticsHub-Dashboard/blob/main/docs/INSTALL.md
What changed
If you host on Azure, the Teams tab now signs in as it opens, also opens in Outlook and the Microsoft 365 Copilot app, and can be published to your org's app catalog. Installs report failed steps accurately, and the Executive summary opens sooner. Full list: CHANGELOG.
Before you update
- No model reset this time. 0.6.7 adds no schema migration. Repair or change updates the models in place and keeps their data.
- Coming from 0.6.5? Read the 0.6.6 notes first. That update clears model data once and makes the next pipeline run longer.
- Azure: one more admin sign-in. Publishing the Teams app to your org's catalog takes a second sign-in, as Microsoft Graph Command Line Tools. It needs the Teams Administrator or Global Administrator role and consent to
AppCatalog.ReadWrite.All. You can skip it and upload the package by hand. - Azure: a new Teams package. If you uploaded the Teams app by hand, upload the new
AnalyticsHub-Teams.zipagain, or let Repair or change publish it. Pinning it in Teams stays manual.
Known issues
-
"The installer couldn't start: Access to the path … is denied." Something, such as antivirus, was still scanning the files the exe had just unpacked. Run the exe again, or use the PowerShell command, which waits and retries.
-
Changing Group by on Adoption's Trend heatmap or Activation page replaces the app with "Something went wrong", and
Column "Chat + Agent Org DataOrganization" was not found.This happens on Fabric and Azure, and 0.6.6 has it too. Choose Try Again: the app reopens on Executive summary, grouped by Organization, with your filters reset. To see those pages grouped another way, change Group by on another page first, such as Executive summary, then open them. -
Azure: the "Power BI model" step can fail with "The connection DisplayName input is already being used by another connection". Choose Retry saved configuration, which takes over the connection that the first attempt made.
-
Azure with Public endpoints, the default: a new install stops at the "Power BI model" step with
DM_GWPipeline_Gateway_DataSourceAccessError. Power BI tests the database sign-in before the install has created the database user it signs in as, so retrying alone fails the same way. Updates of a working install, and installs with Private networking, aren't affected. To get past it, in Azure Cloud Shell or the Azure CLI, signed in to the install's subscription:-
Find the SQL reader's client ID:
az ad app list --display-name "Analytics Hub SQL Reader" --query "[].[appId,createdDateTime]" -o tsv. If it lists more than one, use the newest. -
Give it to the migration job, then run the job once:
az containerapp job update -g <resource group> -n job-vlens-migrate --set-env-vars VALUELENS_SQL_READER_CLIENT_ID=<client ID>az containerapp job start -g <resource group> -n job-vlens-migrate
The job is
job-<name prefix>-migrate, and the prefix isvlensunless you changed it.az containerapp job execution list -g <resource group> -n job-vlens-migrate -o tableshows when it has Succeeded, after about a minute. -
Choose Retry saved configuration, or run the installer again with the same choices. The "Power BI model" step may first say "Azure SQL is resuming…" and retry once; that's expected.
A fix is planned.
-
-
Azure: scheduled runs after the first load fail in processing, with
No files found that match the pattern …/curated/_valuelens_process/context/month-….parquet. The dashboard then stops updating, andstatusshows the runs as Failed. To work around it, runaz containerapp job update -g <resource group> -n job-vlens-run --set-env-vars VALUELENS_PROCESS_FULL_REBUILD=true(if you changed the name prefix, the job isjob-<prefix>-run). Every run then rebuilds all months, as before 0.6.6, so runs take longer. The next run catches up. An Update or Repair removes the setting, so set it again after either. A fix is planned. -
Azure: Share can't add people by email, and lists them by ID. On an Azure install, adding a person by email in the app's Share panel fails with "Microsoft Entra did not allow this change…", even for an admin. People in the viewer group are listed by ID rather than by name. Adding a group by its name works. To add people, run the installer's
accesscommand (Manage access in the browser) and choose Add viewers, or add them to the viewer group in My Groups or the Microsoft Entra admin center. -
Azure: turning on org-scoped access can fail with 403 AuthorizationPermissionMismatch. It reads the scope list before giving you access to the install's storage. Workaround: give yourself Storage Blob Data Contributor on the install's storage account (Azure portal > the storage account > Access control (IAM)), wait about 5 minutes, and try again.
-
Azure: a Repair with
--yes, or one that takes every default, moves a shared-capacity (Pro) install's workspace onto your first active capacity. Workaround: run Repair without--yes, and choose None (shared capacity, Pro) at Capacity for the Power BI workspace. -
A user who isn't an Entra admin can't create the viewer group. Setup,
accessand org-scoped access stop with Graph's 400 "Request contains a property with duplicate values" when they keep A new group. Workaround: choose A group I already have and pick a security group you own (or ask an admin to create one). -
Fabric: updating with Repair or change can keep the earlier version's app. When it asks whether to deploy the app again, the default is No unless the app's pages, currency or access changed, so taking the defaults leaves the earlier version's app on the new model. Answer Yes there, or choose Update, which redeploys the app by default. If you've already updated and kept the app, choose Update, or Repair or change again and answer Yes.
-
A Fabric trial capacity holds only a few SQL databases. A new install's app needs one. If none is free, the app step fails: free one, then run
deploy-app.
Check the download
SHA-256: 64157c43f38c41e01434d530efa21c258554e55140981f833acfd2c511b69cce
In PowerShell, in the folder you downloaded it to, run:
(Get-FileHash .\AnalyticsHubInstaller.exe -Algorithm SHA256).HashIt should match the hash above, which is also in AnalyticsHubInstaller.exe.sha256. PowerShell prints it in capitals; that doesn't matter. A match confirms the file is the one in this release, not who published it.
If your organisation blocks it
This build isn't code-signed yet, so Edge and Windows SmartScreen may warn about it. If your organisation's policy blocks it, don't work around it.
Use the PowerShell command above, another route in https://github.com/microsoft/AnalyticsHub-Dashboard/blob/main/docs/INSTALL.md, such as Azure Cloud Shell or running the installer with Node.js (https://github.com/microsoft/AnalyticsHub-Dashboard/blob/main/docs/INSTALL.md#without-the-exe), or ask your IT team.