Azure Key Vault Reviews

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. 

I use Azure Key Vault to securely store and manage my API keys, passwords, and certificates. It allows me to store them securely and share access without revealing the secrets. Azure Key Vault also automates password rotation every sixty days and offers options for managing keys either by me or by Azure.

Azure Key Vault securely stores passwords and secrets, eliminating the need to share them. Instead, access can be provided to users who log in with their own credentials. Integration with Azure services and third-party applications is seamless, as it's readily available and requires no specific deployment. Automatic retrieval of keys and certificates simplifies usage across different platforms. Overall, Azure Key Vault offers efficient key storage and management with easy integration across various services and applications.              

Azure Key Vault is very affordable, with charges of less than a dollar for over ten thousand keys. Microsoft regularly updates and upgrades the service, offering a user-friendly interface and robust security features, including AES 256 encryption.

Overall, I haven't identified any significant areas for improvement as Azure Key Vault already offers comprehensive functionality and security.

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

I'd rate the stability of Azure Key Vault as a nine out of ten. While it's very reliable, there's always room for improvement.

Scalability isn't a concern for Azure Key Vault as it's primarily for storing keys and certificates. There's no specific limit to the number of keys you can store. Our company has around seven thousand users utilizing the product.

Support from Microsoft is available, though I haven't personally used it. 

Positive

Setting up Azure Key Vault is straightforward and safe, taking about ten to fifteen minutes.There's no need for additional worry or complex deployment steps. It's a pre-deployed service on Azure, so you just need to subscribe and start using it.

For deployment and maintenance of Azure Key Vault, you typically need a technical architect and an engineer, possibly a product manager.

Azure Key Vault plays a crucial role in ensuring compliance with regulatory and governance policies by securely managing secrets and limiting access to only necessary personnel. For example, Azure Key Vault allows us to implement robust access control policies, such as distinguishing between administrative access and application-to-database communication. This helps maintain a clear separation of duties and enhances overall security.

It is a cheap option.

For those considering Azure Key Vault, I highly recommend it for consolidating and managing security assets in one place. Integration with various enterprise applications is already robust. Updates are frequent and timely, addressing any identified bugs promptly. Overall, Azure Key Vault meets our needs effectively. I rated it as nine instead of ten because there's always room for improvement in any product, including Azure Key Vault. While it's reliable, there may be areas where enhancements can be made based on customer feedback and experiences.

We use the solution to store all our passwords. We have all our important information in one place.

Key management is very easy and simple. We need not look for a different solution. It is available to us by default through Microsoft. The tool is highly secure and very easy to manage. We can integrate the product seamlessly.

The users must be allowed to customize the tool. The internal and external passwords must be separate. Users should be able to segregate the passwords.

I have been using the solution for almost four years.

The solution is stable.

The solution is scalable. Almost 2000 to 3000 people are using the product in my organization. We have two administrators.

We are partners with Microsoft. We get good support. We do not have any issues.

We started using the product because we used other Microsoft products and needed a one-stop solution for our key information. We were using the on-premise solution before.

The product is deployed on the cloud. The initial setup is very easy. We can deploy the tool within a week.

Overall, I rate the product a nine 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.

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.

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.

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