Azure Storage Accounts
Azure Storage is Microsoft's cloud storage solution for modern data storage scenarios offering highly available, massively scalable, durable, and secure storage for blobs, files, queues, tables, and disks.
Solid contracts, transparent operations, and an easy start — typically complete on four or five facets with one clear soft spot.
API Evangelist profiles Azure Storage Accounts the way a machine reads it — 157 machine-readable artifacts across 9 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Azure Storage Accounts scores 63.3/100 (strong), with a separate agent-readiness read of 48/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Azure Storage Accounts
Each block below is one kind of artifact we hold for Azure Storage Accounts. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 9
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Azure Storage Accounts BlobContainers API
The BlobContainers API from Azure Storage Accounts — 8 operation(s) for blobcontainers.
Azure Storage Accounts BlobService API
The BlobService API from Azure Storage Accounts — 2 operation(s) for blobservice.
Azure Storage Accounts LocationUsage API
The LocationUsage API from Azure Storage Accounts — 1 operation(s) for locationusage.
Azure Storage Accounts ManagementPolicies API
The ManagementPolicies API from Azure Storage Accounts — 1 operation(s) for managementpolicies.
Azure Storage Accounts Operations API
The Operations API from Azure Storage Accounts — 1 operation(s) for operations.
Azure Storage Accounts PrivateEndpointConnections API
The PrivateEndpointConnections API from Azure Storage Accounts — 1 operation(s) for privateendpointconnections.
Azure Storage Accounts PrivateLinkResources API
The PrivateLinkResources API from Azure Storage Accounts — 1 operation(s) for privatelinkresources.
Azure Storage Accounts Skus API
The Skus API from Azure Storage Accounts — 1 operation(s) for skus.
Azure Storage Accounts StorageAccounts API
The StorageAccounts API from Azure Storage Accounts — 11 operation(s) for storageaccounts.
Scroll within the panel for all 9 ·
Pricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Azure Storage Accounts Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Semantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Spectral Rules 2
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Azure Storage Accounts API Rules
SPECTRALAzure Storage Accounts API Rules
SPECTRALJSON Schema 46
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
AccountSasParameters
JSON SCHEMAActiveDirectoryProperties
JSON SCHEMAAzureFilesIdentityBasedAuthentication
JSON SCHEMABlobContainer
JSON SCHEMABlobRestoreParameters
JSON SCHEMABlobRestoreRange
JSON SCHEMABlobRestoreStatus
JSON SCHEMABlobServiceItems
JSON SCHEMABlobServiceProperties
JSON SCHEMAChangeFeed
JSON SCHEMACheckNameAvailabilityResult
JSON SCHEMAContainerProperties
JSON SCHEMACustomDomain
JSON SCHEMADateAfterCreation
JSON SCHEMADateAfterModification
JSON SCHEMADimension
JSON SCHEMAEncryption
JSON SCHEMAEncryptionService
JSON SCHEMAEncryptionServices
JSON SCHEMAEndpoints
JSON SCHEMAGeoReplicationStats
JSON SCHEMAIdentity
JSON SCHEMAImmutabilityPolicyProperties
JSON SCHEMAImmutabilityPolicyProperty
JSON SCHEMAImmutabilityPolicy
JSON SCHEMAIPRule
JSON SCHEMAKeyVaultProperties
JSON SCHEMALeaseContainerRequest
JSON SCHEMALeaseContainerResponse
JSON SCHEMALegalHoldProperties
JSON SCHEMALegalHold
JSON SCHEMAListAccountSasResponse
JSON SCHEMAListContainerItem
JSON SCHEMAListContainerItems
JSON SCHEMAListServiceSasResponse
JSON SCHEMAManagementPolicyAction
JSON SCHEMAManagementPolicyBaseBlob
JSON SCHEMAManagementPolicyDefinition
JSON SCHEMAManagementPolicyFilter
JSON SCHEMAManagementPolicyProperties
JSON SCHEMAManagementPolicyRule
JSON SCHEMAManagementPolicySchema
JSON SCHEMAManagementPolicy
JSON SCHEMARestorePolicyProperties
JSON SCHEMATagProperty
JSON SCHEMAUpdateHistoryProperty
JSON SCHEMAScroll within the panel for all 46 ·
JSON Structure 46
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Azure Storage Accounts Account Sas Parameters Structure
JSON STRUCTUREAzure Storage Accounts Blob Container Structure
JSON STRUCTUREAzure Storage Accounts Blob Restore Parameters Structure
JSON STRUCTUREAzure Storage Accounts Blob Restore Range Structure
JSON STRUCTUREAzure Storage Accounts Blob Restore Status Structure
JSON STRUCTUREAzure Storage Accounts Blob Service Items Structure
JSON STRUCTUREAzure Storage Accounts Blob Service Properties Structure
JSON STRUCTUREAzure Storage Accounts Change Feed Structure
JSON STRUCTUREAzure Storage Accounts Container Properties Structure
JSON STRUCTUREAzure Storage Accounts Custom Domain Structure
JSON STRUCTUREAzure Storage Accounts Date After Creation Structure
JSON STRUCTUREAzure Storage Accounts Date After Modification Structure
JSON STRUCTUREAzure Storage Accounts Dimension Structure
JSON STRUCTUREAzure Storage Accounts Encryption Service Structure
JSON STRUCTUREAzure Storage Accounts Encryption Services Structure
JSON STRUCTUREAzure Storage Accounts Encryption Structure
JSON STRUCTUREAzure Storage Accounts Endpoints Structure
JSON STRUCTUREAzure Storage Accounts Geo Replication Stats Structure
JSON STRUCTUREAzure Storage Accounts Identity Structure
JSON STRUCTUREAzure Storage Accounts Immutability Policy Structure
JSON STRUCTUREAzure Storage Accounts Ip Rule Structure
JSON STRUCTUREAzure Storage Accounts Key Vault Properties Structure
JSON STRUCTUREAzure Storage Accounts Lease Container Request Structure
JSON STRUCTUREAzure Storage Accounts Legal Hold Properties Structure
JSON STRUCTUREAzure Storage Accounts Legal Hold Structure
JSON STRUCTUREAzure Storage Accounts List Container Item Structure
JSON STRUCTUREAzure Storage Accounts List Container Items Structure
JSON STRUCTUREAzure Storage Accounts Management Policy Rule Structure
JSON STRUCTUREAzure Storage Accounts Management Policy Structure
JSON STRUCTUREAzure Storage Accounts Tag Property Structure
JSON STRUCTUREAzure Storage Accounts Update History Property Structure
JSON STRUCTUREScroll within the panel for all 46 ·
Examples 46
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Scroll within the panel for all 46 ·
Security Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Azure Storage Accounts — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 2
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 3
Pagination, idempotency, versioning, errors, and events
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 4
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
← All providers · Data indexed from github.com/api-evangelist/azure-storage-accounts · machine-readable index on apis.io