Support, rollout, and buyer fit
Use this page when the evaluation is no longer just about features and the buyer needs a clearer plan for support expectations, rollout fit, and next steps.
Marketplace evaluation
Start evaluation where Azure DevOps buyers expect to install and manage extensions.
Open Marketplace →Support requests
Use GitHub issues for product questions, bug reports, and support conversations tied to implementation.
Open support channel →Trust documents
Pair pricing with security, privacy, and install guidance when multiple stakeholders are involved.
Review security →Common rollout questions
When should a team stay on Starter?
Stay on Starter when the evaluation is still centered on basic sprint visibility and quick install proof.
When does Pro become the right next step?
Pro usually becomes the right fit when the buyer needs cycle time, flow analytics, and forecasting rather than only sprint basics.
Who is Business for?
Business is usually the conversation when a team wants WIP monitoring, broader operational visibility, and higher-touch internal reporting use cases.
What should an Enterprise buyer do first?
Use pricing, security, and this support page together so procurement, technical, and operational stakeholders can align before rollout.
How does Enterprise seat assignment work?
An org admin purchases the required number of seats through Visual Studio Marketplace and assigns them to users. Individual users do not need to register or purchase — they receive access through the org admin's assignment.