Skip to content

Knowledge catalog

Generated reference

Read-only pages rendered from the Quake AI knowledge graph.

Competitor MappingReference node

Azure Compute Gallery Image (Generalized or Specialized)

Competitor mapping for Microsoft Azure.

This page is a structured knowledge reference. For step-by-step migration guidance, see the migration guide.

Details

Provider
Microsoft Azure
Service term
Azure Compute Gallery Image (Generalized or Specialized)
Provider documentation
External reference

Behavioral divergences

Azure Compute Gallery Image (Generalized or Specialized)

Quake AI concept: Snapshots

  • Azure requires choosing between generalized (sysprep'd, removes machine identity, destroys the source VM's bootability) and specialized (exact clone, source VM survives). OpenStack Nova createImage is always non-destructive — the server continues running and the image captures the current disk state.
  • Capturing a generalized Azure image requires running waagent -deprovision inside the VM, then deallocating and marking as generalized (az vm generalize) before capture — a multi-step destructive process. OpenStack createImage (POST /v2.1/servers/{id}/action {"createImage": {...}}) requires no VM shutdown.
  • Azure stores instance images in Azure Compute Gallery with versioning and multi-region replication support. Glance stores images with no built-in versioning (images are replaced or new images created).
  • Azure ARM API for capture: POST /providers/Microsoft.Compute/virtualMachines/{vm}/capture (legacy) or via Compute Gallery image versions. Nova API: POST /v2.1/servers/{id}/action.

Related

Diverges from (incoming)

Citations

  1. Microsoft Azure
  2. Microsoft Azure

These citations record configured source URLs in the knowledge graph. They are not a live platform walk verification date.