SecurityProfile for Windows Images #4151
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Windows and Linux images both use the tag "TrustedLaunchAndConfidentialVmSupported" but their use of the tag is different. Windows images are generally GP with CVM support. They are intended to be used on GP hardware or CVM hardware. It is a single combined image for both scenarios. Linux images are generally intended only for CVM. There are separate images for GP scenarios. Testing Linux CVM images on GP hardware is generally not testing an intended use case. This change treats Windows and Linux VMs separately to recognize this difference in labeling conventions.
Contributor
There was a problem hiding this comment.
Pull request overview
This PR introduces OS-specific handling for the TrustedLaunchAndConfidentialVmSupported security profile tag in Azure images. Windows and Linux images use this tag differently: Windows images are general-purpose with CVM support for both GP and CVM hardware, while Linux images are typically CVM-only with separate images for GP scenarios. The changes ensure that Windows images with this tag support both Standard/SecureBoot and CVM/Stateless security profiles, while Linux images continue to support only CVM/Stateless profiles.
- Windows images with
TrustedLaunchAndConfidentialVmSupportednow support Standard, SecureBoot, CVM, and Stateless security profiles - Linux images with
TrustedLaunchAndConfidentialVmSupportedcontinue to support only CVM and Stateless security profiles - The
_get_image_tagsfunction now extractsos_typefrom both Marketplace and Shared Image Gallery images
Collaborator
|
I tested this PR and the WSL VM deployed successfully. My scenarios are fully unblocked. |
LiliDeng
approved these changes
Dec 12, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Windows and Linux images both use the tag "TrustedLaunchAndConfidentialVmSupported" but their use of the tag is different.
Windows images are generally GP with CVM support. They are intended to be used on GP hardware or CVM hardware. It is a single combined image for both scenarios.
Linux images are generally intended only for CVM. There are separate images for GP scenarios. Testing Linux CVM images on GP hardware is generally not testing an intended use case.
This change treats Windows and Linux VMs separately to recognize this difference in labeling conventions.