Microsoft Azure Azure Dedicated HSM Resource Provider
Browse all Azure APIs★ Only Publicly Available OpenAPI DocumentSecuritySecrets Managementoauth26 EndpointsREST
For Agents
Provision and manage single-tenant FIPS 140-2 Level 3 HSM appliances under Microsoft.HardwareSecurityModules. Supports six endpoints for listing, retrieving, creating, patching, and deleting dedicated HSM resources.
Use for: I need to provision a Dedicated HSM in eastus2 for FIPS 140-2 Level 3 workloads, List all Dedicated HSMs in subscription 1111-2222, Retrieve the network profile and SKU of a Dedicated HSM, Find which subnet a Dedicated HSM is attached to
Not supported: Does not perform key generation, signing, or encryption operations and does not manage Key Vault or Managed HSM resources — use for Dedicated HSM appliance lifecycle only.
The Azure Dedicated HSM Resource Provider API manages single-tenant Hardware Security Module appliances (Microsoft.HardwareSecurityModules/dedicatedHSMs) provisioned into a customer's virtual network. It exposes operations to list, create, update, and delete HSM resources scoped to a subscription or resource group. Dedicated HSMs are FIPS 140-2 Level 3 validated and intended for workloads that need direct, exclusive control of cryptographic hardware rather than the multi-tenant Key Vault service.
Install Jentic One Beta
Connect the Azure Dedicated HSM Resource Provider to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Azure Dedicated HSM Resource Provider, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Azure Dedicated HSM Resource Provider API.
Provision a single-tenant Dedicated HSM appliance into a customer subnet
List all Dedicated HSMs across a subscription or scoped to a resource group
Retrieve a specific Dedicated HSM to inspect SKU, location, and network profile
Patch tags or zone information on an existing Dedicated HSM
Delete a Dedicated HSM that is no longer required
Bind a Dedicated HSM to a stable management network interface within the customer VNet
Use Cases
Patterns agents use Azure Dedicated HSM Resource Provider API for, with concrete tasks.
★ Provision a Compliance-Grade HSM Appliance
Deploy a single-tenant Dedicated HSM into a customer-owned subnet so cryptographic keys never leave FIPS 140-2 Level 3 hardware controlled by the customer. The Resource Provider API takes a single PUT with location, SKU (SafeNet Luna Network HSM A790), and a network profile referencing the target subnet and stable IP. After provisioning, application servers connect to the HSM directly via the appliance's documented client tooling.
PUT /subscriptions/{subscriptionId}/resourceGroups/rg-crypto/providers/Microsoft.HardwareSecurityModules/dedicatedHSMs/payments-hsm with location=eastus2, sku.name=SafeNet Luna Network HSM A790, and a networkProfile pointing at subnet hsm-subnet.
Cryptographic Hardware Inventory
Produce a portfolio inventory of every Dedicated HSM across subscriptions to satisfy compliance reporting. The API's DedicatedHsm_ListBySubscription returns each HSM with its location, SKU, zones, and network profile, which is enough to build an audit-ready table. The same flow applies for resource-group scoped queries and is callable from any pipeline that has reader access.
List all Dedicated HSMs in subscription 1111-2222 and emit a row per HSM with name, location, sku.name, zones, and networkProfile.subnet.
Decommission Replaced HSM Appliances
Cleanly remove Dedicated HSMs that have been replaced with newer hardware or migrated to managed HSM offerings. The DELETE operation tears down the resource at the resource provider level, after which the customer is no longer billed for the appliance. This complements out-of-band procedures for key migration, which the API does not manage directly.
DELETE /subscriptions/{subscriptionId}/resourceGroups/rg-crypto/providers/Microsoft.HardwareSecurityModules/dedicatedHSMs/legacy-hsm.
Agent-Driven HSM Lifecycle Reporting
A Jentic agent runs a recurring job that lists every Dedicated HSM, checks zones and SKUs against a compliance baseline, and either patches non-compliant tags or escalates the resource for review. The agent uses the same six endpoints in this spec to enumerate, inspect, and patch HSMs without portal access.
List Dedicated HSMs in subscription 1111-2222, find any without the tag environment=production, and PATCH each to add the missing tag.
Key Endpoints
6 endpoints — the azure dedicated hsm resource provider api manages single-tenant hardware security module appliances (microsoft.
METHOD
PATH
DESCRIPTION
GET
/subscriptions/{subscriptionId}/providers/Microsoft.HardwareSecurityModules/dedicatedHSMs
List Dedicated HSMs across the subscription
GET
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.HardwareSecurityModules/dedicatedHSMs
List Dedicated HSMs in a resource group
GET
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.HardwareSecurityModules/dedicatedHSMs/{name}
Get a single Dedicated HSM
PUT
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.HardwareSecurityModules/dedicatedHSMs/{name}
Create or update a Dedicated HSM
PATCH
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.HardwareSecurityModules/dedicatedHSMs/{name}
Patch tags or zones on an HSM
DELETE
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.HardwareSecurityModules/dedicatedHSMs/{name}
Delete a Dedicated HSM
GET
/subscriptions/{subscriptionId}/providers/Microsoft.HardwareSecurityModules/dedicatedHSMs
List Dedicated HSMs across the subscription
GET
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.HardwareSecurityModules/dedicatedHSMs
List Dedicated HSMs in a resource group
GET
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.HardwareSecurityModules/dedicatedHSMs/{name}
Get a single Dedicated HSM
PUT
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.HardwareSecurityModules/dedicatedHSMs/{name}
Create or update a Dedicated HSM
PATCH
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.HardwareSecurityModules/dedicatedHSMs/{name}
Patch tags or zones on an HSM
DELETE
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.HardwareSecurityModules/dedicatedHSMs/{name}
Delete a Dedicated HSM
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Azure AD service principal credentials stay in the Jentic MAXsystem vault. Agents call Microsoft.HardwareSecurityModules endpoints with a scoped bearer token issued at runtime, so AAD secrets never enter prompts and HSM client material remains under the customer's separate operational control.
Intent-based discovery
Agents search Jentic by intent (e.g. "provision dedicated hsm in azure") and Jentic returns the matching DedicatedHsm operation with its full request schema, including the networkProfile and SKU fields, so the agent does not need to read ARM docs.
Time to first call
Direct integration: 1-2 days for AAD setup, networkProfile validation, and ARM long-running operation polling. Through Jentic: under 1 hour — search, load schema, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Azure Dedicated HSM Resource Provider API through Jentic.
What authentication does the Azure Dedicated HSM API use?
Azure Active Directory OAuth 2.0 via the azure_auth scheme (user_impersonation scope) on https://management.azure.com/. With Jentic, AAD client credentials live in the MAXsystem vault and the agent receives a runtime bearer token rather than the secret itself.
Can I provision a Dedicated HSM with this API?
Yes. PUT /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.HardwareSecurityModules/dedicatedHSMs/{name} with location, sku.name (SafeNet Luna Network HSM A790), and a networkProfile that references the target subnet plus an optional stable IP.
What are the rate limits for the Azure Dedicated HSM API?
It shares Azure Resource Manager subscription throttling, typically 12,000 reads and 1,200 writes per hour per subscription. HSM provisioning itself is a long-running operation; clients should poll the resource until provisioningState reaches Succeeded.
How do I list every Dedicated HSM in my subscription through Jentic?
Search Jentic for "list azure dedicated hsm", load the schema for DedicatedHsm_ListBySubscription, then execute with subscriptionId. Sign up at https://app.jentic.com/sign-up to obtain an API key.
How does this differ from Azure Key Vault?
Azure Key Vault and Managed HSM are multi-tenant or pooled services managed by Microsoft. Dedicated HSM gives the customer exclusive use of an appliance attached to their VNet, with direct cryptographic protocol access for workloads that require single-tenant hardware and explicit compliance control.
Are HSM key operations performed through this API?
No. This is a control plane that provisions the appliance. Cryptographic operations (key generation, signing, encryption) happen via the HSM vendor's client tooling and protocol stack against the appliance's network address inside your VNet.
GET STARTED