Azure Key Vault Reviews

I only work with Azure Defender for Key Vault because I'm on the security team.

So, it's currently used for passwords and secrets.

It's quite easy to use. That's one very important feature.

For additional features, you can always bring your own key (BYOK) or use your own key instead of Azure Key Vault.

There's room for improvement in cross-platform compatibility.

It would be helpful if Azure Key Vault could be used with other cloud platforms besides Azure.

I have been using this solution for three to four years now. 

It's very stable.

I would give it an eight out of ten for scalability. There's room for improvement in cross-platform compatibility.

It's mainly used by administrators. There are less than 12 administrators using it.

I haven't used technical support for Azure Key Vault. However, we did use advisory services once.

We were working on a specific use case that involved blockchain technology. We wanted to know if Azure Key Vault could be used to store private keys for blockchain nodes. We spoke to Microsoft, and they were able to help us.

Positive

The initial setup is very straightforward. It only took a few minutes.

You can deploy it yourself. It's a self-service model. Just a single Azure administrator is enough.

We have definitely seen a return on investment from using Azure Key Vault. It has helped us to improve the security of our organization.

You don't need to pay for a license for Azure Key Vault. It is billed on a pay-as-you-go basis.

I would definitely recommend Azure Key Vault. It is very easy to use, especially for retrieving keys and creating secrets.

We use it to secure passwords and conceal various types of information within documents and data.

It provides a secure and centralized location for managing and protecting sensitive information, making it an essential component for enhancing the security.

While it is reliable, enhancing security and protection should always be the priority.

I would rate its stability capabilities ten out of ten.

Scalability depends on the availability mechanisms established at the data center level, specifically through the use of availability zone regions.

We have been using Cisco Secure and CyberArk. It's not a simple switch; rather, we encountered specific situations that necessitated the use of Key Vault.

The initial setup was straightforward.

It takes about an hour or less to complete the deployment internally with our in-house team.

I would advise to construct the global scenario in alignment with their specific requirements. Overall, I would rate it ten out of ten.

We use Microsoft Azure Key Vault to store encrypted credentials.

One of the most valuable features of Microsoft Azure Key Vault is its ease of use.

Microsoft Azure Key Vault could improve by enhancing the security of credentials. Without the security or the use of key vaults, we would have to configure our credentials into the source code as plain text without the encryption or security.

I have been using Microsoft Azure Key Vault for approximately seven months.

I didn't explore scalability very much, I had limited configurations with Microsoft Azure Key Vault. In the future, if I need to add a few more properties I could do it within the scale.

I used the Microsoft support that they have online at MSDN. I found most of the requirements and answers to my questions needed.

I have not used other solutions previously.

The initial setup of Microsoft Azure Key Vault was easy. The time it took for the implementation was appropriately one hour.

The solution does not require maintenance, there is no maintenance team needed.

The solution is simple to use, but there are now many more wallets that are available in the market. I haven't explored other solutions. I would advise others to look at other solutions to have an overview of what features the others are providing before choosing.

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

We are working with a lot of our clients who use the solution to protect sensitive information and to store it in the key vault within their infrastructure.

The sensitivity of the data needed to be kept in a secure environment so that only people who had proper access would be authorized to access it.

We are using infrastructure as code. So any of the services which require sensitive data can directly use service principles, manage identities, and access key items and then retrieve information from the Key Vault.

Since we are partners of Microsoft, we don't implement it for ourselves. We implement it for our clients. For our clients, many were using on-premises solutions and had connectivity from on-premises to the cloud. With this solution, they get the same level of data protection (or more) on the cloud.

The features on offer are very good.

We are using Key Vault as an optical store for the sensitive data and then retrieve the data and use access policies. So access to policies is quite valuable for us based on the regulations and compliance requirements that we are working with.

There is advanced data protection available. We're working in a highly regulated environment, and this is essential to us.

Perforamnce-wise, it's very good. We haven't had any issues in the past three years. There are no errors or downtime. It's always been available to us.

Microsoft's Key Vault availability is around 99%.

A lot of new features have been added, and it has nice regional availability as well. 

It is stable and scales well.

Technical support has been fine overall. 

It's currently very self-sufficient and doesn't need improvements. It's already a good service. 

We haven't faced any problems with the solution as such. The only issue we are facing is around the comparability with TerraForm, which we use to code the infrastructure. Sometimes there are issues there, even though it's not directly related to Microsoft. 

So far, it's served all of the client's purposes. We haven't come across a use case the solution could not handle. 

There are additional charges for data transfers. However, the pricing is mostly reasonable for the licensing overall. 

I've used the solution for three or four years at this point. I've used it for a while. 

The solution is quite stable. There are no bugs or glitches, and it doesn't crash.

We have 60 different teams that deploy their own Key Vault. They are purely developers that make applications for users. Those users may be from anywhere and may use the application portals.

I'm not sure, behind the scenes, what Microsoft does. However, I've found it to be scalable across regions. If we wanted to use 100 Key Vaults, we could do so.

We do not have plans to increase usage at this time.

Technical support is pretty good. I haven't had any issues with them over the past three years. 

Neutral

The client has used other on-premises versions in the past. Many needed a cloud option, and we helped them move to Key Vault. 

The initial setup was straightforward. We do not deploy it as it is a SaaS. We simply configure it for clients. There are APIs available, and we use them within Key Vault to implement.

We require the business use case and strategy in order to implement the product. For example, if we are in energy or health care, we need to know what is the area that is sensitive and where they are being used. Then, once we have that, we can protect those items.

The only maintenance that is required is service access. For example, if we need to add authorized personnel, we would do that. 

We can handle the implementation for clients. 

The cost is quite cheap. There are no extra costs beyond the standard fees, beyond maybe data transfer charges. It's $0.025 per 10,000 data transactions, so it is quite cheap.

We are a partner of Microsoft.

We haven't exported or imported information in Key Vault.

This solution is worth the cost and is useful to use. 

It's a service that can be used in multiple regions in Azure. They are mostly deployed in UK South and UK West. It can be deployed and used in other regions as well; however, we have data constraints. 

I'd rate her solution eight out of ten overall. 

Potential new users should consider the types of sensitive information they want to store and how they want to retrieve the information, and from where. These are critical to understanding as they will govern the configuration of Key Vault.

You can deploy Key Vault both publicly and privately. For example, if you do it privately, you can ensure you will ensure it can only be accessed from within your environment, and that ensures a very high level of security.

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.

I use the solution in my company to store secrets and certificates.

The most valuable feature of the solution in our company stems from the fact that it is easy to integrate with our codes. The support and SLAs provided by Microsoft for Azure Key Vault are good. The aforementioned areas consist of some of the basic advantages of Azure Key Vault. Azure Key Vault is nice to store the secrets of in a concealed manner.

One of the drawbacks I think is the single-point failure of our products. If the region where the Azure Key Vault data center is hosted goes down, it would be a cumbersome task since our company will have to come up with a different Azure Key Vault and migrate all the secrets or keys into it. Basically, improvements are required in the product to deal with disaster scenarios. Maybe there are some ways to deal with the solution's issues about which our company might not have researched thoroughly.

I have been using Azure Key Vault for 2-3 years. My company is a customer of Microsoft.

Stability-wise, I rate the solution an eight to nine out of ten.

It is a scalable solution. Scalability-wise, I rate the solution as seven out of ten.

Around 500 people in my company use the product.

I rate the technical support an eight out of ten.

Positive

The PoC phase of Microsoft Defender is in the pipeline.

I rate the product's initial setup process as an eight on a scale of one to ten, where ten means it is a very easy phase.

I have not faced any issues during the product's installation and configuration processes.

Considering the features provided by the product, I would say that the solution is available at a good price point.

The payment is made as a whole for all the Microsoft products used in our companies. I don't remember the exact price of Azure Key Vault. The product is affordable, in my opinion.

The most beneficial component related to cryptographic graphic key management stems from the auto-rotation functionality.

The product comes with two types of access policies. The tool provides a conventional policy and Azure RBAC. My company mostly, you say, the conventional access policy and it has been working great so far.

The product plays a crucial role in our company's security strategy.

The product is easy to maintain.

The product helps ensure compliance with our industry regulations since it meets most of the auditing and compliance rules. It is a secure solution that needs to have most of the policies and compliance rules. I would say that Azure Key Vault is a good solution, considering the security part.

I rate the overall tool a nine 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 Azure Key Vault to encrypt and to get our secrets such as passwords and connection strings.

The use of Azure Key Vault is vital to the security of our organization. Here we store our credentials, secrets, tokens, connection strings, and any other information needed to access external services and cloud providers. This service is essential to ensure a high level of security for our company.

The most valuable feature of the solution is the search for secrets feature that we use to store our passwords and connection strings. I also like objects such as keys and certificates.

Azure Key Vault is simpler to use compared to other certificate or password managers such as HashiCorp Vault and ManageEngine Password Manager Pro.

We can currently configure RBAC, Azure role-based access control, or a voucher access policy. The voucher access policy can be improved by configuring it based on groups, rather than just applications or users.

I have been using the solution for three years.

The solution is extremely stable. We have not had any issues or downtime with Azure Key Vault.

The solution is scalable and always responds to our demands.

We currently have around 500 people in our organization using the solution.

The technical support team is good and they provided satisfactory results.

Positive

The initial setup is straightforward. The deployment takes two to three minutes.

The implementation was completed in-house.

We have seen a return on investment for our organization with Azure Key Vault because of its low price and security. 

Compared to other solutions, Azure Key Vault is much cheaper. 

I give the price of the solution a ten out of ten.

I give the solution a ten out of ten.

The solution is self-maintaining. We have implemented EIS, and infra as a code, and incorporated a CI/CD process to automate the maintenance in our environment.

I always recommend going to Microsoft Learn for its rich knowledge base. Azure Key Vault is an excellent solution for improving organizational security, and it offers great value for money.