azure-quotas
Check Azure Quotas and Regional Capacity
Azure deployment plans can fail when regional quotas are unknown or exhausted. This skill checks limits and usage, compares regions, and guides increase requests.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "azure-quotas" from https://skillstore.io/skills/microsoft-azure-quotas.md and its manifest at https://skillstore.io/api/skills/microsoft-azure-quotas/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "azure-quotas". Check standardDSv3Family capacity in eastus.
Expected outcome:
- Resource: standardDSv3Family
- Region: eastus
- Limit: 350 vCPUs
- Current usage: 50 vCPUs
- Available capacity: 300 vCPUs
Using "azure-quotas". Compare 100 available vCPUs across eastus, eastus2, and westus2.
Expected outcome:
- eastus2 meets the requirement with 180 available vCPUs.
- westus2 meets the requirement with 120 available vCPUs.
- eastus does not meet the requirement with 60 available vCPUs.
Using "azure-quotas". Plan an increase to 500 DSv3 family vCPUs in eastus.
Expected outcome:
Current limit and usage are shown first. The proposed request targets 500 vCPUs and waits for confirmation before submission.
Security Audit
Medium RiskThe static alerts are false positives caused by documented Azure CLI examples, Markdown code formatting, standard error redirection, and expected read-only quota queries. Two semantic risks remain: the scripts install an Azure CLI extension without confirmation, and the Bash script embeds Azure response data directly into Python source.
Confirmed security concerns (2)
Risk Factors
🌐 Network access (9)
⚙️ External commands (50)
📁 Filesystem access (4)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/microsoft-azure-quotas/audits/5?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/microsoft-azure-quotas?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/microsoft-azure-quotas?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/microsoft-azure-quotas/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/microsoft-azure-quotas.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
microsoft. (2026). azure-quotas security audit report (audit version 5) [Author version 1.1.2]. Skillstore. https://skillstore.io/skills/microsoft-azure-quotas/audits/5BibTeX citation
@techreport{microsoft-microsoft-azure-quotas-2026,
author = {microsoft},
title = {azure-quotas security audit report (audit version 5)},
institution = {Skillstore},
year = {2026},
number = {5},
url = {https://skillstore.io/skills/microsoft-azure-quotas/audits/5},
note = {Author version 1.1.2}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "azure-quotas security audit report (audit version 5)"
version: "1.1.2"
type: report
authors:
- name: "microsoft"
date-released: "2026-07-23"
url: "https://skillstore.io/skills/microsoft-azure-quotas/audits/5"
identifiers:
- type: other
value: "skillstore:microsoft-azure-quotas:audit:5"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Validate Deployment Capacity
Check whether a planned workload fits available quota before selecting a region.
Diagnose Quota Failures
Compare current usage with limits when an Azure deployment reports a quota error.
Plan Quota Increases
Review current capacity and prepare a scoped quota increase request for approval.
Try These Prompts
Check all Microsoft.Compute quotas in eastus for my current Azure subscription. Show each limit, current usage, and available capacity.
Check <resource-name> for <provider> in <region> using subscription <subscription-id>. Explain whether <required-capacity> additional units fit.
Compare <resource-name> quota across <region-list>. Rank regions by available capacity and identify any region that meets <required-capacity>.
Prepare a quota increase plan for <resource-name> in <region>. Show current values and the exact scope. Do not submit changes until I confirm.
Best Practices
- List quotas first to discover the exact Azure quota resource name.
- Verify the active subscription and regional scope before reading or changing quota.
- Confirm the requested limit and scope before submitting any quota increase.
Avoid
- Do not infer quota resource names from ARM resource types.
- Do not treat a No Limit response as proof of unlimited capacity.
- Do not submit quota increases without explicit user confirmation.
Frequently Asked Questions
What permissions are required?
Does the skill require Azure CLI?
Can it compare multiple regions?
Can it request a quota increase?
Why does the quota API return BadRequest?
Does a No Limit value mean unlimited capacity?
Developer Details
Author
microsoftLicense
MIT
Author version
v1.1.2
Skillstore revision
r2
Ref
ebdfe608f5de2b66ff37ab4af12af8ac4f5e8006
Maintenance freshness
7/25/2026
Usage
4 downloads · 120 views
File structure