PowerBI.tips

Business Ops Has Moved to GitHub

September 2, 2026 By Mike Carlo
Business Ops Has Moved to GitHub

Business Ops Is Now on GitHub

Business Ops has moved from the PowerBI.tips Products area to its official GitHub home: github.com/MikeCarlo/BusinessOps.

Business Ops is a Power BI Desktop companion that helps you install, update, launch, and manage community-built Power BI external tools. It is designed to make useful tools such as DAX Studio, Tabular Editor, Bravo, and Report Analyzer easier to discover and maintain.

Why We Moved It

GitHub is a better home for an open-source utility. Moving Business Ops there improves distribution, gives users a direct place to find releases and report issues, and makes ongoing code management simpler for maintainers and contributors.

The repository is now the source of truth for the project, including its code, release history, installation guidance, and future updates.

Get Business Ops

Visit the official Business Ops repository to learn more, download the latest release, or contribute:

Existing links to the former Business Ops product pages now redirect here so Power BI users can find the project without landing on a missing page.

What Is Business Ops?

Business Ops is a single place to manage external tools for Power BI Desktop. External tools extend Power BI development with capabilities for DAX authoring, semantic-model editing, diagnostics, documentation, and report analysis. The GitHub repository includes current setup information and the project version history.

Previous

Power BI Layouts Have Evolved: Download PBIR Files from the Gallery

More Posts

Oct 24, 2026

How Deplavity Was Born (and Everything We Made Because of It)

On Explicit Measures episode 573, Mike Carlo tried to say "deployment savvy" and invented Deplavity instead. Here is where the slip happened, how it turned into a fake prescription drug, and every video, ad, and jingle made because of it.

Oct 20, 2026

Fabric Deployment Plan - Ep.573

Fabric deployment plans let you order deployments and run notebooks or pipelines before and after each item lands, which finally gives data a place in the release. Mike Carlo and Tommy Puglia work out which teams should reach for a plan, which should stay in Git and GitHub Actions, and why both would wait for GA.