How do I get access to all GPU shapes in DevTest Labs?

kobulloc-MSFT 25,156 Reputation points Microsoft Employee
2019-10-29T20:17:43.587+00:00

Within Azure DevTest Labs, GPU shapes should be allowed for my region (US West 2) however all the N shapes are grayed out. Are we able to create a GPU shape?

Sourced from MSDN

Azure DevTest Labs
Azure DevTest Labs
An Azure service that is used for provisioning development and test environments.
261 questions
0 comments No comments
{count} votes

Accepted answer
  1. bharathn-msft 5,086 Reputation points Microsoft Employee
    2019-10-29T21:17:16.057+00:00

    Welcome to the Microsoft Q&A (Preview) platform.

    Happy to answer your questions

    Repro:

    If you go to your DevTest Labs resource, click "Add" to add a VM, choose a base, and then click on "Change Size" under "Disk and Size" for your VM size settings, you'll be presented with a list of VM options. By scrolling down to the bottom you'll see the N-series VMs which are grayed out with the following message:
    "Size not available. This size is currently unavailable in this location for this subscription: NotAvailableForSubscription."

    Screenshot

    Solution:

    It turns out that for this size family, the default vCPU (core) quota for your subscription is initially set to 0 for each region. You'll need to request a vCPU quota increase for this family (and make sure that it is in an available region).
    On the "Request a vCPU quota increase" page there is a vague instruction to make the request using the portal. What this really means is:

    • Go to "Subscriptions" ("All Services" > "Subscriptions", it will have a key for an icon)
    • Select the subscription you want the quota increase to be applied to
    • Click on "New support request" under "Support + troubleshooting"
    • Complete the wizard:
      Issue Type: Service and subscription limits (quotas)
      Subscription: Your subscription
      Quota Type: Compute-VM (cores-vCPUs) subscription limit increases

    Hope this information helps.

    Sourced from MSDN

    0 comments No comments

0 additional answers

Sort by: Most helpful