QI Accelerate connector

Connect authorized Azure DevOps projects to QI Accelerate using a shared company application identity.

Included pages

• Work-item sync under Azure Boards: destination-scoped export defaults and an independent reviewed synchronization snapshot, discovered ADO types and fields, approval/archive/delete behavior, and an optional existing Test Plan/suite destination.
• Knowledge sync under Azure Repos: saved knowledge kinds and All/Approved-only rules for current and future items, optional Advanced topic/category filters, and an existing top-level project-wiki page. Legacy exact selections retain their saved identities until explicitly converted. Activation requires native event delivery for the current connection.
• Conflict review under Azure Boards: highlighted baseline/current differences, complete-version choices, current write-access checks and protection against stale reviews. Notification links open the selected conflict directly.
• Company connection under Organization settings: single-use company pairing, guided Entra consent and application access, verified connection health, and personal account linking.

New work items are created by the company application. The latest assigned reviewer becomes the assignee only when a unique current provider identity matches; otherwise the assignee stays blank. The account configuring synchronization does not become the background execution identity. The backend verifies company membership, linked account, project access, company project policy, entitlement and operation permissions on every command.

Installation requirements

Live operation requires a configured QI Accelerate gateway and backend, the QI-managed application registration and organization grants. A package with missing gateway configuration displays an explicit unavailable state. No sample data is included in production.

The local preview uses fictional data and in-memory commands for the same work-item and rule-based knowledge sync pages as the packaged extension.

Requested permissions

The extension requests vso.project, vso.work_write, vso.test, vso.wiki, vso.code and vso.graph. The work-item write scope includes read access and supports interactive destination validation. The remaining scopes support project, Test Plans, wiki/repository and Graph identity discovery and event configuration. The extension does not request a PAT or persist SDK tokens.

Unattended integration writes use the dedicated company application identity through the backend. Interactive extension permissions do not grant that application access: a customer tenant administrator must consent to the dedicated multitenant application, add its service principal to the Azure DevOps organization and grant customer-local project permissions. Company pairing and personal account linking remain separate.

This extension targets Azure DevOps Services. Premium or Enterprise two-way integration entitlement is required.

Data used by synchronization

The connector exchanges the work-item and wiki content selected by your company between Azure DevOps and QI Accelerate. Depending on the mapping, this includes requirements and their available process, project and non-functional details, test content, review checklists and knowledge pages. It also uses organization, project, team and user identifiers to select destinations, associate accounts and check access.

The QI Accelerate service retains connection settings, mappings, linked-item identifiers, synchronization state and content needed to detect and review conflicting edits. Content entered by users may include personal data. Your company controls which authorized projects and content are connected. Pausing synchronization stops further synchronization; it does not delete existing copies in either service.

For support, contact TestHuset. See TestHuset's privacy policy and your company's applicable service and data processing agreements for data-handling terms.

Get started and support

After installation, open Organization settings → QI Accelerate, pair your company, complete the guided consent/application permissions and verify the connection. Then open Boards → QI Accelerate sync to choose an authorized project, inspect the discovered types/fields and review synchronization settings. Saving export defaults alone does not activate a binding. Retained excluded content remains readable and stops synchronizing.

Use the Support and Privacy links on this listing. Customer tenant onboarding requires both tenant consent and Azure DevOps project grants.