Azure Key Vault Reviews

We use the Azure Key Vault to encrypt and to get our secrets such as passwords and connection strings.

The use of Azure Key Vault is vital to the security of our organization. Here we store our credentials, secrets, tokens, connection strings, and any other information needed to access external services and cloud providers. This service is essential to ensure a high level of security for our company.

The most valuable feature of the solution is the search for secrets feature that we use to store our passwords and connection strings. I also like objects such as keys and certificates.

Azure Key Vault is simpler to use compared to other certificate or password managers such as HashiCorp Vault and ManageEngine Password Manager Pro.

We can currently configure RBAC, Azure role-based access control, or a voucher access policy. The voucher access policy can be improved by configuring it based on groups, rather than just applications or users.

I have been using the solution for three years.

The solution is extremely stable. We have not had any issues or downtime with Azure Key Vault.

The solution is scalable and always responds to our demands.

We currently have around 500 people in our organization using the solution.

The technical support team is good and they provided satisfactory results.

Positive

The initial setup is straightforward. The deployment takes two to three minutes.

The implementation was completed in-house.

We have seen a return on investment for our organization with Azure Key Vault because of its low price and security. 

Compared to other solutions, Azure Key Vault is much cheaper. 

I give the price of the solution a ten out of ten.

I give the solution a ten out of ten.

The solution is self-maintaining. We have implemented EIS, and infra as a code, and incorporated a CI/CD process to automate the maintenance in our environment.

I always recommend going to Microsoft Learn for its rich knowledge base. Azure Key Vault is an excellent solution for improving organizational security, and it offers great value for money.

We use the solution to store our keys securely because authentication, encryption, and endpoint keys are significant concerns. Azure Key Vault allows storing confidential and secure information in an encrypted way, protecting our keys from threats or theft.

We have over 100 end users spread over geographically diverse areas in the US, Europe, the UK, Asia Pacific, and India. We operate a shared environment where users can store their passwords and keys in the vault and share them within teams.

Azure Key Vault provides secure storage for all of our keys in a single place, and we can quickly retrieve them when required.

The solution does an excellent job of storing and retrieving our stored keys.

It has a favorable UI.

Azure Key Vault has good integrations with other solutions we use, as we operate a Microsoft Azure environment.

I want to see faster key retrieval, as it sometimes takes a while. 

Better integration with other third-party cloud providers, such as AWS and GCP, should be there. That's something I expect from a Microsoft-built product.  

I've been using Azure Key Vault for approximately two years.

The tool is stable and relatively mature in the market, with many organizations using it worldwide.

The scalability is good; we have over 100 keys and passwords stored in the vault, and it works perfectly.

There is little need for technical support, as Azure Key Vault is a fully managed solution. No application runs in our environment; it's just a password repository. Overall though, the technical support is excellent.

Positive

We have always used Azure Key Vault, and we chose it because integration and compatibility are significant challenges for us. We require a product that's fully compatible and easily integrated with our existing applications, databases, and services.

We also tried various third-party and open-source software, such as Skyflow and a HashiCorp product.

The initial setup is straightforward as it is managed by Microsoft and can be enabled in a few clicks through Microsoft Azure. There is no installation or separate deployment required. Five to six staff carried out the initial setup and implementation. There is no maintenance required from our side.

We dealt directly with Microsoft as we were already customers with them. 

We have seen a return on our investment, as security is a significant challenge for us. We want to keep our information as secure as possible to protect our data from third-party attacks and unauthorized users, and Azure Key Vault helps us do that.

The pricing is reasonable and flexible, especially for those already using Microsoft Azure Cloud services. There is a cost associated with retrieval and storage, which is a few dollars. Otherwise, the price can be customized according to requirements, such as how many keys need to be stored.

We evaluated AWS Certificate Manager, but Azure Key Vault was a better fit. 

I rate the solution 10 out of 10. 

I highly recommend the solution to those who already use Microsoft products and have an environment where applications run through Azure. Azure Key Vault would be a great place to securely store all of your confidential information.

I use Azure Key Vault to securely store and manage my API keys, passwords, and certificates. It allows me to store them securely and share access without revealing the secrets. Azure Key Vault also automates password rotation every sixty days and offers options for managing keys either by me or by Azure.

Azure Key Vault securely stores passwords and secrets, eliminating the need to share them. Instead, access can be provided to users who log in with their own credentials. Integration with Azure services and third-party applications is seamless, as it's readily available and requires no specific deployment. Automatic retrieval of keys and certificates simplifies usage across different platforms. Overall, Azure Key Vault offers efficient key storage and management with easy integration across various services and applications.              

Azure Key Vault is very affordable, with charges of less than a dollar for over ten thousand keys. Microsoft regularly updates and upgrades the service, offering a user-friendly interface and robust security features, including AES 256 encryption.

Overall, I haven't identified any significant areas for improvement as Azure Key Vault already offers comprehensive functionality and security.

I have been using Azure Key Vault for the past 5 years now.

I'd rate the stability of Azure Key Vault as a nine out of ten. While it's very reliable, there's always room for improvement.

Scalability isn't a concern for Azure Key Vault as it's primarily for storing keys and certificates. There's no specific limit to the number of keys you can store. Our company has around seven thousand users utilizing the product.

Support from Microsoft is available, though I haven't personally used it. 

Positive

Setting up Azure Key Vault is straightforward and safe, taking about ten to fifteen minutes.There's no need for additional worry or complex deployment steps. It's a pre-deployed service on Azure, so you just need to subscribe and start using it.

For deployment and maintenance of Azure Key Vault, you typically need a technical architect and an engineer, possibly a product manager.

Azure Key Vault plays a crucial role in ensuring compliance with regulatory and governance policies by securely managing secrets and limiting access to only necessary personnel. For example, Azure Key Vault allows us to implement robust access control policies, such as distinguishing between administrative access and application-to-database communication. This helps maintain a clear separation of duties and enhances overall security.

It is a cheap option.

For those considering Azure Key Vault, I highly recommend it for consolidating and managing security assets in one place. Integration with various enterprise applications is already robust. Updates are frequent and timely, addressing any identified bugs promptly. Overall, Azure Key Vault meets our needs effectively. I rated it as nine instead of ten because there's always room for improvement in any product, including Azure Key Vault. While it's reliable, there may be areas where enhancements can be made based on customer feedback and experiences.

We are a financial institution and we are using this product to manage our keys. We are currently trying to roll out a "Bring Your Own Key" solution for Azure and Office 365.

The GUI was quite easy for me to use.

Integration with Fortanix is good.

The integration with Thales HSM is complex and is not out-of-the-box. Uploading the keys was quite a tedious process.

We are just beginners with the Microsoft Azure Key Vault and only started using it within the past six months.

We have approximately 150,000 employees across the organization.

Technical support from Microsoft is excellent. The reason we still buy Microsoft products is because of their support. The documentation is good and they also provide free, professional support.

The premium support is available at an additional cost, but professional support is free with the license.

Prior to Azure Key Vault, we were using the Bring Your Own Key solution, Thales Hardware Security Module (HSM). It worked seamlessly to generate our own key and upload it to the key vault. However, with Azure and Office 365, Microsoft manages the keys. I started using Azure Key Vault because it is an out-of-the-box feature with Azure, and it replaced our Thales HSM.

The installation of Thales HSM is a little bit complex. When we installed it, we needed to have two VDAs. There is an online VDA and an offline VDA, and we have to retrieve information from the offline one and pass it to the online one. These are complex tasks in our environment. Because it is a highly regulated industry, even moving a key is not easy for us. We have to go through all of the processes.

Because of the complications that we have had, we were looking at replacing Thales HSM with Fortanix. It integrates with Azure Key Vault and the key upload process is quite easy.

Pricing is quite reasonable and support is included, although premium support is available for an additional fee.

I am currently researching and evaluating HashiCorp Vault. We have not yet run a PoC but I am learning the differences between these two solutions. In addition to Azure, we have AWS and multiple cloud platforms, and we have heard that HashiCorp Vault is the best solution for cases like this.

HashiCorp Vault is open-source and has a command-line interface. 

One of the things that I would like to know is whether HashiCorp can be used for Azure workloads. For example, can it be used in a situation where a user brings their own key for Office 365, or does that only work with Azure Key Vault? 

Overall, this is a good product and the support is fantastic.

I would rate this solution an eight out of ten.

Azure Key Vault is used to store the encrypted keys. It can be used from the application side or the device side.

The centralized storage and secure storage are features we like. We don't find many effective solutions where we can securely store the encryption keys. So that is essentially, that is what we appreciate.

Many times, the first round of support itself will fail, and they will bring some more competent people in the subsequent support. By then, we will lose some good amount of time. The technical support needs improvement. 

I have been using Azure Key Vault for eight years. 

I would rate the stability a ten out of ten. 

The solution is highly scalable, you can scale up to any level. Our direct clients are small to medium businesses, but we also have large indirect clients, such as Microsoft in the US.

The initial setup is straightforward. The deployment takes two weeks. I would rate the initial setup a ten out of ten. 

Overall, I would rate the solution a nine out of ten. 

We use the solution to secure and store managed sensitive information and cryptographic keys in an application secret.

The solution uses the encryption technique to store the secret information data that uses EPCE. There is also one feature that monitors Azure Key Vault.

They should improve its policies, which sometimes reapplied but don't sync properly between the Key vault and the role-based access. When I put some roles on the user side, it sometimes misses the end data to secure.

One feature that could be added is the transparency of Key stored. There could be a feature to monitor the Key Vault because we can't monitor the Key Vault with a third party. We can't configure the automation or sync the key vault. We store passwords and all those things.

The user intervention also needs to be implemented there. This allows the user to automatically change the password, ensuring that it synchronizes and updates across all stored keys.

I have been using Azure Key Vault for two years.

The product is stable.

The solution is scalable. If they improve certain things with the update, that will be a more scalable product. There are a lot of users that use the Key Vault because it is the organization’s choice.

The initial setup is super easy.

There is a key that says, 'MS bug is there.' Azure has keyword secret information and connectivity issues. Azure File Share has Key connectivity issues. If we share some files and link through the Key, it loses connection.

The product is expensive compared to other products. It is costly to install as data records are charged based on the data. The Key type and plans are the factors that affect the pricing.

We are implementing Azure Key for certain projects. It completely depends on the project. Suppose your company gives us a project and asks us to implement Azure Key for other users.

I don't recommend it to everyone. It completely depends on the scenario base if you use a VM application or shared data. You can use Key Vault to secure information when transferring over the network. Sometimes, you are trying to assess your web information, and it is not working because of the connectivity issue due to some access control policies.

If you are the user and can work on the Azure portal or have access, you may be the support or IT person. You have the right to choose the architecture we must implement in our organization. They want to implement that on their user, but that's not a suitable option for everyone. We have 2,000 employees using this solution. We should have a strong plan to implement the Key Vault.

Anyone can learn Azure Key Vault within a day or two days.

There's a lot of work to do on the standalone side. If we are required to create a different workflow or automate it, then it's not possible or difficult to do that. If I want to keep the alerts on my email or team channel, that isn't easy to automate with the help of the Sentinel.

I need to use Azure Key Vault to ensure my application sends me refined data weekly. This data includes high and low alerts, which are sent to my email address or possibly generate an incident using a third-party API such as ServiceNow or Jira.

We can automate several things. We can fetch the log, but we can't automate that defender workflow itself in Container.

The solution is best because it completely secures passwords, which we can use to access.

Overall, I rate the solution an eight out of ten.

We use Azure Key Vault to store secrets. 

The solution needs to improve its cost. 

I have been using the solution for five years. 

I rate Azure Key Vault's stability a ten out of ten. 

The product's scalability is perfect. My company has around 100-200 users for the solution. 

The tool's installation is straightforward. 

We did the solution's deployment in-house. 

I rate the tool a ten out of ten. 

The primary use case is for storing secrets.

It has improved our organization. We have been able to secure our passwords and secrets. We didn't have to add an extra tool in addition to this solution.

The most valuable feature is the ability to store secrets securely and encrypt them. It is pretty easy and straightforward to use.

I would like more code examples.

Over six months.

It is a reliable solution.

I have had no problems with scalability.

We are deploying it on 10 client systems.

I haven't needed support for this application. However, when I need support from Microsoft, I get it immediately.

I went straight to this solution.

The initial setup was straightforward.

Including research and getting up to speed with the technology, the deployment took less than a week for the PoC. Deploying it all the way to production took about a month. It took a week to determine that it was the right tool. It took another three weeks to implement in all environments, like UAT production and test. We tried it on a dev environment first, then we implemented it over different stages, like QA, test, and production. 

We deploy the solution in just one location.

I did the deployment.

It is a good deal.

The pricing is decent. It has a pretty low price. It is a straightforward cost based on usage.

I just went straight to Azure Key Vault.

Follow the Microsoft official documentation for this solution. It is pretty straightforward and very well documented.

I would rate Azure Key Vault as nine out of 10.