Retirement date
Microsoft lists legacy Computer Vision API versions for retirement on 13 September 2026.
Buyer-intent answers
Azure · Computer Vision · API retirement
Azure Computer Vision API Retirement: Prepare Before 13 September 2026
A Microsoft-backed migration checklist for teams still using Azure Computer Vision API versions 1.0, 2.0, 2.1, 3.0 or 3.1 before the 13 September 2026 retirement date.
Primary query: Azure Computer Vision API v1 v2 v3.1 retirement September 13 2026 migration · Updated 2026-09-07
Direct answer
What should an Azure Computer Vision customer do before legacy API versions retire on 13 September 2026?
Microsoft lists Azure Computer Vision API versions 1.0, 2.0, 2.1, 3.0 and 3.1 for retirement on 13 September 2026. Teams should identify every endpoint and SDK call that still depends on those versions, map each used feature to a supported replacement, and replay representative non-sensitive image cases against the replacement before cutover. The acceptance check should compare fields, errors, thresholds and product behaviour rather than assuming a version bump is semantically identical.
Practical sequence
What to do next
- 01
Inventory production and scheduled jobs that call Azure Computer Vision and record the endpoint, API version, SDK package and feature used.
- 02
Flag calls that reference versions 1.0, 2.0, 2.1, 3.0 or 3.1 and assign an owner for each affected integration.
- 03
Map each affected feature to the current Microsoft-supported replacement path and document any response-schema or capability differences.
- 04
Replay a representative synthetic or non-sensitive image corpus through the replacement and compare expected fields, error handling and business decisions.
- 05
Complete cutover and rollback acceptance before 13 September 2026, keeping the test evidence and current Microsoft retirement guidance with the change record.
Decision facts
Affected versions
The listed versions include 1.0, 2.0, 2.1, 3.0 and 3.1.
Migration risk
Replacement APIs can differ in endpoint, feature and response behaviour, so regression testing is an implementation control rather than a simple date check.
Boundaries
- — The correct replacement depends on the exact vision feature and application behaviour; this checklist does not guarantee output equivalence or model accuracy.
- — Avoid uploading confidential or personal images to third-party tooling solely for migration testing; use approved test data and current Microsoft guidance.
Free proof before paid workflow