Install QaCockpit for Azure DevOps

QaCockpit for Azure DevOps documentation

These guides cover the public Azure DevOps Marketplace extension, its current permissions, personal storage, evidence boundaries, and supported environment.

Looking for QaCockpit Cloud documentation?

Install from the verified Marketplace listing

Use the install action below. Confirm that the listing is published by Vorgan, is named QaCockpit for Azure DevOps, and links back to qacockpit.app for documentation, privacy, terms, and support.

Install from Azure DevOps Marketplace Explore the Azure DevOps edition View documentation

Installation is organization-level, but QaCockpit access is off by default. Installing does not make its navigation visible to teammates, start the evaluation, run pipelines, or modify Azure DevOps data.

Prepare an Azure DevOps administrator

Azure DevOps generally requires a Project Collection Administrator, organization owner, or a user with the documented collection-level permission to install an extension. Organizations should decide who owns extension review, installation, evaluation activation, and later subscription administration.

Before installation, review the stable listing's publisher, extension identity, requested scopes, privacy policy, support link, and release notes. Do not approve a package whose identity or scopes differ from the release evidence.

Version 1.1.0 adds read-only Code, Analytics, and Agent Pools scopes for Pipeline Intelligence. Existing installations require an organization administrator to authorize these scopes before Azure DevOps can complete the upgrade.

Release-day installation flow

Open the verified QaCockpit listing from this documentation.
Select the intended non-production or production Azure DevOps organization.
Review the publisher, scopes, privacy, support, and pricing information.
Install the extension and return to that organization.
Enable QaCockpit access only for yourself, or ask an administrator to enable it for the organization.
Open Subscription, start the 60-day no-card evaluation, then follow Getting started.

After activation and refresh, open the QaCockpit group in project navigation, then Quality Board, Pipeline Intelligence, Test Intelligence, or Campaigns. Start with non-production projects until your administrator has verified access and command permissions.

Verify before onboarding real projects

The installed publisher and extension IDs match the approved stable artifact.
The QaCockpit contribution loads, follows the current theme, and resizes correctly.
A user with limited project access sees only authorized Azure DevOps resources.
Empty and partial-permission states explain the next safe action.
No Cloud workspace or Cloud provider secret is requested by mistake.
Subscription and Diagnostics show the same exact evaluation end date.

Provider reference: Install extensions in Azure DevOps.