Analytics Hub installer 0.6.8

Published as a pre-release first. 0.6.8 becomes Latest once a fresh install from its published exe passes. Until then, the releases/latest links, including the PowerShell command, still serve 0.6.7, and the installer doesn't offer 0.6.8 as an update. This command installs 0.6.8 either way: irm https://github.com/microsoft/AnalyticsHub-Dashboard/releases/download/installer-v0.6.8/install.ps1 | iex.

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.8/install.ps1 | iex

To 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

Check the download

SHA-256: 653097081feaf30690b00531bf63e43578582e40882edf3424fa9b2b682ab9f8

In PowerShell, in the folder you downloaded it to, run:

(Get-FileHash .\AnalyticsHubInstaller.exe -Algorithm SHA256).Hash

It 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.

What changed

What changed since 0.6.7: Every module now works on Azure: Agent Evaluator, the Agent 365 registry, product feedback and Workday org data install there too, and credit consumption is checked against Fabric. An Azure install can use a resource group your Azure admin creates, with least privilege, and setup sizes for tenants with more than 10,000 Copilot seats. On Azure, a long history loads and processes within the run job's memory and disk, runs after the first load no longer fail in processing, the installer doesn't start a run while another is going, a new install with public endpoints completes, uninstall works in a resource group you already had, Share adds people by email, private networking leaves private DNS zones already in the resource group alone, turning on org-scoped access and scoped delegation in Share no longer fail, and Repair keeps a shared-capacity (Pro) install's workspace where it is. Agent Evaluator reads every Copilot Studio transcript, on both paths. A user who isn't an Entra admin can now create the viewer group. Install and update check the prerequisites themselves, and the installer checks that the app can read the audit log, with a new check-audit command. The app's first pages load sooner, several of its slowest queries are faster, it fetches ahead only the next two pages, and when more than 10,000 people have Copilot activity it opens on the last 12 weeks. Changing Group by no longer crashes two Adoption pages, and the Executive summary no longer says everyone has a department. M365 Activity refreshes incrementally, refresh does less work for Consumption Central and Agent Evaluator, and users in the Microsoft 365 Copilot usage report count as licensed. On Fabric, the installer has you sign in to Viva Insights first when Cowork credits come from the Dataflow, Repair or change redeploys the app after an update, and the app shows saved task times, report packs and commercial terms again: check your terms after updating. The README sets out setup step by step, from prerequisites to after setup, and points to ValueLens and Consumption Central for a more targeted report. Azure by hand, in Azure Cloud Shell, works once 0.6.8 is Latest. The details are below, and the release candidates' are in the CHANGELOG.

Update an existing install: run the command above, or open installer 0.6.8, and choose Update. On Azure, that redeploys with this version's images, adds the Agent Evaluator, Agent 365 and product feedback tables (migrations V008 to V010), and redeploys and reloads the ValueLens model; the jobs' next run recomputes every month once. On Fabric, it redeploys and reloads the ValueLens model, redeploys the notebooks, updates and republishes the Ask data agent, and offers to replace the pipeline and redeploy the app: let it redeploy the app. To turn on a module Azure now supports, choose Repair or change, then Data collection; Agent Evaluator's environments are under Module connections, and Workday org data is under the advanced settings: see Workday org data. Some Azure installs that ticked Credit consumption before 0.6.8 keep Copilot Studio and Cowork left out: to turn them on, choose Repair or change, then Module connections, and pick their sources. If you use Agent Evaluator, update as a System Administrator of each of its environments, then reload the history once, as below. The tag also publishes the valuelens-jobs and valuelens-web images as 0.6.8.

Azure: the installer doesn't start a run while one is going. It used to start the run job without checking, so a Repair or change during a long first load started a second run beside it, and the two shared the audit staging area and the tenant's audit queries. Now the installer checks the run job before the first load, a history reload, org-scoped access or run starts it. If a run is going, it doesn't start another: it says which run is going, and what to run once it has finished. A history reload that doesn't start isn't recorded, so the next Repair or change offers it again. As on Fabric, run then exits with an error, a run that started more than 24 hours ago doesn't count, and if the installer can't check, it starts the run as before.

Azure: private networking no longer takes over private DNS zones already in the resource group. With private networking, an install creates its privatelink.* zones in its resource group unless you choose otherwise. When an existing resource group already had a zone of the same name, the deployment updated it in place and tagged it as the install's own, so uninstalling tried to delete it, with every record in it. A second install, in a group where an earlier one had created the zones, did the same to the first install's zones. Now the preflight stops before anything is deployed when a zone the install would create is already there without its tag. It names the zones and says how to go on: choose Use existing zones in another resource group and give that resource group, after creating any of the zones that aren't there yet, or install into another resource group.

• Still goes ahead: a Repair or Update over zones the install created itself, public networking, Use existing zones, Leave DNS to Azure Policy or the network team, and privatelink.* zones the install doesn't create, such as Key Vault's.
• An install that already took over a zone isn't detected: the zone now has that install's tag, and the install record doesn't say which zones were there before it.

Azure: Share adds people by email, and shows viewers' names. In 0.6.7 and the 0.6.8 release candidates, on an Azure install with a viewer group, adding someone by email in Share failed, even for a directory admin, with "Microsoft Entra did not allow this change. Only owners of the viewer group and directory admins can change its members." Share also listed the people in the group by their object ID. The web app could change the group, but it had no permission to look people up. With the viewer group (the default), the installer now also gives it delegated Graph User.ReadBasic.All. That reads basic profiles only (name, email address and photo), not User.Read.All. Without a viewer group, nothing changes. Fabric isn't affected: there, Share opens the group in My Groups.

• Update an existing install: run the installer and choose Update, or Repair or change. It adds the permission to the web app's registration and grants it, with no other step. If you can't grant admin consent, it gives you a link to send to an admin, as for the web app's other permissions.
• When Entra refuses a lookup, Share says so. It says Microsoft Entra didn't let Analytics Hub look up people by email (or groups by name), and that Repair or change in the installer, or an Entra admin's consent, fixes it. "Only owners of the viewer group and directory admins can change its members" is now only for a change to the group that Entra refused. With org-scoped access, an admin who gives or approves a scope gets the new message too, instead of a scope left waiting for approval or the message about owners. A scope a leader gives still waits for an admin.

App: fetches ahead only the next two pages. Once the page on screen has loaded, the app used to fetch the first tab of every other page in the background, about 45 queries per open. It now fetches the first tab of the next two p...

Analytics Hub installer 0.6.8-rc.2

Release candidate. This pre-release is for testing 0.6.8 before it's released. The installer doesn't offer it as an update, and https://github.com/microsoft/AnalyticsHub-Dashboard/releases/latest stays on the last release.

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.8-rc.2/install.ps1 | iex

To 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

Check the download

SHA-256: 54225bce3828b2832fcae10d100402be0f66490b25efb63295f28fa66e81e9c7

In PowerShell, in the folder you downloaded it to, run:

(Get-FileHash .\AnalyticsHubInstaller.exe -Algorithm SHA256).Hash

It 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.

Known issue

On an Azure install done by hand, the browser's developer tools show 400 "Cannot find table" errors. They're expected: the guide publishes the ValueLens template without the tables the installer adds, so the parts of the app that need them stay off, as Azure, by hand lists.

Analytics Hub installer 0.6.8-rc.1

Release candidate. This pre-release is for testing 0.6.8 before it's released. The installer doesn't offer it as an update, and https://github.com/microsoft/AnalyticsHub-Dashboard/releases/latest stays on the last release.

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.8-rc.1/install.ps1 | iex

To 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

Check the download

SHA-256: 0b3f7a4afc9464b110aa67774bb4b3f3121a050e2b1fd297f06123501753659e

In PowerShell, in the folder you downloaded it to, run:

(Get-FileHash .\AnalyticsHubInstaller.exe -Algorithm SHA256).Hash

It 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.

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 | iex

To 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.zip again, 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:

  1. 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.

  2. 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 is vlens unless you changed it. az containerapp job execution list -g <resource group> -n job-vlens-migrate -o table shows when it has Succeeded, after about a minute.

  3. 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, and status shows the runs as Failed. To work around it, run az 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 is job-<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 access command (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, access and 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).Hash

It 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.

Analytics Hub installer 0.6.6

Install from PowerShell

1. Open PowerShell (no admin rights needed) and paste:

   irm https://github.com/microsoft/AnalyticsHub-Dashboard/releases/download/installer-v0.6.6/install.ps1 | iex

   It downloads this release's installer as a zip, checks its SHA-256 and opens the installer in your browser.

2. Sign in, choose Fabric or Azure, your capacity and workspace, and follow the steps to the end. The first load runs at the end.

3. To update an existing install, run the same command and choose Repair or change.

To 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. 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

The app shows less on each page and paces its queries, so it stays quick for a large tenant. The install is sized by Copilot seats, daily processing handles only new days, and an install that stops part way picks up where it left off. A card that shows Power BI is busy retries for up to a minute, then loads again by itself once that model answers. Full list: CHANGELOG.

Before you update

• Model data is cleared once. The models gain new columns, so the update asks before Fabric clears a model's data, then reloads it. Reports on it are empty until the reload finishes.
• The next pipeline run is longer. It rebuilds the curated audit fact once and fills the new columns, which are empty until then.
• Fewer cards. Some slow cards are gone, long lists load on Show …, and Group by no longer offers per-person fields.
• A Fabric trial capacity holds only a few SQL databases (5 on the trial we tested). The app needs one. If none is free, the app step fails; free one and run deploy-app.
• Not code-signed yet, so Edge and SmartScreen may warn about the exe. If your organisation blocks it, use the PowerShell command or ask your IT team.
• Known issue: if you host on Azure, the Teams tab can't sign in yet. Use the web link instead. 0.6.7 fixes it.

Check the download

SHA-256: 13cccc77ccef16a953f73b95a3ec172df4905c6ea533fe7cd3565f018e8f437c

In PowerShell, in the folder you downloaded it to, run (Get-FileHash .\AnalyticsHubInstaller.exe -Algorithm SHA256).Hash. It should match the hash above and AnalyticsHubInstaller.exe.sha256.

Analytics Hub installer 0.6.5

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.5/install.ps1 | iex

To 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

Check the download

SHA-256: 52be7cc0192f11a301462dcbe01bbbd4768a83b97bd39ee71ac9ca5411c218fc

In PowerShell, in the folder you downloaded it to, run:

(Get-FileHash .\AnalyticsHubInstaller.exe -Algorithm SHA256).Hash

It 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.

Analytics Hub installer 0.6.2

What's new in 0.6.2

0.6.2 is the current release: the releases/latest download links and the PowerShell command now serve it. It is the first Latest release since 0.5.1, so it includes everything from the 0.6.0 and 0.6.1 pre-releases. To update an existing install, open this installer and choose Repair or change. On Azure, Repair pulls the 0.6.2 images and runs any migrations the install hasn't had yet.

• Azure Cloud Shell. Before Go ahead?, the plan now says to keep the Cloud Shell tab open (not the PC awake). Without a storage account, each run ends by saying how to download the install record, and a record uploaded with Manage files > Upload is picked up, so running again carries on instead of setting up a second copy.

Coming from 0.5.1: see 0.6.0 and 0.6.1 for the PowerShell command and Cloud Shell, the no-Key-Vault default for new Fabric installs, region preflight and private networking for Azure under policy, the app's report packs, Ask, org-scoped access and delegation, and the fixes from testing. Full list: CHANGELOG.
Download AnalyticsHubInstaller.exe and open it. Steps: https://github.com/microsoft/AnalyticsHub-Dashboard/tree/main/fabric#install

Or install from PowerShell

If your organisation blocks downloaded exes, paste this into PowerShell instead. 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.2/install.ps1 | iex

If irm | iex is blocked too, download install.ps1 and AnalyticsHubInstaller.zip from this release and run powershell -ExecutionPolicy Bypass -File .\install.ps1 -ZipPath .\AnalyticsHubInstaller.zip. More: https://github.com/microsoft/AnalyticsHub-Dashboard/blob/main/installer/README.md#from-powershell

Check the download

SHA-256: b14c9fcae92fb99a0ea53906e9c6c14f5b49cda31485083631d1ea4303ebbc99

In PowerShell, in the folder you downloaded it to, run:

(Get-FileHash .\AnalyticsHubInstaller.exe -Algorithm SHA256).Hash

It should match the hash above, which is also in AnalyticsHubInstaller.exe.sha256. PowerShell prints it in capitals; that doesn't matter.

If Edge or Windows warns you

This build isn't code-signed yet, so Edge and Windows SmartScreen don't recognise it. Check the hash first, then:

• If Edge says it isn't commonly downloaded, choose … next to the file, then Keep, Show more and Keep anyway.
• If Windows says it protected your PC, choose More info, then Run anyway.

If your organisation blocks the download, use the PowerShell command above, or run the installer with Node.js instead: https://github.com/microsoft/AnalyticsHub-Dashboard/blob/main/installer/README.md#without-the-exe

Analytics Hub installer 0.6.4

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.4/install.ps1 | iex

To 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

Check the download

SHA-256: 668229e637fb403257d78e2171b1ac8ca47cac67b3668a25ea03365d0c845fc5

In PowerShell, in the folder you downloaded it to, run:

(Get-FileHash .\AnalyticsHubInstaller.exe -Algorithm SHA256).Hash

It 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.

Analytics Hub installer 0.6.3 (pre-release)

Pre-release, for testing. The releases/latest links still serve 0.6.2. Use the pinned command below to try 0.6.3.

What's new in 0.6.3

What the installer deploys is the same as 0.6.2. This release changes how you can run it, the docs and what's in the download.

• PowerShell is the default route. The docs now lead with the PowerShell command, then the exe, Azure Cloud Shell and running with Node.js.
• Use an IT-approved Node.js. -UseInstalledNode, or $env:ANALYTICS_HUB_USE_INSTALLED_NODE = '1', runs the installer with the x64 Node.js 22.13+ or 24.x already on the PC instead of the zip's.
• A smaller download. The zip no longer carries build-only packages the installer doesn't use.
• Docs restructure. The long README is split into pages under docs/.
• The tag publishes the valuelens-jobs and valuelens-web images as 0.6.3.

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.3/install.ps1 | iex

To 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

Check the download

SHA-256: 07410d426e2f0f0081d8662d1fbf57183a07a57d20e7b222f0fc215d57b5cab4

In PowerShell, in the folder you downloaded it to, run:

(Get-FileHash .\AnalyticsHubInstaller.exe -Algorithm SHA256).Hash

It 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.

Analytics Hub installer 0.6.1 (pre-release)

Pre-release, for testing. 0.6.1 isn't the latest release yet, so the releases/latest download links and the installer's update notice still point at 0.5.1. Use the downloads and the pinned PowerShell command below.

What's new in 0.6.1

0.6.1 fixes problems found while testing 0.6.0. To update an existing install, open this installer and choose Repair or change. On Azure, Repair pulls the 0.6.1 images and runs migration V006, and the next data load fills the new columns.

• Azure first data load. The model refresh no longer fails with "The 'Agent_Key' column does not exist". The Azure jobs now add the same agent link and agent type columns as the Fabric notebook.
• Azure upgrades. On an install upgraded from 0.6.0, the audit collect no longer fails with "Referenced column "AgentPlatform" not found".
• Azure SQL free offer. When Azure turns down the free offer, set-up carries on with a serverless database instead of stopping.
• Installer. The app deploys as the person who signed in to the installer, not a saved sign-in for another account.
• PowerShell launcher. -Uninstall and removing an older version work in Windows PowerShell 5.1.
• Plan review. The no-Key-Vault notebook secret shows as New.
• The valuelens-jobs and valuelens-web images are published as 0.6.1.

Full details are in the CHANGELOG.

Install

Download AnalyticsHubInstaller.exe and open it. Steps: https://github.com/microsoft/AnalyticsHub-Dashboard/tree/main/fabric#install

Or install from PowerShell

If your organisation blocks downloaded exes, paste this into PowerShell instead. 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.1/install.ps1 | iex

If irm | iex is blocked too, download install.ps1 and AnalyticsHubInstaller.zip from this release and run powershell -ExecutionPolicy Bypass -File .\install.ps1 -ZipPath .\AnalyticsHubInstaller.zip. More: https://github.com/microsoft/AnalyticsHub-Dashboard/blob/main/installer/README.md#from-powershell

Check the download

SHA-256: f8837420323a9e448b55a4773ea03cda53a93bbd9a168b06e2f39b73db3c7dea

In PowerShell, in the folder you downloaded it to, run:

(Get-FileHash .\AnalyticsHubInstaller.exe -Algorithm SHA256).Hash

It should match the hash above, which is also in AnalyticsHubInstaller.exe.sha256. PowerShell prints it in capitals; that doesn't matter.

If Edge or Windows warns you

This build isn't code-signed yet, so Edge and Windows SmartScreen don't recognise it. Check the hash first, then:

• If Edge says it isn't commonly downloaded, choose … next to the file, then Keep, Show more and Keep anyway.
• If Windows says it protected your PC, choose More info, then Run anyway.

If your organisation blocks the download, use the PowerShell command above, or run the installer with Node.js instead: https://github.com/microsoft/AnalyticsHub-Dashboard/blob/main/installer/README.md#without-the-exe