These guides cover the public Azure DevOps Marketplace extension, its current permissions, personal storage, evidence boundaries, and supported environment.
Looking for QaCockpit Cloud documentation?01
Edition and launch questions
Is this the same as the Azure DevOps integration in QaCockpit Cloud?
No. The Cloud integration connects Azure DevOps to the hosted QaCockpit application. QaCockpit for Azure DevOps is a separate Marketplace extension whose experience lives inside Azure DevOps.
Does the extension replace Azure Pipelines or our test frameworks?
No. Azure DevOps remains the engineering and execution system. QaCockpit organizes the quality picture and keeps it connected to the exact evidence produced by existing automation.
Do we need a QaCockpit Cloud workspace?
Not for the normal Marketplace extension workflow. Teams that need a hosted cross-provider layer across GitHub Actions and Azure DevOps should choose QaCockpit Cloud.
Which permissions does the extension require?
The extension uses the signed-in Azure DevOps identity. Read access and pipeline commands require the corresponding native permissions. Queue and Stop are included, so Marketplace also discloses the vso.build_execute extension scope. A user without the native command permission cannot run that action.
Does it support Azure DevOps Server?
Not in version 1.0.0. The first public release supports Azure DevOps Services organizations at dev.azure.com only.
Does all data stay inside Azure DevOps?
Azure DevOps holds execution evidence. Personal campaigns, saved views, and Failure Inbox Status and Owner use personal Extension Data. A narrow QaCockpit service processes evaluation contact details, license state, and a first-open record containing the organization, version, and current-user identity supplied by Azure DevOps. It does not receive pipeline, project, test, or result data.
Will everyone see QaCockpit after installation?
No. Installation is organization-level, but QaCockpit access is off by default. You can enable it only for yourself in User settings > Preview features. An administrator can separately enable it for the organization.
How much will the Azure DevOps edition cost?
The initial release is a 60-day organization evaluation with no card or automatic renewal. Paid sales are planned separately at $49 USD per Azure DevOps organization per month. The offer is separate from QaCockpit Cloud and is not priced per user.
How do the evaluation and future subscription work?
The initial release provides a 60-day organization evaluation with no payment method and no automatic renewal. The exact end date is recorded when access starts. Paid sales are planned later at $49 per organization per month through Paddle.
What happens if the subscription expires?
Product data is not deleted. You can still review license status, renew, manage billing, and export your own saved configuration. Paid product views become available again after entitlement is restored.
When can we install it?
Install the extension from its public Azure DevOps Marketplace listing. An Azure DevOps organization administrator must review the publisher, scopes, policies, and pricing information before installation.