This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(313.6, 2%, 40%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMR%3C/text%3E%3C/svg%3E)
When trying to deploy a new SCCM Cloud Management Gateway via the SCCM console you only get limited VM Size options, none of which seem to be available in any Azure region.
How do you deploy an SCCM Cloud Management Gateway if there are no Azure regions available for the VM Size SCCM forces you to use?
A family of System Center products for managing incidents and problems.
I think that CMG shows those unavailable vm sizes when the console ends up using an outdated sku cache… it happens when the metadata doesn’t refresh cleany. if u can, re‑auth the Azure app and pls try switch the CMG mode once and that usually forces a fresh sku pull and the correct sizes show up again.
No luck with that unfortunately. Same result.
Thank u for letting me know. i think if the VM list is still wrong, check the ARM side. Make sure the sub has Microsoft.ClassicCompute and Microsoft.Web RPs registed, then look in CloudMgr.log for the ARM SKU‑query call. If the SCP isn’t pulling ARM metadata (needs to be Onlne), the console will keep showing bad sizes. Sorry if this doesn’t solve it.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(99.2, 21%, 19%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EWB%3C/text%3E%3C/svg%3E)
We had this same issue that we've been troubleshooting the last couple days. If you go to quotas in Azure you'll likely see 0/10 on your quota usage but it will still show unavailable.
We tried requesting 10 Standard Av2 Family vCPUs and it actually worked. The deployment wizard still said it was unavailable but the deployment succeeded regardless.