Why I can't create VM with any imge from makeplace

Question

Why I can't create VM with any imge from makeplace

zhangyong 5

I want create a VM , when I select the image from Image list, I found windows server 2016 is not in the list.

then a click the see all images ,and it take me to the market place.

I found the windows server 2016 and click select , then it goes back to the create VM UI,

but it's strange the Windows server 2016 that I selected just now does not become and value of image input box. the value in the input box is the old value.

I try it with some other images in the marketplace , they are all with the same problem.

and I change the region , change the security type ,

the problem is still there.

I feel it's the bug in Azure. is there anyone encounter the same problem.

VarunTha 15,005 Reputation points Microsoft External Staff Moderator

2026-06-29T19:05:01.7633333+00:00
Hi zhangyong,

Thank you for your question.

I understand that the selected Marketplace image is not being reflected in the VM creation page and the previous image value remains selected.

Based on the behaviour described, this appears to be related to the Azure portal image-selection experience/UI rendering, rather than an issue with the selected region, security type, or the Windows Server 2016 image itself. In Azure, Marketplace VM images are identified by image details such as Publisher, Offer, SKU, and Version, and these can also be validated outside the portal using Azure CLI or PowerShell.

To isolate whether this is only a portal-side issue, could you please try the below steps:

Sign out from the Azure portal and sign in again.

Try the same operation in an InPrivate/Incognito browser window.

Clear browser cache/cookies or try from a different browser.

Try creating the VM using Azure CLI with the required Windows Server 2016 image URN.

You can validate available images using Azure CLI, for example:

az vm image list --publisher MicrosoftWindowsServer --offer WindowsServer --all --output table

If Windows Server 2016 Datacenter is available for your selected region/subscription, you can try creating the VM by specifying the image directly through CLI. Azure CLI supports listing Marketplace images and using the image URN to create VMs programmatically.

Could you please try the above recommended steps and check if the selected Marketplace image is reflected correctly in the VM creation page?

If the issue still persists after trying these steps, please share a screenshot of the behaviour/error. We will review it further and investigate accordingly.
zhangyong 5 Reputation points

2026-06-30T05:58:25.9033333+00:00

I have identified the issue.

When I access the Azure Portal through a proxy located outside Shanghai, everything works normally. However, when I access it directly from Shanghai, the problem occurs consistently.

Based on my testing, the issue appears to be related to Azure service in Shanghai 。
VarunTha 15,005 Reputation points Microsoft External Staff Moderator

2026-06-30T18:41:40.2966667+00:00

Hello zhangyong,
Thank you for confirming the additional testing.

Since the VM creation works successfully through Cloud Shell/CLI and also works from the Azure portal when accessed through a proxy outside Shanghai, this indicates that the VM image and subscription are working as expected.

Based on your testing, the issue appears to be specific to the Azure portal/Marketplace image selection experience from the Shanghai network path. This could be related to network routing, proxy/firewall restrictions, or connectivity to Azure portal/Marketplace endpoints from that location. Microsoft documentation also recommends allowing the required Azure portal and Marketplace URLs on proxy/firewall configurations to avoid portal connectivity or loading issues.

As a workaround, please continue using Cloud Shell/CLI or access the Azure portal through the working network path where the Marketplace image selection works correctly.

You may also review the Azure portal URL allowlist requirements with your network team to ensure the required Azure portal and Marketplace endpoints are allowed from the affected network.

Thank you for your patience and for sharing the detailed validation results.

1 answer

Your answer

VarunTha 15,005 Reputation points Microsoft External Staff Moderator

2026-06-29T19:05:01.7633333+00:00

Hi zhangyong,

Thank you for your question.

I understand that the selected Marketplace image is not being reflected in the VM creation page and the previous image value remains selected.

Based on the behaviour described, this appears to be related to the Azure portal image-selection experience/UI rendering, rather than an issue with the selected region, security type, or the Windows Server 2016 image itself. In Azure, Marketplace VM images are identified by image details such as Publisher, Offer, SKU, and Version, and these can also be validated outside the portal using Azure CLI or PowerShell.

To isolate whether this is only a portal-side issue, could you please try the below steps:

Sign out from the Azure portal and sign in again.

Try the same operation in an InPrivate/Incognito browser window.

Clear browser cache/cookies or try from a different browser.

Try creating the VM using Azure CLI with the required Windows Server 2016 image URN.

You can validate available images using Azure CLI, for example:

az vm image list --publisher MicrosoftWindowsServer --offer WindowsServer --all --output table

If Windows Server 2016 Datacenter is available for your selected region/subscription, you can try creating the VM by specifying the image directly through CLI. Azure CLI supports listing Marketplace images and using the image URN to create VMs programmatically.

Could you please try the above recommended steps and check if the selected Marketplace image is reflected correctly in the VM creation page?

If the issue still persists after trying these steps, please share a screenshot of the behaviour/error. We will review it further and investigate accordingly.
zhangyong 5 Reputation points

2026-06-30T05:58:25.9033333+00:00

I have identified the issue.

When I access the Azure Portal through a proxy located outside Shanghai, everything works normally. However, when I access it directly from Shanghai, the problem occurs consistently.

Based on my testing, the issue appears to be related to Azure service in Shanghai 。
VarunTha 15,005 Reputation points Microsoft External Staff Moderator

2026-06-30T18:41:40.2966667+00:00

Hello zhangyong,
Thank you for confirming the additional testing.

Since the VM creation works successfully through Cloud Shell/CLI and also works from the Azure portal when accessed through a proxy outside Shanghai, this indicates that the VM image and subscription are working as expected.

Based on your testing, the issue appears to be specific to the Azure portal/Marketplace image selection experience from the Shanghai network path. This could be related to network routing, proxy/firewall restrictions, or connectivity to Azure portal/Marketplace endpoints from that location. Microsoft documentation also recommends allowing the required Azure portal and Marketplace URLs on proxy/firewall configurations to avoid portal connectivity or loading issues.

As a workaround, please continue using Cloud Shell/CLI or access the Azure portal through the working network path where the Marketplace image selection works correctly.

You may also review the Azure portal URL allowlist requirements with your network team to ensure the required Azure portal and Marketplace endpoints are allowed from the affected network.

Thank you for your patience and for sharing the detailed validation results.

Answer 1

Alex Burlachenko 23,170 MVP Volunteer Moderator

hi zhangyong & thx for sharing urs issue here at Q&A portal,

Could be a portal UI bug, but Windows Server 2016 is also old enough that it may not show in the normal quick image list anymore.

Try creating it with CLI instead of portal

az vm image list \

--publisher MicrosoftWindowsServer \

--offer WindowsServer \

--sku 2016-Datacenter \

--all \

--output table

Then create the VM using the exact URN returned

az vm create \

-g <rg> \

-n <vm-name> \

--image publisher:offer:sku:version \

--admin-username <user>

If CLI works, it’s just the portal image picker being flaky. If CLI also fails, the image/SKU may not be available for that region/security type/subscription. Try Gen1 / Standard security type too, bc older images may not support Trusted Launch.

rgds,

Alex

&

If my answer was helpful pls mark it and additional thx if u follow me at Q&A portal

and at my blog https://ctrlaltdel.blog/

zhangyong 5 Reputation points

2026-06-30T12:21:01.4366667+00:00

@Alex Burlachenko , Thank you for your answer.

I've confirmed the command(VM list and VM create) in cloud shell works normally.
and I have also created the VM from console GUI through a proxy connecting to a point in Japan outside Shanghai,
so that's the problem specially in Shanghai when using console to select the image.
Alex Burlachenko 23,170 Reputation points MVP Volunteer Moderator

2026-06-30T13:56:10.0933333+00:00

zhangyong, thanks for confirming. Since CLI and VM creation through a Japan proxy work, this points to the Azure Portal/Marketplace UI path from Shanghai, not the VM image or subscription. So the image picker is likely failing to load/apply Marketplace metadata correctly from that network/location. Could be regional CDN, proxy/firewall, browser network path, or China-side filtering between Shanghai and Azure Marketplace/Portal endpoints. I’d report it as a portal Marketplace image-selection issue with repro details Azure Portal image picker from Shanghai does not apply selected Marketplace image. Same account/subscription works via Cloud Shell CLI and via console GUI through Japan proxy. Use CLI/Cloud Shell or access the portal through a network path where Marketplace selection works. This doesn’t look like a VM platform issue anymore.

rgds,

Alex