{"id":1747,"date":"2019-09-18T15:56:36","date_gmt":"2019-09-18T15:56:36","guid":{"rendered":"https:\/\/www.teal-consulting.de\/2019\/09\/18\/troubleshooting-azure-resource-quotas\/"},"modified":"2019-12-17T11:16:16","modified_gmt":"2019-12-17T11:16:16","slug":"troubleshooting-azure-resource-quotas","status":"publish","type":"post","link":"https:\/\/www.teal-consulting.de\/en\/2019\/09\/18\/troubleshooting-azure-resource-quotas\/","title":{"rendered":"Troubleshooting Azure – Resource Quotas"},"content":{"rendered":"
[vc_row css_animation=”” row_type=”row” use_row_as_full_screen_section=”no” type=”full_width” angled_section=”no” text_align=”left” background_image_as_pattern=”without_pattern”][vc_column][vc_empty_space height=”50″][vc_row_inner row_type=”row” type=”full_width” text_align=”left” css_animation=””][vc_column_inner][vc_column_text]We are currently working on the next internal project, which we will report on in detail in due course. Until then we will blog at irregular intervals about technical stumbling blocks and their solution. Today we start with Azure Resource Quotas. Azure Resource Quotas are certainly not a new topic for many, but there is no clear error message.<\/p>\n

Problem<\/h3>\n

When we wanted to provision the servers in Azure for our internal project, it went smoothly at first. At some point we simply couldn’t select a VM size anymore and therefore couldn’t provision a server anymore. The portal reported “The value must not be empty”, but all VM types were grayed out:[\/vc_column_text][\/vc_column_inner][\/vc_row_inner][vc_empty_space height=”20″][vc_single_image image=”1199″ img_size=”full” alignment=”center” qode_css_animation=””][vc_empty_space height=”20″][vc_single_image image=”1200″ img_size=”full” alignment=”center” qode_css_animation=””][vc_empty_space height=”20″][vc_column_text]\n

Solution<\/b><\/h3>\n

There are numerous limits to the use of the various Azure services. These are documented here:\u00a0Azure Subscription Service Limits<\/a><\/p>\n

In our case, the vCPU limit for one of the regions and VM size was again exhausted. Probably almost everyone will encounter the problem sooner or later, because the default limits are quite small, as you can see below:[\/vc_column_text][vc_empty_space height=”20″][vc_single_image image=”1201″ img_size=”full” alignment=”center” qode_css_animation=””][vc_empty_space height=”20″][vc_column_text]Unfortunately you have to rely on the Azure support for the solution. To change the quotas proceed as follows:<\/p>\n

1 In Azure go to Help + Support:[\/vc_column_text][vc_empty_space height=”20″][vc_single_image image=”1202″ img_size=”full” alignment=”center” qode_css_animation=””][vc_empty_space height=”20″][vc_column_text]2. create a new support request with the option “New support request” and select the following:<\/p>\n

a.Issue Type: Service and subscription limits (quotas)<\/p>\n

b.Subscription: (Your subscription)<\/p>\n

c.Quota type: Compute VM (core-vCPUs) subscription limit[\/vc_column_text][vc_empty_space height=”20″][vc_single_image image=”1203″ img_size=”full” alignment=”center” qode_css_animation=””][vc_empty_space height=”20″][vc_column_text]3. In the next step, fill in the appropriate contact details and click on “Provide Details” to add the required details for the quota.[\/vc_column_text][vc_empty_space height=”20″][vc_single_image image=”1204″ img_size=”full” alignment=”center” qode_css_animation=””][vc_empty_space height=”20″][vc_column_text]4. In the fly-out menu on the right hand side select the locations in which the quota is to be changed and select the corresponding “family”. Then you can define the new quota. For example 50.[\/vc_column_text][vc_empty_space height=”20″][vc_single_image image=”1205″ img_size=”full” alignment=”center” qode_css_animation=””][vc_empty_space height=”20″][vc_column_text]5. supply the support request and wait for implementation. In our case, the implementation took 6 hours.[\/vc_column_text][vc_empty_space height=”20″][vc_single_image image=”1206″ img_size=”full” alignment=”center” qode_css_animation=””][vc_empty_space height=”20″][vc_column_text]If you check the quotas again after the implementation, you will see that the “Total Regional vCPU” quota has also been increased:[\/vc_column_text][vc_empty_space height=”20″][vc_single_image image=”1207″ img_size=”full” alignment=”center” qode_css_animation=””][vc_empty_space height=”20″][vc_column_text]There is currently no SR to increase the regional quota alone. According to a GitHub issue, this should be changed in early 2019. From there is also the information that the Regional Quota is calculated as follows: “Maximum value of (current regional limit AND Max of (all newly requested SKU limits))”.<\/p>\n

Useful links<\/p>\n

https:\/\/docs.microsoft.com\/en-gb\/azure\/azure-supportability\/resource-manager-core-quotas-request<\/a>[\/vc_column_text][vc_empty_space height=”40″][vc_column_text]\n

Source: freepik.com<\/a><\/p>\n[\/vc_column_text][vc_empty_space height=”50″][vc_raw_html]JTNDYSUyMGhyZWYlM0QlMjJqYXZhc2NyaXB0JTNBaGlzdG9yeS5iYWNrJTI4JTI5JTIyJTNFJTNDc3BhbiUyMHN0eWxlJTNEJTIyY29sb3IlM0ElMjAlMjNmZjIwNzAlM0IlMjIlM0UlM0MlM0MlMjBCYWNrJTNDJTJGc3BhbiUzRSUzQyUyRmElM0U=[\/vc_raw_html][vc_empty_space height=”50″][vc_separator type=”small” position=”center” color=”#eeeeee” thickness=”2″ width=”1100″][vc_empty_space height=”100″][\/vc_column][\/vc_row][vc_row css_animation=”” row_type=”row” use_row_as_full_screen_section=”no” type=”full_width” angled_section=”no” text_align=”left” background_image_as_pattern=”without_pattern”][vc_column][vc_column_text]\n

LATEST POSTS<\/h2>\n[\/vc_column_text][vc_empty_space height=”30″]\n
\n