# Treat community gallery withdrawal as a consumer capacity change

> What must an image publisher review before making a public Azure community gallery private?

- Canonical URL: https://update.dsesecurity.com/updates/dse-20260909-085-treat-community-gallery-withdrawal-as-a-consumer-capacity-change/
- Publisher: Detection Systems & Engineering (DSE Security)
- Author: DSE Security Editorial Team
- Published: 2026-09-10T00:30:31+00:00
- Modified: 2026-09-10T00:35:08+00:00
- Last reviewed by DSE: 2026-09-09
- Resource type: Guide
- DSE priority: Information
- Topics: Business Continuity, IT
- Reading time: 2 minutes

## What you need to know

What must an image publisher review before making a public Azure community gallery private?

## Potentially affected

Azure community gallery publishers planning to withdraw publicly shared VM images.

## DSE recommendation

Identify dependent scale-set consumers and agree a replacement image path before stopping public sharing.

## Article

## Source facts

Marking a gallery for community sharing makes its images available to Azure customers through public proxy resources while the publisher’s original gallery resources remain private. Microsoft warns that withdrawing public sharing prevents existing scale-set users from scaling their resources. Publisher contact and image-definition information are publicly visible. Community image support belongs to the publisher, while Microsoft can help isolate platform issues. [Microsoft Learn](https://learn.microsoft.com/en-us/azure/virtual-machines/share-gallery-community).

## Applicability

Use this review for the publisher’s withdrawal decision, not for granting one recipient access to a private gallery. Identify the public-facing gallery and the corresponding private resource handle. Review the published support contact and known consumer relationships before scheduling a change.

## DSE recommendation

Identify dependent scale-set consumers and agree a replacement image path before stopping public sharing. Ask each known workload owner to validate its future capacity requirement, not only the health of already-running instances. Prepare a clear withdrawal notice and escalation route without placing secrets or private customer details in public metadata. Record consumers whose readiness remains unknown.

## Verification

In an approved test arrangement, verify that the proposed replacement image can support the consumer’s intended deployment workflow. Preserve the old and new image references and the consumer’s observed result. Have the publisher confirm the exact gallery targeted by the withdrawal operation. Close the change only against the agreed consumer evidence, and do not describe a private publisher resource as proof that its former public distribution had no downstream dependencies.

## Official references

[Microsoft Learn: Share images using a community gallery](https://learn.microsoft.com/en-us/azure/virtual-machines/share-gallery-community). Source reviewed September 9, 2026.

## Primary reference

- Name: Share Azure Compute Gallery Resources with a Community Gallery - Azure Virtual Machines | Microsoft Learn
- Authority: Microsoft Learn
- URL: https://learn.microsoft.com/en-us/azure/virtual-machines/share-gallery-community
- Source publication date: Not stated by the source

## Citation and use

Preferred citation: “Treat community gallery withdrawal as a consumer capacity change,” DSE Security, https://update.dsesecurity.com/updates/dse-20260909-085-treat-community-gallery-withdrawal-as-a-consumer-capacity-change/
Publishing principles: https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/
Usage and citation policy: https://update.dsesecurity.com/usage/
Copyright © 2026 Detection Systems & Engineering. All rights reserved.