Azure Dedicated HSM
Manage hardware security modules that you use in the cloud.
-
" "
Maintain full administrative and cryptographic control of your HSMs
-
Validated for FIPS 140-2 Level 3 and eIDAS Common Criteria EAL4+
-
" "
Migrate HSM applications to Azure with minimal changes and improved latency
Manage HSMs that you use in Azure
With Azure Dedicated HSM, you manage who in your organization can access your HSMs and the scope and assignment of their roles. You have full administrative and cryptographic control over your HSMs. Microsoft has no access to or visibility into the keys stored in them.
Enhance security and compliance with controls and certifications
Each HSM device comes validated against FIPS 140-2 Level 3 and eIDAS Common Criteria EAL4+, ensuring tamper resistance. This enables you to meet a wide variety of security and compliance requirements.
Easily migrate applications to Azure
Developed in partnership with Thales, the Thales Luna 7 HSM model A790 cloud-based HSM is compatible with many applications, simplifying migration of legacy or custom on-premises applications to Azure. Because minimal changes are needed for your on-premises applications to work in Azure, you save time. Hybrid capabilities allow you to run your legacy or custom applications on your on-premises Thales HSM or on Azure. Keep a copy of your keys on the Thales HSM for added security.
Comprehensive security and compliance, built in
-
Microsoft invests more than USD1 billion annually on cybersecurity research and development.
-
We employ more than 3,500 security experts who are dedicated to data security and privacy.
-
Azure has more certifications than any other cloud provider. View the comprehensive list.
-
Azure Dedicated HSM pricing
Azure Dedicated HSM allows you to do key management on a hardware security module that you control in the cloud.
Get started with an Azure free account
1
2
After your credit, move to pay as you go to keep building with the same free services. Pay only if you use more than your free monthly amounts.
3