One caveat applies throughout. Microsoft's Azure Updates page renders as empty in the captured view, showing "0 Updates found" with no announcement text. The feature details below come from a roadmap site, 365Fanatic Cloud, that reproduces the Azure update text. They are not from Microsoft documentation I could open. Treat the operational specifics as reported, not confirmed.
What the preview is meant to do
According to the reproduced announcement, the validation lets VM image publishers and enterprise platform teams run Azure's certification-grade quality and security checks on their images in their own subscriptions. That wording is paraphrased from the 365Fanatic listing, and I am citing it only loosely. The key change is timing. Those checks reportedly ran only when you submitted an Azure Marketplace offer in Partner Center. Now you could run them at any point in your build process.
The reported capabilities are:
- Self-service runs in your subscription, with your choice of tests and timing.
- Checks for bootability, OS configuration and platform compatibility.
- Malware and vulnerability scanning powered by Microsoft Defender.
- A native Azure resource with an API, so validation can act as a CI/CD release gate.
- Per-test results with stable error codes and stated reasons.
The listing says images can be bound for Azure Marketplace, galleries or other distribution platforms. It names no image formats, sources or test catalog.
It does not replace Marketplace certification
The announcement says Artifact Validation complements Marketplace certification and does not replace it. Final certification still runs through Partner Center. A clean validation run is therefore not a guarantee of Marketplace acceptance. It is an early warning system.
Availability and the date wrinkle
The listing reports these regions: Central US, North Central US, South Central US, Sweden Central, Japan East and Australia East. Access is through the REST API, ARM templates and Azure SDKs. There is no portal or CLI experience in that list. That does not mean none exists, only that none was reported.
There is also a timing oddity. The roadmap site gives a "Preview from" date of November 30, 2026, which is after today's date of November 17. The status label says "In preview" while the start date sits in the future. Don't assume you can start testing today. Check your subscription and region before planning around it.
Microsoft's generic Azure Updates definition of "In preview" applies. It means the feature is for non-production use and testing. That is general status language, not product-specific terms. Don't put production release gates on it yet.
How it differs from tools you may already use
Azure already has related checks. Keeping them separate avoids confusion.
- Trusted Launch validation in Azure Compute Gallery. Microsoft Learn describes this as a preview in which the platform adds the validation result to the image version property. That validation takes a minimum of one hour. It checks one specific capability. Nothing in the evidence says Artifact Validation uses the same mechanism or takes the same time.
- Azure VM Image Builder. This is a build tool. Microsoft's documentation says it can integrate with existing image build pipelines. Its in-VM validations are a separate feature. The announcement does not say how Artifact Validation connects to Image Builder, if at all.
- The older manual route. A community lab guide notes that images should be tested before publishing, or they may fail certification checks. The usual tool was the Certification Test Tool for Azure Certified. A native Azure resource with an API would be a more automatable alternative, if the reported design holds.
Why admins and image teams should care
This is my analysis, not a measured result. Image pipelines tend to find problems late. A boot failure, a misconfigured OS or a flagged vulnerability is cheapest to fix before an image is replicated, shared or submitted. A pipeline gate that returns stable error codes would let teams fail a build with a clear reason. It would also let them track recurring defects over time.
For enterprise teams that never publish to Marketplace, the reported scope still covers images bound for galleries and other distribution platforms. That could make it a useful check for internal golden images. It is worth confirming this in Microsoft's documentation.
What to verify before you build on it
The reproduced text leaves these questions open:
- The exact resource type and API version.
- Onboarding or registration requirements, if any.
- How tests are selected and what the full test list is.
- Supported image sources and formats.
- How long results are retained and what the error-code reference says.
- Limits of the Defender-powered scanning.
- Pricing, if any, and the formal preview terms.
Until those are answered in Microsoft's documentation, treat this as a promising but unverified addition to Azure image tooling. If your team publishes images, watch for the November 30 preview start and for official documentation before changing your pipelines.
References
- (In preview) Public Preview: Azure Artifact Validation for VM images Azure Updates · 2026-11-17T20:00:32Z
- Public Preview: Azure Artifact Validation for VM… | 365Fanatic Cloud cloud.365fanatic.com
- Azure VM Image Builder service DevOps task (preview) - Azure Virtual Machines learn.microsoft.com