Azure Key Vault Reviews

We use the solution for a lending platform in the BFSI domain. It helps to store secrets. 

Azure Key Vault's performance is excellent. It makes infrastructure management easier. 

The solution needs to improve reliability and protection. 

I have been working with the product for three years. 

Azure Key Vault is stable.

The product is scalable. 

Microsoft's support is good. 

The tool's deployment is straightforward. 

Azure Key Vault is expensive. 

I rate Azure Key Vault an eight out of ten. 

Users can store all the security credentials in Azure Key Vault, which only authorized users can access.

Azure Key Vault allows only identified users to get the credentials and rotates the keys automatically.

The solution's usage can be a little better from the user interface point of view. Azure Key Vault is a little complex from the usage point of view, and users should be able to use it in a much simpler way.

I have been using Azure Key Vault for two years.

Azure Key Vault is a highly stable solution.

Azure Key Vault is a highly scalable solution. Our clients for Azure Key Vault are mostly medium-sized businesses.

I rate Azure Key Vault an eight or nine out of ten for scalability.

Azure Key Vault’s technical support is very good.

Positive

I rate Azure Key Vault a four or five out of ten for the ease of its initial setup.

Azure Key Vault's deployment doesn't take much time and can be done in a few minutes.

Azure Key Vault is an affordable solution. On a scale from one to ten, where one is cheap, and ten is expensive, I rate Azure Key Vault's pricing a three out of ten.

I am working with the latest version of Azure Key Vault. I would recommend Azure Key Vault to other users because it is scaling up and getting better than other cloud solutions.

Overall, I rate Azure Key Vault an eight out of ten.

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 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 use Azure Key Vault to store all of our applications’ keys and secrets in the Azure platform. The secrets and keys are for our public facing SaaS software which mainly includes websites and APIs.

The solution has reduced the amount of time that we had spent worrying about the management of the keys and secrets.

I find the simplicity of key management to be the most valuable feature. Key management has always been a difficult function to do, especially in the cloud premises. Azure Key Vault provides you with a mechanism for managing keys, without having to worry about protecting secrets, and that is valuable.

I have been using this solution for about five years.

I would rate the stability of the solution as eight out of ten. We encountered a few problems where Azure had infrastructure problems like the DMS. It was not necessarily a problem with the Key Vault but a problem with the infrastructure that did not allow us to access it.

I would give a rating of ten out of ten for the scalability of the solution. I have not found any scalability issues with Azure Key Vault.

I have found the customer service and support of Microsoft to be very good and very high.

Positive

We haven’t used any different solution before Azure Key Vault. We have used it since initially implementing it in the cloud.

The initial deployment was straightforward. I was involved in the deployment of the solution in a project management role.

We implemented the solution with the help of an in-house team. There was only one team member doing the deployment.

We have seen ROI with the solution. We observed reduced internal development effort with the use of the tool. The solution was certainly worth the cost.

I find the pricing of Azure Key Vault to be reasonable.

We did not evaluate any other options because we were fully on the Microsoft platform, so we went ahead with their recommendation.

I would rate Azure Key Vault a nine out of ten. I recommend it as a good solution for those using Azure Cloud to host their services. The solution does not require any maintenance.

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 primarily use the solution to secure our DevOps processes and store all the essential secrets for our project's services.

The integration with other Azure services is one of the standout features for me. It allows us to use secrets from the Azure Key Vault seamlessly without direct interaction.Additionally, the ability to easily mark secrets for expiration and receive notifications is invaluable.

One area for improvement is the notification system for secret expiration. It would be beneficial if the service could handle this more autonomously, eliminating the need for additional integrations.

I have been using Azure Key Vault for about three years. 

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

I rate Azure Key Vault's scalability an eight out of ten. My company has more than 50 users. We use it daily. 

I rate the tool's deployment an eight out of ten. It takes less than a minute to complete. You need two resources to handle it; no maintenance is involved since it is a managed service. 

I rate the solution's pricing a four out of ten. 

I rate the tool an eight out of ten. 

We use Azure Key Vault to store secrets. 

The solution needs to improve its cost. 

I have been using the solution for five years. 

I rate Azure Key Vault's stability a ten out of ten. 

The product's scalability is perfect. My company has around 100-200 users for the solution. 

The tool's installation is straightforward. 

We did the solution's deployment in-house. 

I rate the tool a ten out of ten. 

We use the solution to authenticate security features for environments. Using it, we can encrypt keys and protect the databases from getting hacked.

The solution works as an effective tool for securing our organization's databases.

They should add a key vault feature for the databases temporarily integrated into hybrid clouds. Also, they should make the key accessible once the databases migrate to another environment.

We have been using the solution for seven years.

The solution's customer service is excellent.

Positive

The solution's initial setup process is moderately complex. It is a time-consuming process if you are new to the product. But, if you know source applications and target databases, it just takes a few hours. Whereas in the case of larger environments, it might take days to complete.

Our in-house team deploys the solution. It requires three executives to work on larger deployments. Also, it requires a huge team when there are multiple databases to work with. 

The solution is affordable compared to other competitors.

I advise others to use the solution if they already work with Microsoft Azure environment. In such cases, they should not prefer integration with a third-party tool. They should consider other products if the databases are distributed to on-cloud and on-premises infrastructures.

I rate the solution as an eight.