Azure Key Vault Reviews

We have an application connecting to the database. So we have implemented an authentication in place wherein without that particular secret value, it won't be authenticated. So that is a use case that I can tell you about Azure Key. We have implemented it for some small identity providers as well. 

Using Azure key Vault has increased the security of our organization. 

I would say its granular access control is the most valuable feature.

It would be great if it would integrate with other cloud solutions.

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

I think the stability works perfectly. I've never seen a block from the cloud side. But there might be some problems when we are configuring it. So maybe we are missing some strings or something, but I have never seen an issue from the cloud side.

A thousand people using the solution at present.

You have to configure based on, like, who should access routers, security should be generated, the identity management and everything. And Azure Microsoft people have provided a good documentation on it. They have provided a good labs also and good videos also for reference. So I believe everything is good on that part.

I would rate the overall solution an eight out of ten. 

The product’s most valuable feature is the ability to store secret information.

Azure Key Vault has been a crucial component in securing sensitive information within our organization. It includes storing critical details such as usernames, passwords, and other confidential data.

It is a simple service. I rate the stability a nine out of ten.

The service is easy to set up. However, the process requires various details, such as access controls and permissions. It includes determining who can create, read, or modify secrets. Overall, it is relatively easy and can be efficiently deployed through templates into CI/CD pipelines and DevOps workflows.

The product is inexpensive.

The platform provides straightforward integration with most of the other Azure services. It has improved the compliance and auditing processes. Earlier, we had to either store secret information inside the application or develop a custom solution to comply with it. There was a high chance of the data getting corrupted as different people had access to it.

I rate Azure Key Vault an eight out of ten.

We integrate Azure Key Vault to Azure DevOps for configuration automation. It allows selected access to the client IDs. Centralizing these keys ensures developers don't have direct access to sensitive information. Instead, the platform management team or developers can securely retrieve these keys during the pipeline execution.

The platform has a valuable feature for seamless integration. It's integrated into Azure API Management and Azure DevOps or directly into code. It supports various environments.

Azure Key Vault takes time to fetch values while integrating it with the code written in .NET format.

We have been using Azure Key Vault for four to five years.

I have been using it for five years, and it has been a stable product.

We have more than 100 Azure Key Vault users in our organization. It is a scalable product in terms of adding keys.

The product costs much less compared to other vendors.

Azure Key Vault is easy to use. It is a best practice and must be used within architecture implementation for security. I rate it an eight out of ten.

We are using Azure Key Vault for holding secrets, such as certificates and API management. We're using it for integrating and saving secrets for web applications.

The most valuable feature of Azure Key Vault is the secret storage of data.

If multiple clouds are to be used it can be difficult and a third party should assist in the implementation.

I have been using Azure Key Vault for approximately six years.

I rate the stability of Azure Key Vault a ten out of ten.

I rate the scalability of Azure Key Vault a ten out of ten.

I have not had issues needing support.

The initial setup of Azure Key Vault was easy.

My advice to others is if they want to do a multi-cloud deployment it should be done by a third party.

I rate Azure Key Vault a nine out of ten.

We use Microsoft Azure Key Vault for the secret management side of things; that's where all our application secrets are stored.

This solution speeds up the product development life cycle. That is, the time from product development to market is drastically reduced because of the CI/CD pipelines. You can have your code deployed within a matter of minutes. The entire pipeline, unit testing, and insights, even on the mobile apps, are powerful. We can even obtain crash analytics. So the entire life cycle has been really fast. Also, it's pretty easy to develop and then deploy web services within a matter of minutes.

The DevOps pipelines and the ease with which you can deploy the code through the CI/CD pipelines have been valuable features.

Azure has great documentation, but I would like to see more use cases pertaining to specific industries. For example, case studies on how to use HIPAA compliant solutions in the healthcare industry or how to use PCI compliant data analytics solutions in the financial technology industry would be helpful.

I've been using this solution for more than five years.

I think the stability is great.

I think Microsoft Azure Key Vault is very scalable.

Technical support has been absolutely splendid.

Overall, I would rate this solution at nine, on a scale from one to ten. 

However, if you're not looking to have your application tied to one cloud provider, then you should stay away from this solution. Once you are tied to a particular cloud provider, coming out of it will be very difficult.

Our primary use case for Azure Key Vault is cloud applications that are being developed and deployed on Azure. In addition, we use it to store secrets that are used for on-premises applications.

The best feature is the integrity of the .NET applications in our company.

The big problem with Azure Key Vault is key rotation. We haven't found a good way to synchronize the credentials between the databases and Key Vault.

We have been using Microsoft Azure Key Vault for about one and a half years.

Azure Key Vault is stable. We haven't had issues with it in terms of reliability.

The scalability of Key Vault depends on how we develop applications. The technical part of integrating between the cloud and Key Vault is easy. It's more that the development of life cycle processes needs to be improved. That's one of the big problems. They have to improve it so that all projects and all servers achieve integration easily. But that's not so much an Azure Key Vault issue. It has more to do with the processes of our company.

We don't look at the number of users but, rather, what are called service principals in Azure Key Vault. We have a lot of service principal applications.

Our first step is always to try to find issues ourselves. If we can't handle an issue we escalate the request to a local Microsoft support provider. If they don't have the answer, they go directly to Microsoft.

We have been using Azure Key Vault and Centrify. We have begun a migration to CyberArk because our provider told us about a technology change and offered to migrate us from Centrify to CyberArk. We are looking to understand what CyberArk's capabilities are in comparison with Azure Key Vault. We are trying to decide which option is the best one to go with. What we have learned is that each product has particular issues that make us think that we need to keep both. The issue we have is with the rotation of databases and servers. CyberArk accomplishes it better. That's why we are trying to integrate these two solutions.

It's not complex to set up. It's easy to configure secrets.

What can be a little difficult is establishing a good design and governance of the Key Vault repositories. Sometimes it's difficult to understand if we need one key vault or multiple key vaults. Do we need a key vault instance for an environment or do we need multiple key vaults for our databases or maybe multiple key vaults for the segregation of services according to on-premises and cloud? But creating a secret and integrating an application you're going to consume the secret with is easy.

We have four operators responsible for Key Vault and CyberArk.

Azure is cheaper than CyberArk. You can configure a lot of applications with it, but the key rotation issue is there. CyberArk has good key rotation. It integrates with a lot of technologies and a lot of different types of databases. CyberArk is good, but it's quite expensive. 

Both Azure Key Vault and CyberArk are paid annually.

I would rate Azure Key Vault a seven out of 10 because of the key rotation issues. They are a big problem. The integration of the application is easy, but key rotation is not easy. It needs a lot of improvement.

From what I have seen from CyberArk in terms of services, key rotation, and its integration with technologies, it's quite good. The big problem is its pricing. I would rate CyberArk at 8.5 out of 10.

Currently, we're looking at how we're going to use it in our dev environment. We actually have another product that we're using. We're going to test out those keys for maintaining our secrets, however, we first have them in our dev and test environment before we roll it out, as another protection area.

The most valuable aspect of the product is its ability to keep our admin password accounts for keys and a lot of our high-value assets. It can manage those types of assets. So far, the product does a great job of managing keys.

The initial setup is pretty straightforward.

The stability has been very good. We've been happy with it so far.

The security on offer seems to be quite good. 

The solution offers very good preferences.

We've found the pricing to be better than our last solution.

I don't have any thoughts on areas for improvement at this time.

While the solution already does a great job of managing keys, the solution could probably look at maybe expanding more into mobile devices and endpoints.

We've been quite happy with the stability on offer. It doesn't crash or freeze. There are no bugs or glitches. It's reliable.

Right now, for our environment, we're hoping that it's scalable and it's more cost-effective than the other tools that we were using in the past. Scalability was one of the key things that we were looking at. That said, we have not attempted to scale just yet. That may be in the future.

Technical support has been helpful and responsive. If we ever run into issues we know we can reach out and they can assist us. So far, we're quite satisfied with the level of support our organization receives.

We were previously using CyberArk, which was quite costly for us. One of the reasons we are moving away from it is the overall costs involved. This solution seems ot be better in that regard. Also, this product does seem to offer better scalability.

The initial setup is not overly complex. It's pretty straightforward. 

One of the things with the initial setup is just making sure that we understood what all our assets were and what type of things we wanted to capture in that regard. Therefore, it wasn't complex at all. It's just making sure that we did a proper plan and everything at the outset, in order to move forward properly and effectively.

The deployment took us around two to three weeks. We had an implementation strategy, however, we had to have a slow roll out. The whole thing took us about two to three weeks to get everything in place and to start migrating our keys over. 

We did not use an outside consultant or implementor during the implementation. It was an internal project. We used one of our customized tools to help us out.

The solution is less costly than our old solution, CyberArk. It's actually substantially cheaper. That said, I don't have the exact pricing off-hand.

We're partners with Microsoft.

Although we just did an upgrade to the latest version, I'm not 100% sure what the current version number we are using is.

We're quite happy with the product. I would rate the solution at an eight out of ten.

We use Microsoft Azure Key Vault to store some secrets and then we use them outside in connectors in the Data Factory.

The most valuable features of Microsoft Azure Key Vault are the security and convenience of changing passwords in multiple places.

I have used Microsoft Azure Key Vault within the past 12 months.

I would rate the stability of Microsoft Azure Key Vault an eight out of ten.

We use the solution in the data science field. If there is some outage, we did not notice any prolonged outage which would affect our business significantly while working with it.

We did interact with the technical support from Microsoft and we did not have any negative experiences with them.

My advice to others is to figure out what your needs are and then start using the solution if it fits.

I rate Microsoft Azure Key Vault a nine out of ten.