Azure Key Vault Reviews

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

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. 

We use the solution to secure and store managed sensitive information and cryptographic keys in an application secret.

The solution uses the encryption technique to store the secret information data that uses EPCE. There is also one feature that monitors Azure Key Vault.

They should improve its policies, which sometimes reapplied but don't sync properly between the Key vault and the role-based access. When I put some roles on the user side, it sometimes misses the end data to secure.

One feature that could be added is the transparency of Key stored. There could be a feature to monitor the Key Vault because we can't monitor the Key Vault with a third party. We can't configure the automation or sync the key vault. We store passwords and all those things.

The user intervention also needs to be implemented there. This allows the user to automatically change the password, ensuring that it synchronizes and updates across all stored keys.

I have been using Azure Key Vault for two years.

The product is stable.

The solution is scalable. If they improve certain things with the update, that will be a more scalable product. There are a lot of users that use the Key Vault because it is the organization’s choice.

The initial setup is super easy.

There is a key that says, 'MS bug is there.' Azure has keyword secret information and connectivity issues. Azure File Share has Key connectivity issues. If we share some files and link through the Key, it loses connection.

The product is expensive compared to other products. It is costly to install as data records are charged based on the data. The Key type and plans are the factors that affect the pricing.

We are implementing Azure Key for certain projects. It completely depends on the project. Suppose your company gives us a project and asks us to implement Azure Key for other users.

I don't recommend it to everyone. It completely depends on the scenario base if you use a VM application or shared data. You can use Key Vault to secure information when transferring over the network. Sometimes, you are trying to assess your web information, and it is not working because of the connectivity issue due to some access control policies.

If you are the user and can work on the Azure portal or have access, you may be the support or IT person. You have the right to choose the architecture we must implement in our organization. They want to implement that on their user, but that's not a suitable option for everyone. We have 2,000 employees using this solution. We should have a strong plan to implement the Key Vault.

Anyone can learn Azure Key Vault within a day or two days.

There's a lot of work to do on the standalone side. If we are required to create a different workflow or automate it, then it's not possible or difficult to do that. If I want to keep the alerts on my email or team channel, that isn't easy to automate with the help of the Sentinel.

I need to use Azure Key Vault to ensure my application sends me refined data weekly. This data includes high and low alerts, which are sent to my email address or possibly generate an incident using a third-party API such as ServiceNow or Jira.

We can automate several things. We can fetch the log, but we can't automate that defender workflow itself in Container.

The solution is best because it completely secures passwords, which we can use to access.

Overall, I rate the solution an eight out of ten.

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. 

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

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.