Help Docs

Azure Service Quota monitoring 

Azure enforces preconfigured resource limits on your subscription to ensure optimal performance and stability. To prevent unexpected provisioning failures, it's essential to account for these limits when designing and scaling your Azure environment. Proactively monitoring and planning for these constraints will help you maintain seamless operations and support future growth.

Site24x7's Azure Service Quota monitoring enables you to track quota usage proactively, set threshold-based alerts, and avoid unexpected service restrictions. By monitoring quotas across storage, compute, networking, and other key resource categories, you can ensure smooth cloud operations and timely capacity planning. 

Use case 

A CloudOps team needs to deploy additional virtual machines (VMs) to handle increased workload demand. However, an attempt to spin up new instances fails due to reaching the regional vCPU quota limit. 

How Site24x7 helps:

  • Site24x7's Azure Service Quota monitoring notifies the team when the vCPU utilization exceeds 80% of the allocated limit. This threshold can be flexibly configured based on the operation demands.

  • The team receives a trouble alert via email and mobile notification, prompting a review of available quotas.

  • Using Site24x7's Service Quotas dashboard, they identify that the vCPU quota needs to be increased and submit a quota request to Azure before deployment.

Thus, the CloudOps team optimized their vCPU for better resource allocation, and their auto-scaling stays unaffected since Site24x7's service quota monitoring takes care of the quota utilization and ensures smooth cloud operations.

This proactive approach prevents last-minute failures, ensuring uninterrupted service availability.

Prerequisites

  • Azure subscription access: Ensure your subscription includes the Reader role.

  • Enable Azure Resource Manager (ARM): Ensure that the ARM API is enabled for the Site24x7 application created in Azure for quota and usage data collection.

  • Enable the Microsoft quota resource provider: Navigate to Subscriptions > select your Subscription > select Resource providers from the left pane > click Register.

Site24x7 uses Azure Quota Service APIs to retrieve limit and usage metrics, correlating them for monitoring.

Setting up Azure Service Quota monitoring   

If you haven't added an Azure monitor yet, follow these steps to add one.

    1. Navigate to Cloud > Azure > select the Azure monitor > select Service Quotas from the left menu.

    2. Enable service quotas by clicking Enable Service Quota Monitoring.

    3. In the pop-up window that opens, provide an appropriate name for your service quota metric profile.

      Note

      A service quota metric profile is mandatory to add quota monitoring.

    4. Select the required metrics.

    5. Review your changes and click Save.

Enable Service Quota

Note
  • If you already have a service quota metric profile, it will be automatically associated with your current monitor. You can view the selected profile on the Edit Monitor page.
  • It takes up to 30 minutes for the data collection to complete, after which all the discovered quotas and their metrics will be listed under the Monitored Quotas tab.

Alternative method

Alternatively, you can enable service quotas by following the below steps.

    1. Navigate to Cloud > Azure > select the Azure monitor > select Service View.

    2. Click the hamburger iconnear Service View > Edit.

    3. On the Edit Azure Monitor page, under Advanced Configuration, toggle Enable Service Quotas to Yes.

    4. Select Quota Profiles: Use the drop-down to select an existing quota profile or create a new one by clicking the + icon.

    5. Click Save.

 Polling frequency 

The data refresh frequency for your service quotas is 30 minutes.  

Service Quotas dashboard   

The Service Quotas dashboard has three different views that help you get overall insights into your quotas.

Navigate to Site24x7 > Cloud > Azure > your Azure Account > Service Quotas to view the monitoring insights. The dashboard includes:

Top 100 Quota Usages 

You can see the Top 100 Quota Usages by selecting the subscription. Selecting All Subscriptions will give a centralized view of the top 100 quota usages across all your subscriptions.

The Criticality of the quotas depicts the usage of the quotas that need your attention based on four different criticality levels: High, Moderate, Low, and Info.

The Search bar allows you to search the quotas based on their name, region, unit, and so on.

Top 100 Quota Usages

Highlights

  • Displays the 100 highest quota utilization

  • Includes last updated timestamps and export options (CSV, PDF, Email, or Schedule Report)

  • Allows you to schedule reports to get the latest insights

Schedule Reports

 Monitored Quotas 

This view lists all the quotas under the subscription based on their category. Simply select the subscription and then the category, which can be Network, Storage, Compute, or Container App.

Access detailed insights such as:

  • Quota Metric
  • Unique Name
  • Region
  • Unit
  • Current Limit
  • Usage
  • Utilization Percentage

Monitored Quotas

Click Threshold Configuration at the top-right of the table to configure thresholds.  

Threshold configuration 

Set up proactive alerts when the resource usage, percent, or limit approaches thresholds for quotas in bulk or individually:

  • Bulk configuration:
    In the Monitored Quotas tab, click Threshold Configuration at the top-right of the table. Select a quota type and configure thresholds for multiple quotas simultaneously.
    Bulk Thresholds

  • Individual quotas:

    • Navigate to a specific quota in the Monitored Quotas tab.

    • Use the pencil iconin the Action column to set thresholds.

Threshold attributes include:

  • Limit, Usage, and Utilization Percentage thresholds.

  • Condition and Poll Strategy for fine-tuned alerts.

Removing a metric from monitoring

If you wish to remove a particular quota metric from monitoring:

  1. Click the hamburger iconnear Service Quotas, which opens up the Edit Azure monitor page.

  2. Under Advanced Configuration > General Settings, near the Service Quota Metric Profile drop-down, click the pencil icon.

  3. In the Metric Profile pop-up window, unselect the metrics which you wish to stop monitoring.

  4. Click Save.

Note

This action will stop Site24x7 from monitoring the metric from across all the monitored regions, and the metric will be removed from the immediate data collection.

Outages 

The Outages tab lists outages that happened in the selected subscription based on a preferred time duration.

It has the start and end time of the outage, the total duration of the outage, and the reason for the outage. You can also derive the list of outages specific to a desired time period by clicking the drop-down at the top-right of the page. 

Outages View

Nexus view 

Additionally, you can view all the subscriptions under the respective Management Group monitor or the Account-level monitor in a single centralized view.  

Nexus View

Supported quotas

We have segregated each quota under its respective quota categories.

Category Metrics
Storage - 1
  • Storage Accounts
Container App - 5
  • Managed Environment Count
  • Subscription NCA 100 GPUs
  • Session Pools
  • Subscription Consumption NCA 100 GPUs
  • Subscription Consumption T 4 GPUs
Compute - 54
  • Virtual Networks
  • Custom IP Prefixes
  • Public IP Prefixes
  • Public IP Addresses
  • Public IPv4 Addresses - Basic
  • Public IPv6 Addresses - Basic
  • Public IPv4 Addresses - Standard
  • Public IPv6 Addresses - Standard
  • Public IPv4 Addresses - Global Tier
  • Public IPv6 Addresses - Global Tier
  • Public IPv4 Addresses - Internet Routing Preference
  • Public IPv6 Addresses - Internet Routing Preference
  • Network Security Groups
  • NAT Gateways
  • Network Interfaces
  • Private Endpoints
  • Private Endpoint Redirect Maps
  • Load Balancers
  • Private Link Services
  • Application Gateways
  • Route Tables
  • Route Filters
  • Virtual Network Taps
  • Network Watchers
  • Packet Captures
  • Application Security Groups
  • DDoS Protection Plans
  • DDoS Customized Policies
  • Service Endpoint Policies
  • Network Intent Policies
  • Standard SKU Load Balancers
  • Auxiliary Mode Enabled Network Interfaces
  • DNS servers per Virtual Network
  • Custom DNS servers per P2SVpnGateway
  • Subnets per Virtual Network
  • IP Configurations per Virtual Network
  • Peerings per Virtual Network
  • Prefixes per Subnet
  • Security Rules per Network Security Group
  • Security Rules per Network Intent Policy
  • Routes per Network Intent Policy
  • Security rules addresses or ports per Network Security Group
  • Inbound Rules per Load Balancer
  • Frontend IP Configurations per Load Balancer
  • Outbound Rules per Load Balancer
  • Routes per Route Table
  • Routes with service tag per Route Table
  • Secondary IP Configurations per Network Interface
  • Secondary IP Configurations per PrivateEndpoint Network Interface
  • Inbound rules per Network Interface
  • Route filter rules per Route Filter
  • Route filters per Express route BGP Peering
  • Public IPv4 Prefix Length
  • Source NICs per Virtual Network Tap
Network - 171    
  • Availability Sets
  • Total Regional vCPUs
  • Virtual Machines
  • Virtual Machine Scale Sets
  • Dedicated vCPUs
  • Cloud Services
  • Total Regional Low-priority vCPUs
  • Standard BS Family vCPUs
  • Standard DSv2 Family vCPUs
  • Basic A Family vCPUs
  • Standard A0-A7 Family vCPUs
  • Standard A8-A11 Family vCPUs
  • Standard D Family vCPUs
  • Standard Dv2 Family vCPUs
  • Standard DS Family vCPUs
  • Standard G Family vCPUs
  • Standard GS Family vCPUs
  • Standard F Family vCPUs
  • Standard FS Family vCPUs
  • Standard NV Family vCPUs
  • Standard NC Family vCPUs
  • Standard H Family vCPUs
  • Standard Av2 Family vCPUs
  • Standard LS Family vCPUs
  • Standard Dv2 Promo Family vCPUs
  • Standard DSv2 Promo Family vCPUs
  • Standard MS Family vCPUs
  • Standard Dv3 Family vCPUs
  • Standard DSv3 Family vCPUs
  • Standard Ev3 Family vCPUs
  • Standard ESv3 Family vCPUs
  • Standard Dv4 Family vCPUs
  • Standard DDv4 Family vCPUs
  • Standard DSv4 Family vCPUs
  • Standard DDSv4 Family vCPUs
  • Standard Ev4 Family vCPUs
  • Standard EDv4 Family vCPUs
  • Standard ESv4 Family vCPUs
  • Standard EDSv4 Family vCPUs
  • Standard FSv2 Family vCPUs
  • Standard NDS Family vCPUs
  • Standard NCSv2 Family vCPUs
  • Standard NCSv3 Family vCPUs
  • Standard LSv2 Family vCPUs
  • Standard PBS Family vCPUs
  • Standard EIv3 Family vCPUs
  • Standard EISv3 Family vCPUs
  • Standard DCS Family vCPUs
  • Standard NVSv2 Family vCPUs
  • Standard MSv2 Family vCPUs
  • Standard HBS Family vCPUs
  • Standard HCS Family vCPUs
  • Standard NVSv3 Family vCPUs
  • Standard NV Promo Family vCPUs
  • Standard NC Promo Family vCPUs
  • Standard H Promo Family vCPUs
  • Standard DAv4 Family vCPUs
  • Standard DASv4 Family vCPUs
  • Standard EAv4 Family vCPUs
  • Standard EASv4 Family vCPUs
  • Standard NDSv3 Family vCPUs
  • Standard DCSv2 Family vCPUs
  • Standard NVSv4 Family vCPUs
  • Standard NDSv2 Family vCPUs
  • Standard NPS Family vCPUs
  • Standard HBrsv2 Family vCPUs
  • Standard NCASv3_T4 Family vCPUs
  • Standard NDASv4_A100 Family vCPUs
  • Standard EIDSv4 Family vCPUs
  • Standard XEISv4 Family vCPUs
  • Standard EIASv4 Family vCPUs
  • Standard HBv3 Family vCPUs
  • Standard MDSMediumMemoryv2 Family vCPUs
  • Standard MIDSMediumMemoryv2 Family vCPUs
  • Standard MSMediumMemoryv2 Family vCPUs
  • Standard MISMediumMemoryv2 Family vCPUs
  • Standard DASv5 Family vCPUs
  • Standard EASv5 Family vCPUs
  • Standard Ev5 Family vCPUs
  • Standard EIv5 Family vCPUs
  • Standard EDv5 Family vCPUs
  • Standard EIDv5 Family vCPUs
  • Standard ESv5 Family vCPUs
  • Standard EISv5 Family vCPUs
  • Standard EDSv5 Family vCPUs
  • Standard EIDSv5 Family vCPUs
  • Standard Dv5 Family vCPUs
  • Standard DDv5 Family vCPUs
  • Standard DSv5 Family vCPUs
  • Standard DDSv5 Family vCPUs
  • Standard DLSv5 Family vCPUs
  • Standard DLDSv5 Family vCPUs
  • Standard LSv3 Family vCPUs
  • Standard LASv3 Family vCPUs
  • Standard DCSv3 Family vCPUs
  • Standard DDCSv3 Family vCPUs
  • Standard DADSv5 Family vCPUs
  • Standard EADSv5 Family vCPUs
  • Standard FXMDVS Family vCPUs
  • Standard DPLDSv5 Family vCPUs
  • Standard DPLSv5 Family vCPUs
  • Standard DPDSv5 Family vCPUs
  • Standard DPSv5 Family vCPUs
  • Standard EPDSv5 Family vCPUs
  • Standard EPSv5 Family vCPUs
  • Standard NDAMSv4_A100Family vCPUs
  • Standard DCASv5 Family vCPUs
  • Standard ECASv5 Family vCPUs
  • Standard ECIASv5 Family vCPUs
  • Standard DCADSv5 Family vCPUs
  • Standard ECADSv5 Family vCPUs
  • Standard ECIADSv5 Family vCPUs
  • Standard NVADSA10v5 Family vCPUs
  • Standard NCADS_A100_v4 Family vCPUs
  • Standard EBDSv5 Family vCPUs
  • Standard EBSv5 Family vCPUs
  • Standard EIASv5 Family vCPUs
  • Standard EIADSv5 Family vCPUs
  • Standard NCADSA10v4 Family vCPUs
  • Standard DCACCV5 Family vCPUs
  • Standard DCADCCV5 Family vCPUs
  • Standard ECACCV5 Family vCPUs
  • Standard ECADCCV5 Family vCPUs
  • Standard EIBDSv5 Family vCPUs
  • Standard EIBSv5 Family vCPUs
  • Standard DCEV5 Family vCPUs
  • Standard DCEDV5 Family vCPUs
  • Standard ECEV5 Family vCPUs
  • Standard ECEDV5 Family vCPUs
  • Standard MS Medium Memoryv3 Family vCPUs
  • Standard MDS Medium Memoryv3 Family vCPUs
  • Standard MS High Memoryv3 Family vCPUs
  • Standard MIS High Memoryv3 Family vCPUs
  • Standard MDS High Memoryv3 Family vCPUs
  • Standard MIDS High Memoryv3 Family vCPUs
  • Standard HBv4 Family vCPUs
  • Standard HX Family vCPUs
  • Standard Bpsv2 Family vCPUs
  • Standard Bsv2 Family vCPUs
  • Standard Basv2 Family vCPUs
  • Standard NDSH100v5 Family vCPUs
  • Standard NGADSV620v1 Family vCPUs
  • Standard ECIEV5 Family vCPUs
  • Standard ECIEDV5 Family vCPUs
  • Standard NCadsH100v5 Family vCPUs
  • Standard NCCads2023 Family vCPUs
  • Standard NDI Sv 5MI300X Family vCPUs
  • Standard NVadsV710v5 Family vCPUs
  • Standard Storage Managed Disks
  • Premium Storage Managed Disks
  • Standard SSD Storage Disks
  • Standard SSDZRS Storage Disks
  • Premium ZRS Storage Disks
  • Ultra SSD Storage Disks
  • Premium V2 Storage Disks
  • Standard Storage Snapshots
  • Standard SSD Storage Snapshots
  • Premium Storage Snapshots
  • ZRS Storage Snapshots
  • Ultra SSD Total Size in GB
  • Premium V2 Total Disk Size in GB
  • Disk Encryption Sets
  • Disk Accesses
  • Attach InProgress Ultra SSD Disks
  • Attach InProgress Premium V2S SDDisks
  • Premium V2 Storage Snapshots
  • Premium V2 Total Snapshot Size in GB
  • Gallery
  • Gallery Image
  • Gallery Image Version
  • Gallery Application Version

 

Events  

Navigate to Applogs > set Infrastructure Events as the log type, and then you can construct your own query based on your requirements. With the below query, you can derive all the outage events related to the above-set thresholds.

logtype="Infrastructure Events" and productModule CONTAINS "AZURE-QUOTA" 

Infrastructure Events

Sample:

logtype="Infrastructure Events" and ProductModule CONTAINS "AZURE-QUOTA" groupby source 

Log Group by Source

logtype="Infrastructure Events" and ProductModule CONTAINS "AZURE-QUOTA" groupby severity 

Log Group by Severity

logtype="Infrastructure Events" and ProductModule CONTAINS "AZURE-QUOTA" and severity CONTAINS "Critical" 

Log Severity Critical

Note

If you have not set any threshold, when the utilization percentage reaches 100%, an event will be created.

License   

Every 10 service quota metrics consume one basic monitor license.

 

 

Was this document helpful?

Would you like to help us improve our documents? Tell us what you think we could do better.


We're sorry to hear that you're not satisfied with the document. We'd love to learn what we could do to improve the experience.


Thanks for taking the time to share your feedback. We'll use your feedback to improve our online help resources.

Shortlink has been copied!