Azure Key Vault Reviews

I have used the solution on a couple of projects for a client, mainly for storing credentials and secrets, such as API keys and application or username passwords into the vault, as well as certificates. 

It is used for anything we need to keep safe and secure and not have users access, except via applications that programmatically access Key Vault and retrieve the secrets and connect to other APIs. That way, we don't supply usernames and passwords within application code or to people. We vault them in Key Vault and those secrets can be used within an application without human intervention.

Azure Key Vault is a SaaS solution.

You have to have this to make sure that you're compliant with security and governance. One of the main concerns with compliance is how you manage keys and secrets in your cloud environments. You're encrypting your data at rest and in transit, but where do you store the encryption key itself to not become compromised? Key Vault addresses all those concerns. This is one of the main tools and, without it, it's hard to implement and address one of the main pillars of cloud architecture, which is security.

The whole nature of it is to help make things autonomous, because you can run infrastructure as code. That really takes away the human factor and you can fully automate the creation and management of, and access to, the keys, including the rotation of the keys. By taking away the human element, it's really secure. And, implementation-wise, when you're using Key Vault, Microsoft is behind it and they're using the best methods for encryption and ciphering of keys. You don't have to worry about those things.

It really simplifies the whole process, in contrast to needing in-house experts to help you facilitate key management. When it comes to two main concerns, encryption of the data in transit and at rest, it is a service that is with you all the time. It has a low cost and it's ready to implement. You don't have to have 10 developers build something that you don't even know will be successful, versus a service that has already been tested across global enterprise companies.

All its features are really valuable. It's really well thought-out. It's a complete turnkey solution that has all the concerns taken care of, such as access control and management. You can use it in infrastructure as code to create key vaults, APIs, PowerShells, CLIs, even Terraform.

You can also use it in different services across the board. If you have app services, or virtual machines, Kubernetes, or Databricks, they can all use Key Vault effectively. In my opinion, in a DevSecOps, DevOps, or even in a modern Azure implementation, you have to use Azure Key Vault to make sure you're addressing security and identity management concerns. By "identity" I mean usernames, passwords, cryptography, et cetera. 

It's also a regional solution and it frees you up from using third parties like HashiCorp Vault, for example.

In addition, there is a feature in Azure called managed identities, and when storing your credential or any keys or secrets in that you can have your code use managed identities to access Key Vault. That simplifies the whole process of connecting to Key Vault and retrieving your secrets, passwords, and credentials. 

It's a full-blown solution and it supports most breeds of key management: how you store keys and certify. 

I can't say that one of its features is better than others. You have to have all of them to make it a competent service, although one of the especially important features is the connection with monitoring and logging, so you can see who had access to what.

If you check the capabilities of other key management services across Amazon, HashiCorp, and Google, there are features that Key Vault doesn't have. It could be the case that when you use Key Vault, you might be forced to use a third-party solution to get certain services. If those services could be included in Key Vault, there would be diminished reasons to go for a third-party key management system.

I was using Microsoft Azure Key Vault until two years ago, but since then I've been actively using it for two or three different projects.

It's stable. There is the SLA and the resiliency that goes with Azure. Because many services are dependent on Key Vault, if it's highly available and redundant, it helps a lot. You can imagine how many times applications would go down if Key Vault were not available. It is one of the high-demand services. Anything that needs to access a key or a certification is dependent on Azure Key Vault. 

So far, compared to other services that are available in the Azure environment, I haven't seen anything surprising with the stability or availability of Key Vault.

It's scalable and global in its performance. I have implemented it for one of the largest pharmaceutical companies in the whole world, a company that operates on a global scale. Key Vault is a main ingredient for every one of their infrastructure pieces that is tied to it. The scale of that company in its use of Key Vault was phenomenal.

I haven't needed to contact Microsoft support about Key Vault. There have been instances when I have had to talk with Microsoft support about Graph API for Active Directory and other services, and even to the cloud adoption framework team, but never for Key Vault. It is just so straightforward.

The complexity depends on what you're trying to do with Key Vault. It can get complex or it can be simple. You don't expect advanced scenarios to be easy to implement because it has many ingredients. If someone is simply going to Azure portal to create a secret and retrieve it, it's simple. But if you want to tie in your services, and have role-based control over who can access keys, and what services are tied to the keys, it gets complicated. But that's not just Azure. That complexity comes with the level of complexity of the scenario.

Key Vault is easy to use because there are many APIs and mechanisms to create and retrieve. The concepts are easy. I use it in many scenarios, such as building infrastructure as code, consuming it in Kubernetes. Everything seems to be straightforward. It is really the de facto for key management and vaulting secrets. 

For example, one of the applications recently we developed needed to store the username and password of the service that connects to SQL Server. I found it was super-easy to tie the credentials within the application configuration files to Key Vault to retrieve the keys. It was a no-brainer for a developer to learn and do it. It took about 15 to 30 minutes to follow the documentation. And it has really nice documentation. Performing any action using the features of Key Vault is really easy as it's user-friendly. Depending on your level of skill, the deeper you get, the more features you can use.

Key Vault, like every Azure service, has a cost associated with it, but you don't have to spend thousands of dollars to spin up an environment to build a key management system. It's already there.

You pay as you go, similar to other services in Azure.

There are many other tools that I am still using, including AWS Secrets Manager, CyberArk, and Conjur, but none of them is close to Key Vault.

One of the benefits of Azure Key Vault is its integration with Active Directory, as is the case with most of the services in Azure. That really adds something to all the services.

Also, Managed HSM is not available in those other solutions. You have to go with HashiCorp Vault to get that. 

In addition, the key rotation feature of Key Vault is a lot better than in AWS Secrets Manager. CyberArk and Conjur, are more one-off products for specific use cases. You have to purchase a license and implement and manage them yourself, and not everything works seamlessly in CyberArk.

Conjur was good until Key Vault supported containerization. Azure created services for using blob storage, and those features of Key Vault came naturally as part of the whole cloud stack. 

Key Vault covers different problems for various personas and roles. As a developer, you get a lot of benefits that you don't get when you start developing with other tools, excluding HashiCorp Vault. HashiCorp Vault is really neat, and the only downside is that you have to manage the infrastructure yourself.

I'm a cloud architect. If I don't see that Key Vault has been included in a proposed architecture, I don't approve it. It's a main ingredient in any cloud enterprise infrastructure and architecture. When you're using Azure, you have to have this or a third-party solution. If someone shows me a third-party solution, I have to ask, "What's the cost of owning this component that you're adding to the architecture? Is it included, like Key Vault, or do you have to pay for it like with HashiCorp Vault?" With Azure Key Vault you have something that is free, enterprise-level, global, and it just works.

I don't know if we could survive without Key Vault in a cloud implementation and still call it a secure platform. These days, you have to have Azure Key Vault or some third-party mechanism such as HashiCorp Vault. You need something that addresses key management in your cloud environment. But why should you pay for extra resources, costs, and management overhead, if everything is managed by Azure itself?

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 will likely use Microsoft Azure Key Vault for secure key management.

Provide a central, secure repository for keys.

It is a managed service in Azure, you do not have to worry about security other than the access. The vaults themselves are inherently secure.

It's too early for me to say with certainty, but what I'm seeing thus far is that Key Vault at face value is more of a secure store than it is a password manager. I suspect that we may be able to use logic apps to perform some actions that a password manager would, but a little more focus in this area would be beneficial.   

I have been using Microsoft Azure Key Vault for one day.

We have approximately 15 users using the solution in my organization.

The setup of my test files has been easy and the documentation is straightforward.

I handle the implementation of the solution.

The price of the solution is reasonable for what we are using it for.

We did not have a great solution in the past. We wanted something better, and everything that I read about Microsoft Azure Key Vault was good. We did evaluate other solutions but we were already using Azure for other things, it made sense to implement Microsoft Azure Key Vault.

Other people's opinions of Microsoft Azure Key Vault seem to be quite good.

I rate Microsoft Azure Key Vault an eight 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 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.

The product integrates well with Azure Active Directory to manage identity or secret certificates.

Azure Key Vault's most valuable feature is its ability to store security certificates securely. It allows me to run applications using these certificates without directly installing them.

The platform's configuration process could be easier. Most of the new technologies involve certain prerequisites and complex setup processes.

I have been using Azure Key Vault for a long time.

I rate the product's stability a nine out of ten.

The product's scaling process is complex for users who are not familiar with its concept. It is suitable for small to enterprise businesses. 

I rate the scalability an eight out of ten.

The initial setup process takes 15 minutes to complete for me as I have prior experience working with it. The non-proficient users need professional assistance. In most cases, they need to be notified about the necessity of authenticating the user ID and password.

The product has good pricing.

I recommend Azure Key Vault to others and rate it 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."