Azure Key Vault Reviews

Users can store all the security credentials in Azure Key Vault, which only authorized users can access.

Azure Key Vault allows only identified users to get the credentials and rotates the keys automatically.

The solution's usage can be a little better from the user interface point of view. Azure Key Vault is a little complex from the usage point of view, and users should be able to use it in a much simpler way.

I have been using Azure Key Vault for two years.

Azure Key Vault is a highly stable solution.

Azure Key Vault is a highly scalable solution. Our clients for Azure Key Vault are mostly medium-sized businesses.

I rate Azure Key Vault an eight or nine out of ten for scalability.

Azure Key Vault’s technical support is very good.

Positive

I rate Azure Key Vault a four or five out of ten for the ease of its initial setup.

Azure Key Vault's deployment doesn't take much time and can be done in a few minutes.

Azure Key Vault is an affordable solution. On a scale from one to ten, where one is cheap, and ten is expensive, I rate Azure Key Vault's pricing a three out of ten.

I am working with the latest version of Azure Key Vault. I would recommend Azure Key Vault to other users because it is scaling up and getting better than other cloud solutions.

Overall, I rate Azure Key Vault an eight out of ten.

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 for passwords. Instead of adding the password to everything, you can add them to Azure Key Vault and directly use it whenever required, in whichever place it's needed.

The solution's most valuable features are reusability and safety. You don't have to type everything every time or remember things. Regarding safety, you don't have to keep track of the passwords. You can directly access those particular things in one go and at one particular location. You don't have to worry about password protection because it is handled by Azure.

Azure Key Vault has a lot of glitches. The solution's trial version should provide some more facilities so that people can try them and then decide whether to implement the tool in their project.

I have been using Azure Key Vault for three months.

Azure Key Vault has a lot of glitches. We faced an outage yesterday because some of our flow executes on ADF, and it failed. We have to continuously raise tickets with the support team. The outages impact our daily jobs.

I rate the solution’s stability a seven out of ten.

Azure Key Vault's scalability is good because it's a cloud-based solution. It is far better than on-premises tools, which is a good thing.

The solution's technical support is fine. However, I am not happy with the kind of acknowledgment Azure provides. If you're making changes to the tool that will impact the end user, you should inform them beforehand.

Neutral

The solution’s initial setup is easy. Since Azure Key Vault is a cloud-based service, you don't have to install it.

With Azure Key Vault, you get everything in one portal and don't have to go anywhere else, which is a good thing.

The solution's access policy is important. You can directly provide the kind of access you want to grant to any particular user or batch of users rather than monitor which particular user should assign which particular task and what things can be seen by which particular user. Those kinds of restrictions can be added directly using the access policy.

You need to maintain the solution. If the credentials are getting expired, you have to provide an update on that. One person is more than enough to maintain the solution.

Overall, I rate the solution a seven out of ten.

I use the solution for saving keys. We use it to manage encryption keys and secrets in our applications.

It is a good solution. I use it to deploy my services. All the features are valuable. The access policy feature helps secure content and resources. We use the automated key rotation feature to secure the deployments and the development process. It can be used to secure resources. The availability is high. We can integrate the tool with VMs, storage, and Azure App Service.

The product must provide AI features.

I have been using the solution for three to four years.

The tool has high stability.

The tool’s scalability is high. Our clients are small, medium, and enterprise businesses.

The support must be improved.

Positive

The initial setup is easy. The deployment took a few minutes.

The pricing is normal. The product is neither cheap nor expensive.

I am an implementer and designer. I will recommend the product to others to keep keys, secrets, and related information secure. Overall, I rate the product a ten 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.

We primarily use the solution for key management.

The access policies are the solution's most valuable aspect.

The solution is very stable.

The scalability is very good.

The pricing of the product is reasonable.

Technical support is helpful.

The rotation of key needs improvement. It needs to offer dynamic secrets management.

I've been using the solution for about a year or so. It hasn't been that long.

The solution is very stable. It doesn't crash or freeze. There are no bugs or glitches. It's reliable. 

The solution can scale well. It's not a problem at all. If a company needs to expand it, it can.

Our clients tend to be enterprises, and aren't overly small. 

You do need a support agreement, however, from what I have seen, it's quite reliable and knowledgeable. It's easy to reach them and to work with them.

The initial setup has a moderate amount of difficulty. It's neither extremely straightforward nor overly difficult.

You do need a special agreement in order to receive technical support.

While I don't directly deal with pricing, my understanding is that it's okay, and not too expensive.

We are currently looking at other solutions in order to compare them. We are also using HashiCorp Terraform and looking into HashiCorp Vault.

We are just a customer and an end-users. We tend to use the solution for our clients.

For those companies that want to work with the solution, I'd advise that they consider the use of and integration with Azure's pipeline.

Overall, I'd rate the solution at an eight out of ten. We've largely been quite happy with its capabilities.

I am a system architect and this is one of the products that I work with when designing systems for our customers. This key vault allows you to store passwords and secret keys so that you can retrieve them when needed. Each customer will have their own secret password that can be used in a cloud-based scenario to retrieve their login usernames, passwords, and other secrets.

The most valuable feature is that you can retrieve user account details from the cloud.

Azure needs to provide versions of Key Vault that are suitable for different sizes of companies. For example, we are not a big corporation that can afford corporate-level pricing. We have to strike a balance between the number of users and the volume of keys that are being used.

I have been using the Microsoft Azure Key Vault for close to two years.

This is a stable product and I haven't had any issues. The performance decreases as many keys are added to the vault. For example, it will be slow if we have 1,000 users.

Scalability is related to the licensing plan. At some point, the number of keys that can be stored will run out until the vault plan is upgraded.

The product support is awesome and I don't have any issues with it.

Azure is the first key vault that we have used.

The initial setup is straightforward. It is not complex, although it takes weeks to implement because we have to integrate with other modules.

Our in-house team handles deployment.

The cost of the Azure Key Vault is very high and the pricing model is based on the number of keys that you store and retrieve. It is billed in blocks, such as 1,000 passwords that I can store. However, if I am paying to store information for 1,000 users then the pricing is not discounted if I only need to store 500.

I am currently evaluating HashiCorp Vault because it is more economical than Azure Key Vault.

In summary, this is a good product and one that I recommend.

I would rate this solution an eight out of ten.