System requirements
Azure DevOps Services only, HTTPS, supported browsers, and Stripe billing prerequisites for ADO Pilot.
Last updated
ADO Pilot is a cloud service. You can run it against any Azure DevOps Services organization that is reachable over HTTPS from the public internet, with a modern browser for the management portal and a Stripe-supported payment method for paid plans.
Azure DevOps platform
| Platform | Supported in v1 |
|---|---|
| Azure DevOps Services (cloud) | Yes |
| Azure DevOps Server (on-prem) | No |
On-premises Azure DevOps Server is not supported in v1 and is not on the near-term roadmap. The webhook architecture relies on your organization's service hooks reaching adopilot.dev over HTTPS, which an air-gapped Server install cannot do.
Network and security
- All ingress and egress is over HTTPS. Azure DevOps service hooks reject
http://andlocalhosttargets, and ADO Pilot only exposes HTTPS endpoints. - If your organization restricts outbound traffic, allow HTTPS to
adopilot.devfrom the management portal and toapi.stripe.comfor billing. - Azure DevOps service hooks do not support HMAC signing. Webhook authorization to ADO Pilot's ingress is enforced with a per-tenant JWT that the wizard provisions automatically.
Browser support
The management portal at adopilot.dev is tested against the latest two versions of Chrome and Edge. Firefox and Safari work but are not part of the regression suite. The portal is responsive on mobile, but the in-Azure-DevOps settings hub from the Marketplace extension is desktop-only.
Billing and payments
- Paid plans are charged through Stripe. You need internet access to
api.stripe.comfrom your browser when entering or updating a payment method. - Stripe accepts Visa, Mastercard, American Express, and Discover. The set of supported countries is whatever Stripe supports for the merchant of record. See the Stripe documentation for the current list.
- The free trial is offered without a payment method. You only enter card details when you select a paid plan.
Azure DevOps organization access
To complete onboarding you need:
- A user account in the target Azure DevOps Services organization that can create a personal access token (PAT) with the scopes listed in Creating a personal access token.
- Permission to add service hook subscriptions to the projects you want reviewed. The wizard creates one
git.pullrequest.createdand onegit.pullrequest.updatedsubscription per selected project. - Optionally, organization-admin permission to install the Marketplace extension. The extension is not required — see Installing the extension.