Microsoft Azure SharedImageGalleryServiceClient
Browse all Azure APIs★ Only Publicly Available OpenAPI DocumentCloud InfrastructureComputeoauth226 EndpointsREST
For Agents
Create Azure Compute Galleries, define custom VM images and gallery applications, and publish versioned artefacts replicated across regions.
Use for: Create a Shared Image Gallery in West Europe, Define a custom Windows image under a gallery, Publish a new image version replicated to three regions, Define a gallery application wrapping a setup.exe install script
Not supported: Does not provision VMs, build managed images, or manage marketplace images — use for Shared Image Gallery image and application registration and publishing only.
Jentic publishes the only available OpenAPI specification for SharedImageGalleryServiceClient, keeping it validated and agent-ready. The Azure Shared Image Gallery API (now Azure Compute Gallery) lets agents create galleries, register custom VM image and gallery application definitions, and publish versioned image and application artefacts that can be replicated across Azure regions and shared with other subscriptions or tenants. It models galleries, images, image versions, applications, and application versions under the Microsoft.Compute resource provider.
Install Jentic One Beta
Connect the SharedImageGalleryServiceClient to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the SharedImageGalleryServiceClient, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with SharedImageGalleryServiceClient API.
Create a Shared Image Gallery in a chosen Azure region
Define a custom VM image with OS type, hyperVGeneration, and identifier
Publish a new image version replicated across target regions
Define a gallery application that wraps an installer or script
Publish a new gallery application version with target regions and storage account type
List all galleries in a subscription or resource group
Inspect every image and version registered under a gallery
Use Cases
Patterns agents use SharedImageGalleryServiceClient API for, with concrete tasks.
★ Custom VM Image Distribution
Platform teams build hardened OS images and distribute them to engineering teams across regions through a central gallery. The galleries, images, and image versions endpoints accept the OS type, hyperVGeneration, source managed image ID, and target regions, so an agent can promote a baked image into the gallery and have it replicated automatically.
PUT a galleries/{galleryName}/images/{galleryImageName} resource with osType Windows, then PUT a versions/{galleryImageVersionName} with publishingProfile.targetRegions for westeurope and northeurope
Gallery Application Catalogue
DevOps teams maintain a catalogue of installer scripts that can be applied on top of any VM at deploy time. The applications and application versions endpoints store the install command, remove command, and the storage location of the package, so an agent can register a new tool or update its version without rebaking VM images.
PUT an applications/{galleryApplicationName} resource with supportedOSType Linux, then PUT a versions/{galleryApplicationVersionName} with publishingProfile.source.fileName and target regions
Image Inventory and Cleanup
FinOps and platform teams audit gallery contents periodically to find unused image versions and reclaim storage. The list endpoints at gallery, image, and version scope return every artefact with replication state and provisioning state, so an agent can build a report of stale versions older than a chosen date and delete them in bulk.
List galleries, then for each gallery list images and versions, returning galleryName, imageName, versionName, and replicationStatus.aggregatedState
AI Agent Image Promotion
An agent built on Jentic accepts a request to promote a tested managed image into the gallery for production use. It reads the source managed image, creates the image definition if missing, publishes the new version, sets target regions, and reports back the replication state — without the user opening the Azure portal.
Search Jentic for publish image version to azure shared image gallery, load the schema, and PUT a galleryImageVersion with the source managed image ID and the chosen target regions
Key Endpoints
26 endpoints — jentic publishes the only available openapi specification for sharedimagegalleryserviceclient, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
PUT
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Compute/galleries/{galleryName}
Create or update a Shared Image Gallery
PUT
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Compute/galleries/{galleryName}/images/{galleryImageName}
Define a custom VM image under a gallery
PUT
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Compute/galleries/{galleryName}/images/{galleryImageName}/versions/{galleryImageVersionName}
Publish a new image version with target regions
PUT
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Compute/galleries/{galleryName}/applications/{galleryApplicationName}
Define a gallery application
PUT
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Compute/galleries/{galleryName}/applications/{galleryApplicationName}/versions/{galleryApplicationVersionName}
Publish a new gallery application version
GET
/subscriptions/{subscriptionId}/providers/Microsoft.Compute/galleries
List all galleries in a subscription
PUT
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Compute/galleries/{galleryName}
Create or update a Shared Image Gallery
PUT
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Compute/galleries/{galleryName}/images/{galleryImageName}
Define a custom VM image under a gallery
PUT
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Compute/galleries/{galleryName}/images/{galleryImageName}/versions/{galleryImageVersionName}
Publish a new image version with target regions
PUT
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Compute/galleries/{galleryName}/applications/{galleryApplicationName}
Define a gallery application
PUT
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Compute/galleries/{galleryName}/applications/{galleryApplicationName}/versions/{galleryApplicationVersionName}
Publish a new gallery application version
GET
/subscriptions/{subscriptionId}/providers/Microsoft.Compute/galleries
List all galleries in a subscription
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Azure AD service principal credentials sit encrypted in the Jentic vault. Agents receive a short-lived bearer token scoped to user_impersonation — raw secrets never enter the agent context, which matters when image references include managed-identity-bound storage URLs.
Intent-based discovery
Agents search Jentic by intent such as publish azure image version or create shared image gallery and Jentic returns the matching Microsoft.Compute galleries operation with its full input schema.
Time to first call
Direct integration with the galleries ARM endpoints: 1-2 days for AAD setup, async replication polling, and ARM error retries. Through Jentic: under 1 hour — search, load schema, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using SharedImageGalleryServiceClient API through Jentic.
Why is there no official OpenAPI spec for SharedImageGalleryServiceClient?
Microsoft Azure does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call SharedImageGalleryServiceClient via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.
What authentication does the Shared Image Gallery API use?
It uses Azure AD OAuth 2.0 with the implicit flow against https://login.microsoftonline.com/common/oauth2/authorize and the user_impersonation scope. When called through Jentic, your service principal credentials live in the Jentic vault and the agent receives only a short-lived bearer token scoped to the subscription it is acting on.
Can I publish a custom VM image with this API?
Yes. PUT a galleries/{galleryName}/images/{galleryImageName} resource to define the image (OS type, identifier, hyperVGeneration), then PUT a versions/{galleryImageVersionName} with the source managed image ID and a publishingProfile.targetRegions list to replicate it across regions.
How do gallery applications differ from gallery images?
An image version captures a full VM disk; a gallery application packages an installer or script that gets applied on top of any base VM at deploy time. Use applications/{galleryApplicationName}/versions for tools and agents that should be layered onto multiple base images.
What are the rate limits for this API?
Azure Resource Manager throttles around 12,000 reads and 1,200 writes per hour per principal at subscription scope, surfaced via x-ms-ratelimit-remaining-subscription-reads and x-ms-ratelimit-remaining-subscription-writes. Image version publishes are async — the 202 response includes an asyncOperation URL to poll for replication progress.
How do I publish an image version through Jentic?
Search Jentic for publish image version to azure shared image gallery, load the schema for PUT /.../galleries/{galleryName}/images/{galleryImageName}/versions/{galleryImageVersionName}, and execute it with the source managed image ID and target regions. The Jentic Python SDK ships the search, load, execute pattern after pip install jentic.
Can I share a gallery across subscriptions?
Yes — galleries support direct sharing through Azure RBAC role assignments on the gallery resource. Newer API versions add Direct Shared Gallery and Community Gallery flavours; this 2019-07-01 API exposes the core gallery surface with subscription and tenant-level visibility through ARM permissions.
GET STARTED