Azure Key Vault Reviews

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 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 it for storing secrets for different accounts. If a service account or a storage account or a resource needs access to a resource, and there's a password involved, you would book out a password, and access Key Vault to gain access to the password, and get access to the resource.

The ability to use identity access management incorporated with RBAC is important for us. It helps us ensure the governance and security posture is secure and logical.

Among the features that have helped improve our security posture are storing secrets in a secure location to create a trusted situation, trusted resources, and incorporating identity access management so that we know who has access to what.

In addition, it hasn't affected our end-user experience. It's seamless.

One of my previous clients was one of the big banks here in the Netherlands and the EU courts have stated that Microsoft Azure Key Vault is not, according to their perspective, secure due to the fact that Microsoft has access to Key Vault. If you cannot demonstrate that only you, as an organization, have access to your secrets, then you are not in control of your secrets. That is a concern.

Also, a big issue is the configuration. It could be that the people working on the solution, the system engineers, might lack knowledge and not incorporate all the best practices from Microsoft. The way they've implemented it might not be the way Microsoft envisioned it. It's always back to who's implementing what for you as a solution.

We've been using Microsoft Azure Key Vault for two to three years.

It's robust. It's good.

The scalability is very good. It's up to your imagination and how big you want to make your resilience and high availability and so on.

We have plans to increase our usage because we are going to launch new websites for specific regions. There will just be more resources needed.

Microsoft has a support team that calls our security team every two weeks to discuss any topics and issues, and to talk about topics of the day or the week. It might be about resilience or expansion or features that are changing and new releases. It's good to have a meeting at least every two weeks that gives us the opportunity to speak to Microsoft account management.

Positive

The initial setup was straightforward. It's already incorporated in Azure, so you can just use it. It took minutes to deploy.

The ROI is due to the fact the services keep on growing. It's better, it's more secure, and it grows. It's becoming a better product.

Our customer did not evaluate other products. They mostly want to do things native to Microsoft Azure, so that's their first port of call. And if Azure services cannot provide the functionality that they need, then they will go and look outside.

Other service providers try to lower the prices, but it all depends on your development environment and your core skills. You are a bit more stuck if you are coding in .NET. If you go down that route, you can't easily move out to another service provider. Maybe you can go the route of adding a new team with a different service provider, but then you will need to mash it together. You would need to evaluate if that is a good option.

We have about 70 developers and they are in different teams. They interact with third parties and they have different roles, including front-end and back-end developers. Each one creates services for different websites for different regions, to sell e-vape cigarettes. And we have team leaders who use it as well. There's a security team of five people responsible for the infrastructure of Azure, including creating new resources or whatever is necessary for the dev teams. There are also operations management and product owners who make decisions on schedules, what will be built, and priorities.

Deployment and maintenance are part of the security engineers' work, to manage any issues. Sometimes the dev teams get involved with root cause analysis if something is going wrong with a web application. We have a team for certain maintenance tasks and requests.

The biggest lesson I've learned from using this solution is: "Stay secure."

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.

We use it to store our secrets and passwords for our integrations and applications.

We only use the basic features and those are the ones that have the ability to tie into the app, the secrets, and the passwords and encrypt them.

So far we've had good luck with it. We haven't had any bad experiences. Once we got it set up and we got it injected into our code, we've had pretty good success.

I have been using Microsoft Azure Key Vault for around a year and a half. 

We have about 225 applications that are using it.

Their technical support was good when we used them.

Positive

We did not use a different solution. This is our first time using the services.

The initial setup was pretty straightforward. 

I thought the price was reasonable. 

My advice would be to definitely leverage your premier support to help you get it going. Once you get going on it, it's fairly simple to use.

I would rate it an eight out of ten. 

To make it a ten the setup should be more streamlined.

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.

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.

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 this product to manage our keys for storage, as well as the SQL server.

The most valuable features are ease of use and enabling our clients to manage keys.

The initial setup could be less complex for first-time users.

We have been working with Microsoft Azure Key Vault for about a year.

This product has been very stable for us.

Scalability does not apply to our use case. I can say that it works well for smaller organizations.

Microsoft technical support has been very responsive and good.

Prior to the Azure Key Vault, we used a third-party password value. We moved to satisfy our customer requirements.

The first time we implemented this solution it was a little complex but as you use it, the process becomes easier. Installation specifics depend on each organization's needs.

The deployment, initially, was a couple of hours. After that, it took perhaps another hour to work through the setup and documentation.

We have admins who are in charge of using the Key Vault.

I would rate this solution a ten out of ten.

There are currently two people in my team using this solution. I'm an associate consultant. 

This is a very user friendly solution and the security level is very high.

The solution could be improved by making it accessible to more people. 
The most significant additional feature I'd like to see would be the ability to access the system on the phone via my Microsoft login and to be able to manage the desktop file folders that way. That's something I look forward to. 

I've been using this solution for six months. 

It's a stable solution. 

It's a scalable solution. 

I'm satisfied with the technical support. 

The initial setup took less than 10 minutes. 

I recommend this solution and would rate it an eight out of 10.