Computer vision · API / SDK

Azure Vision

Microsoft

Access Microsoft's documented image-analysis and text-reading services.

Official documentation Download development spec

Lifecycle gate: Image Analysis is scheduled to retire on 2028-09-25. This page documents existing integrations and migration assessment, not an unconditional new-build recommendation.

MICROSOFT AZURE VISION / DEVELOPER FIELD GUIDE

Choose an interface. Define a verifiable result.

Company or project context, ten technical entry points and a practical analysis of every reference.

2026-10-08 · Integration not tested

Company / project overview

Original summary of official company or project statements; use the source for the full original page.

Microsoft Azure Vision · About
Mission	Microsoft frames its mission around enabling people and organizations through technology.
Commitments	Its About page covers opportunity, trust, rights and sustainability.
Ecosystem	Cloud, developer tools, products, careers and corporate information are linked from the company page.

Complete official About page ↗

About reference — TA analysis
Audience	Buyers, partners and product owners shortlisting an AI provider.
Our assessment	Use positioning and company history for initial fit. Obtain project-specific deployment, support and commercial terms separately.

Official project and developer sources reviewed; no provider API was called. Expected outputs below are our illustrative contracts, not measured results.

Top 10 technical entry points

Ten documented technical entry points, selected by task; not ten independent SDKs or an official ranking.

Choose by the work you need to complete
Interface	Purpose and audience
01 · Migration optionsAPI / SDK / developer guide	Plan replacement of the retiring Image Analysis service.Architect / product owner
02 · Image Analysis 4.0 SDK / REST quickstartAPI / SDK / developer guide	Initialize a client and request selected image features.Application developer
03 · Image Analysis 3.2 call guideAPI / SDK / developer guide	Review existing 3.2 request and response handling.Legacy integration owner
04 · Content tagsAPI / SDK / developer guide	Generate semantic tags for images.Catalogue / search team
05 · Object detectionAPI / SDK / developer guide	Locate recognized object instances.Vision UI developer
06 · Image and dense captionsAPI / SDK / developer guide	Describe an image or its regions.Content / accessibility team
07 · Image OCRAPI / SDK / developer guide	Extract text from photographed content.Document intake developer
08 · Smart-cropped thumbnailsAPI / SDK / developer guide	Find a crop region for an aspect ratio.Catalogue UI engineer
09 · Language supportAPI / SDK / developer guide	Check feature-specific language support.Localization / QA team
10 · Document Intelligence Read alternativeAPI / SDK / developer guide	Evaluate Read as an OCR replacement path.OCR migration team

Reference analysis

Capabilities summarize official documentation. Constraints and proposed tests are our engineering assessment.

API / SDK / developer guide

Migration options

Migration options · TA
Target audience	Architect / product owner
Documented capability	Plan replacement of the retiring Image Analysis service.
Input → output	Existing feature dependencies → migration plan
Execution environment	Azure cloud; feature, API version and region dependent
Our decision constraint	Retirement is September 25, 2028; do not present this as a fresh long-term default.
Our suggested validation	Map each used feature to a tested replacement.

Official reference · Migration options ↗

API / SDK / developer guide

Image Analysis 4.0 SDK / REST quickstart

Image Analysis 4.0 SDK / REST quickstart · TA
Target audience	Application developer
Documented capability	Initialize a client and request selected image features.
Input → output	Image + features → analysis result
Execution environment	Azure cloud; feature, API version and region dependent
Our decision constraint	An SDK example does not resolve service lifecycle or regional support.
Our suggested validation	Record endpoint, version and feature list in the contract.

Official reference · Image Analysis 4.0 SDK / REST quickstart ↗

API / SDK / developer guide

Image Analysis 3.2 call guide

Image Analysis 3.2 call guide · TA
Target audience	Legacy integration owner
Documented capability	Review existing 3.2 request and response handling.
Input → output	Legacy image request → selected visual features
Execution environment	Azure cloud; feature, API version and region dependent
Our decision constraint	Do not mix 3.2 and 4.0 schemas.
Our suggested validation	Keep a versioned fixture for the currently deployed adapter.

Official reference · Image Analysis 3.2 call guide ↗

API / SDK / developer guide

Content tags

Content tags · TA
Target audience	Catalogue / search team
Documented capability	Generate semantic tags for images.
Input → output	Image → tags with confidence
Execution environment	Azure cloud; feature, API version and region dependent
Our decision constraint	Generic tags do not establish exact part identity.
Our suggested validation	Compare relevant tags with a human catalogue taxonomy.

Official reference · Content tags ↗

API / SDK / developer guide

Object detection

Object detection · TA
Target audience	Vision UI developer
Documented capability	Locate recognized object instances.
Input → output	Image → object boxes and scores
Execution environment	Azure cloud; feature, API version and region dependent
Our decision constraint	Object classes are not custom defect classes.
Our suggested validation	Verify box alignment after resizing the image.

Official reference · Object detection ↗

API / SDK / developer guide

Image and dense captions

Image and dense captions · TA
Target audience	Content / accessibility team
Documented capability	Describe an image or its regions.
Input → output	Image → descriptive text
Execution environment	Azure cloud; feature, API version and region dependent
Our decision constraint	Generated descriptions require review and regional availability checks.
Our suggested validation	Reject invented material, model or certification claims.

Official reference · Image and dense captions ↗

API / SDK / developer guide

Image OCR

Image OCR · TA
Target audience	Document intake developer
Documented capability	Extract text from photographed content.
Input → output	Image → text and positions
Execution environment	Azure cloud; feature, API version and region dependent
Our decision constraint	Recognition alone does not parse tolerances or units.
Our suggested validation	Compare part numbers character-by-character.

Official reference · Image OCR ↗

API / SDK / developer guide

Smart-cropped thumbnails

Smart-cropped thumbnails · TA
Target audience	Catalogue UI engineer
Documented capability	Find a crop region for an aspect ratio.
Input → output	Image + ratio → crop coordinates
Execution environment	Azure cloud; feature, API version and region dependent
Our decision constraint	Cropping can hide engineering evidence.
Our suggested validation	Retain the original and verify dimensions remain visible.

Official reference · Smart-cropped thumbnails ↗

API / SDK / developer guide

Language support

Language support · TA
Target audience	Localization / QA team
Documented capability	Check feature-specific language support.
Input → output	Feature + language → supported-path decision
Execution environment	Azure cloud; feature, API version and region dependent
Our decision constraint	One feature’s language list does not cover every other feature.
Our suggested validation	Test the actual document language and mixed scripts.

Official reference · Language support ↗

API / SDK / developer guide

Document Intelligence Read alternative

Document Intelligence Read alternative · TA
Target audience	OCR migration team
Documented capability	Evaluate Read as an OCR replacement path.
Input → output	Document → extracted text structure
Execution environment	Azure cloud; feature, API version and region dependent
Our decision constraint	Separate service and schema; not a drop-in replacement.
Our suggested validation	Map text order, coordinates and errors before migration.

Official reference · Document Intelligence Read alternative ↗

Official documentation overview

Official documentation overview · Supporting reference analysis
TA	Developers and product owners selecting the supported technical path.
Our validation advice	Choose the operation, supported version and runtime before assigning implementation.

Official reference · Official documentation overview ↗

04 / INPUT · EXPECTED OUTPUT · ACCEPTANCE

Expected results before implementation

Existing-image analysis and migration specification; no cloud request is executed.

Illustrative contract · no API call or model execution · not measured provider output

Valid image

Expected behavior — illustrative, not executed
Input	Authorized image and selected tags feature
Expected result	ok with tag names and normalized scores
Acceptance	Validate structure; human-check tag usefulness

No qualifying tags

Expected behavior — illustrative, not executed
Input	Valid image without relevant labels
Expected result	ok with data=[]
Acceptance	Do not report transport failure as empty success

Unavailable or retired service

Expected behavior — illustrative, not executed
Input	Unsupported endpoint/version
Expected result	error; data=null; migration_required where known
Acceptance	Display actionable lifecycle state

Malformed image

Expected behavior — illustrative, not executed
Input	Unreadable input
Expected result	error; invalid_input
Acceptance	No invented tags or automatic success

Map the expected result to your application

Review the scenarios below and map the actual SDK response into this internal contract. No credential, API call or live output is included. Replace example data only after your own integration test.

Expected output JSON — illustrative, not measured · AzureVision-expected-results.json

{
  "schema_version": "1.0.0",
  "example": true,
  "provider": "Microsoft Azure Vision",
  "status": "ok",
  "input_id": "sample-001",
  "data": [
    {
      "label": "metal object",
      "score": 0.8
    }
  ],
  "error": null,
  "verification": "illustrative-only;not-provider-response"
}

Download specification, example and acceptance plan

Engineering handoff — our proposed contract and gates
Result states	ok means the selected operation returned a valid result; a valid empty result differs from error. Pending work remains pending until a terminal result. Do not infer real-world correctness from API success.
Reproducibility	Record input ID, library/model version, configuration, runtime and coordinate/score conventions. Examples contain invented sample values.
Acceptance — proposed	Use representative authorized samples plus empty, malformed and unavailable-runtime cases. Agree quality and latency targets before running tests. No measured accuracy, cost or speed is claimed.
Operation boundary	Existing-image analysis and migration specification; no cloud request is executed.

Related route to assess: Google Cloud Vision

Development assessment

Legacy vision migration review

Development concept · integration not tested

Provider capabilities above are based on official documentation or repositories. The proposed product, inputs, deliverable and acceptance criteria below are our development assessment.

Resolve access first

A lifecycle, license, model-compatibility or access decision must be resolved before assigning implementation.

Proposed inputs: A small authorized image dataset, task definition and reference annotations.
Proposed deliverable: A reviewable result with image references, labels or annotation state; keep original files.
Acceptance criterion: Compare the supported operation against a labeled sample; report errors and missing results separately.
Dependencies: Dataset access, image rights and a supported model or annotation project.

Integration condition

Lifecycle gate: Image Analysis is scheduled to retire on 2028-09-25. This page documents existing integrations and migration assessment, not an unconditional new-build recommendation.

Development sequence

Confirm access to Azure Vision, license and the exact supported version.
Prepare the sample above and implement one documented operation for “Legacy vision migration review”.
Normalize the result with source, time and explicit error state; keep the provider response for review.
Run the acceptance criterion before estimating rollout effort or committing a customer deliverable.

How to validate demand

Record product views, documentation clicks, specification downloads and contextual hub clicks. These are event counts, not unique people or completed integrations.

This feasibility assessment uses implementation conditions. No traffic-based rank or delivery-time promise is assigned.

Azure Vision

Choose an interface. Define a verifiable result.

Company / project overview

Top 10 technical entry points

Reference analysis

Official documentation overview

Expected results before implementation

Valid image

No qualifying tags

Unavailable or retired service

Malformed image

Map the expected result to your application

Legacy vision migration review

Integration condition

Development sequence

How to validate demand

Related products