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.

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. 

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.

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. 

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 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.

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.

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.