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
Access follows your Azure permissions
Extension scopes and your effective project, pipeline, repository, Analytics and agent-pool permissions both constrain access. Viewing results does not grant permission to queue or cancel a pipeline. QaCockpit does not ask you to create a Cloud workspace or enter a personal access token.
Review the scopes shown by Marketplace before installing or approving an update. Diagnostics shows the current organization, project, extension version and effective capabilities. The separate native QaCockpit access setting controls navigation visibility without changing those permissions.
02
Pipeline Intelligence uses three additional read-only scopes
vso.codereads the exact run commit to locate one unique YAML task after you open an affected run. QaCockpit does not change or persist source code or scan YAML across the portfolio.vso.analyticsreads bounded run, stage, job, task and agent-request timing facts for the selected 7, 14 or 30-day window.vso.agentpoolsreads pools, queues, agents and recent jobs for aggregate, anonymized capacity views. Worker identities, capabilities and raw assignments are not displayed or persisted.
Your native Azure permissions still apply. Inaccessible projects and pools are not disclosed, and a missing Analytics observation remains Not available instead of becoming zero.
03
Storage and evidence
Campaigns, saved views and their report records use personal Extension Data storage. Failure Inbox Status, Classification and Owner also use personal storage and are labelled Private to you. They are not a shared team workflow in the first public release.
Azure DevOps holds the execution evidence. The extension reads Azure Test Run and Result APIs, with bounded recovery from compatible retained JUnit artifacts. It does not store complete test evidence in Extension Data.
A narrow QaCockpit service processes the immutable Azure organization identifier, evaluation contact and consent record, entitlement state and, after paid sales are enabled, minimum billing state. On first open it also records the organization, extension version, and current-user identity fields supplied by Azure DevOps. Azure DevOps does not expose a verified installer identity, so the record is explicitly labelled first observed user. Missing identity fields retain an availability reason. The service does not receive project names, pipeline names, test names, results, saved workspace content, or interaction analytics. Reports link exact executions, so reopening them and exporting PDFs depends on the evidence still accessible under Azure DevOps permissions and retention.
04
Partial or changed access
If evidence becomes unavailable, check your current access to the exact project, pipeline, repository, pool and execution. A saved report link does not grant access to the underlying resource. Contact your Azure DevOps administrator for the access needed by your role.
When an evaluation or subscription is inactive, QaCockpit stops loading product evidence but preserves personal configuration. Access status, extension requests or future billing management, and personal configuration export remain available.
Azure DevOps Services at dev.azure.com is supported. Azure DevOps Server is not supported. Available history remains bounded by the selected analysis window, API limits, Azure permissions and retention.
Provider references: extension manifest and scopes and Extension Data storage.