# XrmToolBox puts Dataverse administration in one Windows window

> XrmToolBox is a GPL-3.0 Windows desktop application that connects to the Common Data Service and gathers more than 30 plugins for configuring and customising Dynamics 365 and model-driven PowerApps, and its real strength is that other developers can add their own tools to it.

**MscrmTools/XrmToolBox** — An application that gather multiple tools to ease the customization and configuration of Microsoft Dynamics CRM/365/Dataverse/PowerApps

- Repository: https://github.com/MscrmTools/XrmToolBox
- Website: https://www.xrmtoolbox.com
- Stars: 653 · Forks: 238
- Language: C#
- License: GPL-3.0
- Published: 2026-10-21 · Updated: 2026-10-21 · Language: en
- Canonical page: https://hysenlabs.com/projects/mscrmtools-xrmtoolbox

## What it connects to and who it is for

XrmToolBox is a Windows application that connects to the Common Data Service for Apps, known as CDS. The README explains why that is a wide target: Dynamics 365 Customer Engagement applications, such as Dynamics 365 for Sales, Service or Talent, all use the Common Data Service as their foundational data service.

So the tool covers anything built on CDS, including Dynamics 365 CE, formerly CRM, and model-driven PowerApps. It is described as providing tools to ease customisation, configuration and operation tasks, and it ships with more than 30 plugins for making administration, customisation and configuration tasks easier and less time consuming.

The user is implied by that feature list. This is not a tool for end users of a CRM, and it is not a development IDE. It is for the people who administer and customise a Dataverse environment: the consultant asked to tidy up a solution, the developer who needs to inspect what a deployment actually contains, the administrator who wants to look at data across entities without writing a query client.

Everything happens against a live environment you connect to, which is why the wiki's connection documentation matters as much as the plugin list. The tool is a client for an environment that already exists.

## The plugin model is the part worth copying

The README singles out one point as one of the great points about XrmToolBox, and it is not a feature of the application itself: the capability to welcome external plugins written by other developers, just by implementing specific parts of XrmToolBox code.

That is a design decision with consequences. A toolbox that only contains its own thirty tools has a fixed feature set and a fixed release cycle. A toolbox that defines an interface for tools has a feature set that grows without the core team shipping anything, and the growth is distributed to people who know one narrow task better than the core maintainers do.

The repository layout backs this up. There is a dedicated XrmToolBox.Extensibility project, which is where the contract for a third-party tool has to live, alongside XrmToolBox.ToolLibrary for the shared tool infrastructure, XrmToolBox.PluginsStore for the store that lists available plugins, and a Plugins/ directory holding the plugins that ship inside the application itself.

The PluginsStore is worth noting on its own. It is a separate project, not a feature of the main window, which suggests that discovering and installing third-party tools is treated as a first-class concern rather than a menu item. For an administrator assembling a workstation, that distinction decides whether adding a new tool is a click or a side project.

## The solution layout describes the whole product

The repository is a Visual Studio solution, XrmToolBox.sln, and the project directories give a fair map of what the application does.

XrmToolBox/ is the application itself. Commands/ is a separate project, which usually means the command layer is decoupled from the user interface and can be driven or tested separately. Referenced Assemblies/ holds the assemblies the tool builds against, which in a solution that loads plugins at runtime is the mechanism that keeps the plugin contract versioned.

Then there are the supporting projects. XrmToolBox.AutoUpdater is the update mechanism, which for a desktop tool distributed outside the Microsoft store is the difference between running a current version and a two year old one. MigrationBackup sits alongside it, and given the name it is the component that protects data when a tool performs a migration, which is the kind of precaution you want in a client that writes to a production environment.

LicenseChecker/ is the last one, and it is a reminder that plugins come from third parties. The application checks licences, which in an enterprise deployment is usually a requirement rather than a nicety, and the fact that the check is a first-class component says the tool is expected to run in a managed environment.

## Windows only, and connected to a live environment

Two constraints shape who can use it, and both are stated rather than implied.

The first is the platform. XrmToolBox is a Windows application, and the repository carries a .vs/ directory, which is Visual Studio's own metadata directory, along with a solution file and a Referenced Assemblies folder, all of which describe a desktop application built on Windows tooling. There is no indication of a cross-platform build, so a team on macOS or Linux is out of luck without a virtual machine, which is the standard workaround and also a cost.

The second is the nature of the connection. The tool connects to a Common Data Service environment and operates on it, which means the credentials it uses are typically a real account with real permissions in that environment. The wiki's help on how to connect to a Microsoft Dynamics CRM deployment is listed as one of the things the documentation covers, and the notes on prerequisites alongside it.

That combination, a Windows desktop client with administrative rights against a live tenant, is exactly what makes the tool useful to a consultant and exactly what makes a security team ask questions about it. The README's guidance is to consult the wiki on prerequisites, which is where the permission story is set out.

## The documentation lives in the wiki, and it is a request for help

The documentation for XrmToolBox is the wiki of the GitHub repository, and the README describes what it holds: prerequisites, a list of existing plugins, help on how to connect to a Microsoft Dynamics CRM deployment, and more.

The list of existing plugins is the practically important part. With more than 30 plugins shipped and an open model for third-party ones, the question for a new user is not what XrmToolBox can do but which plugin does it, and that list lives in the wiki rather than in the README or in the code.

The README also asks for help filling the wiki, asking anyone who feels they can contribute to create a GitHub account and help fill it with as much interesting content as possible. That is a signal about the state of the documentation: it exists, it is where the answers are, and it is short of content in places.

Bugs and suggestions go to the GitHub issues section, which the README also notes requires an account. Between the wiki for questions and the issue tracker for problems, there is no separate support channel, which is normal for a community tool and is worth knowing before a rollout.

## Dated versions, frequent releases, and an auto updater

The version scheme is the first thing to understand about the release cadence, because the numbers are not semantic versions. The recent releases are v1.2026.9.78 published on 2026-09-30, v1.2026.8.76 on 2026-08-18 and v1.2026.8.75 on 2026-08-03.

Reading them, the version encodes the year, the month and a build counter, which is the pattern for a desktop tool that has to be rebuilt often to track a platform that ships updates of its own. The major version has been 1 throughout, and the year and month move with each release rather than the minor number.

Two releases in August and one at the end of September is a release every few weeks, and the XrmToolBox.AutoUpdater project is the mechanism that delivers them. For a tool that connects to a cloud platform, keeping the client current matters because the platform side changes, and a stale client that talks to a newer environment is a support call waiting to happen.

The repository is not archived and the last push was on 2026-09-30, the same day as the newest release, so the work is current. The build itself runs on AppVeyor, with the badge in the README pointing at the ci.appveyor.com project.

## GPL-3.0, free to use, and supported by donations

The licence is GPL-3.0, with LICENSE.txt at the repository root. For a tool that people install on a workstation and connect to a customer tenant, the copyleft terms mean that a modified build you distribute carries obligations, while running it internally does not raise the same questions.

The project states its funding model plainly: XrmToolBox is a free tool and will remain like this, and the README asks for donations through PayPal if the tool has improved your productivity or saved time on a Dynamics CRM project. There is a donors page on the project website and a LicenseChecker project in the solution, which is the piece that keeps the licence and the third-party plugin licensing in view.

The combination of a GPL licence, a wiki maintained by volunteers, a busy release line and a donation link describes a project sustained by its users rather than by a vendor. For an evaluator that matters in one specific way: the tool is not going to be acquired or sunset by a company, and the continuity you get comes from the people who use it, which is the same reason the plugin list is the strongest part of the offer.

## Conclusion

XrmToolBox fits a Dynamics or Dataverse consultant or developer who spends their day in the platform admin area and wants the repetitive work, from schema edits to solution management, done through a desktop tool with a plugin ecosystem, rather than through the web portal. It does not fit a Linux or macOS shop, since it is a Windows application, and it does not fit a team that wants a supported vendor product rather than a community tool. Before installing it, read the wiki section on prerequisites and on connecting to a deployment, plan for the fact that the tool needs real credentials against the environment, and pin a version if a specific plugin build matters to you, since the releases are dated and frequent.

## FAQ

### What does XrmToolBox connect to?

It is a Windows application that connects to the Common Data Service for Apps, which is the foundational data service for Dynamics 365 Customer Engagement applications such as Sales, Service and Talent, and it covers anything built on CDS including model-driven PowerApps.

### Can other developers add their own tools to XrmToolBox?

Yes. One of the stated strengths of the tool is its capability to welcome external plugins written by other developers just by implementing specific parts of XrmToolBox code, and the repository has a dedicated XrmToolBox.Extensibility project plus an XrmToolBox.PluginsStore for the plugin listing.

### Is XrmToolBox free and open source?

It is released under the GPL-3.0 licence, with LICENSE.txt at the repository root, and the README states that it is a free tool and will remain so, with donations accepted through PayPal.

### Where is the documentation for XrmToolBox?

In the GitHub wiki of the XrmToolBox repository, which covers prerequisites, a list of existing plugins, help on connecting to a Microsoft Dynamics CRM deployment and more. Bugs and suggestions go to the repository's issues section.

### How often is XrmToolBox released?

Frequently, with dated version numbers. The recent releases are v1.2026.9.78 on 2026-09-30, v1.2026.8.76 on 2026-08-18 and v1.2026.8.75 on 2026-08-03, and the project ships an XrmToolBox.AutoUpdater component to deliver them.

## Sources

- [License: GPL-3.0](https://github.com/MscrmTools/XrmToolBox/blob/master/LICENSE)
- [MscrmTools/XrmToolBox on GitHub](https://github.com/MscrmTools/XrmToolBox)
- [Project website](https://www.xrmtoolbox.com)
- [README](https://github.com/MscrmTools/XrmToolBox/blob/master/README.md)
- [Releases](https://github.com/MscrmTools/XrmToolBox/releases)

---

Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/mscrmtools-xrmtoolbox