Azure Key Vault Reviews

We were using the solution to store our keys that includes secrets, passwords, and also application properties.

The application properties and the ability to store our certificates too have been great aspects of the solution. 

Mainly, having the application properties where all our applications' configurations were stored in the key vault was very useful.

The initial setup is pretty simple. 

The stability is very good.

The solution can scale up as needed. 

The solution offers very reasonable pricing. 

I can't recall coming across any missing features or elements. 

The solution does not allow you to integrate with XML parties if it is not inside Azure itself.

I used the solution during my previous project that I handled last year. I used it for a full year, from January to December.

The solution is stable. I never had issues, for example, with stability, bugs or glitches, or crashing. It's reliable.

The solution can scale. It is already a platform as a service, and therefore, it's already scaled up.

Our entire company is currently using the product.

I did not use technical support when I worked with the product. Therefore, I cannot speak to how helpful or responsive they are. 

We did use HashiCorp Vault. We used to use it, and then we moved to Azure Key Vault due to the fact that it's a cloud platform as a solution and it is easy to implement.

The initial setup was straightforward, however, we never used the console. We always used to use the Azure CLIs to set everything up.

The pricing is very reasonable. It's not overly expensive.

We're a Microsoft partner.

I cannot recall which version of the solution I used for the project I worked on.

Overall, it's a great product.

There's nothing I dislike about the solution. I would rate the solution at 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 use the solution for a lending platform in the BFSI domain. It helps to store secrets. 

Azure Key Vault's performance is excellent. It makes infrastructure management easier. 

The solution needs to improve reliability and protection. 

I have been working with the product for three years. 

Azure Key Vault is stable.

The product is scalable. 

Microsoft's support is good. 

The tool's deployment is straightforward. 

Azure Key Vault is expensive. 

I rate Azure Key Vault an eight out of ten. 

The product’s advantageous feature is integration.

It is complicated to use different services and products along with Azure Key Vault. There should be a single vault for virtual servers, containers, and other services. It could be universal with the possibility to use all types of technologies. 

We have been using Azure Key Vault for two years.

The product is stable as it is cloud-based.

We have an enterprise agreement for support services. We encountered difficulties in communicating with the first-line support team.

Neutral

We use other products in parallel, including ARIS, AWS, HashiCorp, etc.

I rate Azure Key Vault an eight out of ten.

We use the solution to authenticate security features for environments. Using it, we can encrypt keys and protect the databases from getting hacked.

The solution works as an effective tool for securing our organization's databases.

They should add a key vault feature for the databases temporarily integrated into hybrid clouds. Also, they should make the key accessible once the databases migrate to another environment.

We have been using the solution for seven years.

The solution's customer service is excellent.

Positive

The solution's initial setup process is moderately complex. It is a time-consuming process if you are new to the product. But, if you know source applications and target databases, it just takes a few hours. Whereas in the case of larger environments, it might take days to complete.

Our in-house team deploys the solution. It requires three executives to work on larger deployments. Also, it requires a huge team when there are multiple databases to work with. 

The solution is affordable compared to other competitors.

I advise others to use the solution if they already work with Microsoft Azure environment. In such cases, they should not prefer integration with a third-party tool. They should consider other products if the databases are distributed to on-cloud and on-premises infrastructures.

I rate the solution as an eight.

We use the solution for API keys. We are migrating most of the data, including the application built in react native from the IBM server to Azure. AWS Key Vault stores secret keys and API keys.

Azure has its SLAs and Vault. We were never worried about the impact on security or any compliance with GDPR or others.

The product is very helpful. AI has been introduced to Azure. The services are being introduced thoroughly in Azure, especially in AI and IoT.

The solution could be cheaper.

I have been using Azure Key Vault for a year. We started migrating 20-22 applications from IBM server to Azure.

The product is stable. A few others are dynamic in Azure. We might need an extension for those. So, we moved to the cloud.

We've around three to four million users in one application.

During the migration process, we utilized Microsoft support for Azure Key Vault. We encountered a couple of issues that the vendor couldn't resolve, so we had to turn to Microsoft support for assistance.

The initial setup is easy. We have migrated around 20 applications in six months with the help of a vendor. There were a few architecture glitches otherwise it had a good impact on the deployment.

We have conducted this code assessment using the tool. Initially, we had two environments; development and production. We have set up multiple environments including development, and production. Additionally, we have initiated a force support assessment. We have commenced licensing for a few applications, utilizing both the relationship method and the refactor method. We have undertaken additional work on the porting part for a couple of applications. We are also focusing on automating this process as DevOps has been introduced.

Azure Key Vault is more expensive than Amazon.

I recommend the solution.

Overall, I rate the solution a seven 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.