Customizing Windows 365 Cloud PC Image Source

Answer Correct answer: B — Change the disk format to VHD to ensure compatibility with Windows 365 Cloud PC custom image uploads.

You have a Microsoft 365 subscription that has Windows 365 Enterprise licenses. You plan to use a custom Windows 11 image as a template for Cloud PCs. You have a Hyper-V virtual machine that runs Windows 11 and has the following configurations: • Name: VM1 • Disk size: 64 GB • Disk format: VHDX • Disk type: Fixed size • Generation: Generation 2 You need to ensure that you can use VM1 as a source for the custom image. What should you do on VM1 first?

Change the disk type to Dynamically expanding.
Change the disk format to the VHD. Correct Answer
Change the generation to Generation 1.
Increase the disk size.

windows 365 custom image vhd vs vhdx format md-102 cloud pc hyper-v vm template

Community Votes

100%

100% of anonymous learners picked answer B. Votes are pick records left by other test-takers — they are not the verified answer.

Community Insight

The exam tests knowledge of specific supported formats for Windows 365 custom images. The common trap is assuming modern formats like VHDX or Generation 2 features are universally required, whereas Windows 365 has specific legacy constraints.

This question addresses the requirements for creating a custom Windows 11 image for Windows 365 Cloud PCs. It establishes that the virtual hard disk format must be VHD rather than VHDX to ensure compatibility with the upload process.

Candidates often select option A (Dynamically expanding) because it is a general best practice for efficiency, but this does not address the primary format incompatibility issue which prevents the upload entirely.

Community Discussion (8 comments)

CaTa_LySt 👍 6

To use VM1 as a source for the custom Windows 11 image on Windows 365, you should choose option B. Change the disk format to VHD. Microsoft 365 Windows 365 Cloud PCs typically use VHD (Virtual Hard Disk) format for virtual machine images. Therefore, converting the disk format from VHDX to VHD is necessary for compatibility.

Meek_Learner 👍 1

The correct answer is: a. Change the disk type to Dynamically expanding. Windows 365 requires custom images to use dynamically expanding disks. This is because dynamically expanding disks are more efficient in terms of storage usage and are supported for creating custom images in Windows 365 Enterprise. The current configuration of VM1 uses a fixed-size disk, which is not compatible with Windows 365 requirements for custom images.

Daniel_G 👍 1 Selected: B

B is correct. VHDX is not possible for custom imaging. Disk size is sufficient and does not need to by dynamically expanding. Generation is sufficient too.

CJL324 👍 3

B. Change the disk format to VHD. The VHDX format is not supported for creating custom images in Windows 365; it must be converted to VHD format. This will ensure that the custom image can be uploaded and used within the Windows 365 environment.

PrepaCertif 👍 1

B&C https://learn.microsoft.com/en-us/azure/lab-services/upload-custom-image-shared-image-gallery

Darkfire 👍 3 Selected: B

I think B based on: https://learn.microsoft.com/en-us/azure/virtual-machines/generation-2#:~:text=Is%20VHDX%20supported%20on%20generation%202%3F%0ANo%2C%20generation%202%20VMs%20support%20only%20VHD.

Krayzr 👍 1 Selected: B

B I think not sure

kiro_e 👍 2

As of last update in January 2022, Windows 365 Cloud PCs support virtual hard disk (VHD) format for custom images. VHDX format is not explicitly mentioned as supported for Windows 365 Cloud PC custom images. Therefore, to ensure compatibility, it's recommended to convert your custom Windows 11 image from VHDX format to VHD format before using it as a template for Cloud PCs in Windows 365. So the answer could be B

Comments & Corrections

No comments yet — spotted an error or have a note? Share it below.

Expert Analysis

Why the Answer Is Correct

To use a Hyper-V VM as a source for a Windows 365 custom image, the virtual hard disk must be in the .VHD format. Although the VM uses Generation 2 and VHDX, Microsoft's documentation for Windows 365 specifically requires converting the disk to VHD before uploading. This ensures compatibility with the backend infrastructure used to provision Cloud PCs.

Why the Other Options Are Wrong

Option A is incorrect because while dynamically expanding disks are efficient, they do not solve the fundamental format incompatibility. Option C is wrong because Generation 2 is supported and preferred for modern OSes, provided the disk format is correct. Option D is unnecessary as 64GB is generally sufficient for a base Windows 11 image, and increasing size does not fix the format error.

Community Comment Notes

Community consensus strongly supports B. Users noted that "VHDX is not supported" and referenced official Microsoft learn pages confirming VHD is the required format. One user mentioned generation 2 support issues, but clarified that the disk format is the critical blocker.

Official Reference

https://learn.microsoft.com/en-us/windows-365/dev/prepare-custom-image

Exam Strategy

Memorize the specific technical constraints for Windows 365 custom images. When dealing with 'upload' or 'source' questions for this service, always check if the disk format needs to be converted to VHD, regardless of whether the VM is Gen 1 or Gen 2.

Frequently Asked Questions

Why is VHDX not supported for Windows 365?

Windows 365 provisioning infrastructure currently requires the legacy VHD format for custom images to ensure broad compatibility during the upload and conversion process.

Can I use a Generation 2 VM for Windows 365?

Yes, you can use a Generation 2 VM, but you must still convert its disk from VHDX to VHD format before uploading it as a custom image.

Related Analysis

Practice All MD-102 Questions

Access 92 questions with complete answers and detailed explanations.

View Full MD-102 Practice Test →

← Back to MD-102 Study Guide