Our host pool has GPU enabled machines, and trying to find a secondary sku that works with the image template and is close to the same specs as the original sku is very cumbersome. Firstly, Microsoft support is currently pushing back on quota requests, and secondly, if quota does get approved, its either very limited, or the specs for the other machine sku size are different. I have found a secondary sku that works with our image but does not have a GPU. When trying to provision an Azure Extended Capacity with that new sku, Nerdio removes that size for being “critically different". The size is very different and has multiple flags in Nerdio on it, in terms of no temporary storage, different CPU architecture, CPU size and RAM size. My goal for Azure Extended Capacity is for Nerdio to be able to recognize the errors that Azure is giving with machine capacity and provision a machine for our customers, so that the customer does not get an error trying to launch one of the remote apps.
I would like for Nerdio to continue to flag the different in sku, in regards to CPU, GPU, RAM and other difference, but having a button or warning to “acknowledge” the difference would be ideal. Letting the host pool provision the machine even if it is “critically different”. I have done my due diligence to test that this machine size is what I want in case of a capacity issue, and having the warning still there, but able to bypass it would be perfect. Essentially removing this error inside the provision process:
{
"Id": 8418179,
"CreationDateUtc": "2026-05-21T14:56:55.8423935Z",
"ResultDateUtc": "2026-05-21T14:56:55.8426611Z",
"Name": "Remove critically different sizes",
"Description": null,
"TaskStatus": 2,
"Result": "Removed sizes: Standard_E8s_v4\r\nValid sizes: Standard_NV6ads_A10_v5\r\n",
"ResultInJson": false,
"JobId": 686727,
"PiiDetectorResults": null
}
Comments (0 comments)