Azure Key Vault Reviews

I use the solution for saving keys. We use it to manage encryption keys and secrets in our applications.

It is a good solution. I use it to deploy my services. All the features are valuable. The access policy feature helps secure content and resources. We use the automated key rotation feature to secure the deployments and the development process. It can be used to secure resources. The availability is high. We can integrate the tool with VMs, storage, and Azure App Service.

The product must provide AI features.

I have been using the solution for three to four years.

The tool has high stability.

The tool’s scalability is high. Our clients are small, medium, and enterprise businesses.

The support must be improved.

Positive

The initial setup is easy. The deployment took a few minutes.

The pricing is normal. The product is neither cheap nor expensive.

I am an implementer and designer. I will recommend the product to others to keep keys, secrets, and related information secure. Overall, I rate the product a ten 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 primarily use the solution for key management.

The access policies are the solution's most valuable aspect.

The solution is very stable.

The scalability is very good.

The pricing of the product is reasonable.

Technical support is helpful.

The rotation of key needs improvement. It needs to offer dynamic secrets management.

I've been using the solution for about a year or so. It hasn't been that long.

The solution is very stable. It doesn't crash or freeze. There are no bugs or glitches. It's reliable. 

The solution can scale well. It's not a problem at all. If a company needs to expand it, it can.

Our clients tend to be enterprises, and aren't overly small. 

You do need a support agreement, however, from what I have seen, it's quite reliable and knowledgeable. It's easy to reach them and to work with them.

The initial setup has a moderate amount of difficulty. It's neither extremely straightforward nor overly difficult.

You do need a special agreement in order to receive technical support.

While I don't directly deal with pricing, my understanding is that it's okay, and not too expensive.

We are currently looking at other solutions in order to compare them. We are also using HashiCorp Terraform and looking into HashiCorp Vault.

We are just a customer and an end-users. We tend to use the solution for our clients.

For those companies that want to work with the solution, I'd advise that they consider the use of and integration with Azure's pipeline.

Overall, I'd rate the solution at an eight out of ten. We've largely been quite happy with its capabilities.

I am a system architect and this is one of the products that I work with when designing systems for our customers. This key vault allows you to store passwords and secret keys so that you can retrieve them when needed. Each customer will have their own secret password that can be used in a cloud-based scenario to retrieve their login usernames, passwords, and other secrets.

The most valuable feature is that you can retrieve user account details from the cloud.

Azure needs to provide versions of Key Vault that are suitable for different sizes of companies. For example, we are not a big corporation that can afford corporate-level pricing. We have to strike a balance between the number of users and the volume of keys that are being used.

I have been using the Microsoft Azure Key Vault for close to two years.

This is a stable product and I haven't had any issues. The performance decreases as many keys are added to the vault. For example, it will be slow if we have 1,000 users.

Scalability is related to the licensing plan. At some point, the number of keys that can be stored will run out until the vault plan is upgraded.

The product support is awesome and I don't have any issues with it.

Azure is the first key vault that we have used.

The initial setup is straightforward. It is not complex, although it takes weeks to implement because we have to integrate with other modules.

Our in-house team handles deployment.

The cost of the Azure Key Vault is very high and the pricing model is based on the number of keys that you store and retrieve. It is billed in blocks, such as 1,000 passwords that I can store. However, if I am paying to store information for 1,000 users then the pricing is not discounted if I only need to store 500.

I am currently evaluating HashiCorp Vault because it is more economical than Azure Key Vault.

In summary, this is a good product and one that I recommend.

I would rate this solution an eight out of ten.

We have an application connecting to the database. So we have implemented an authentication in place wherein without that particular secret value, it won't be authenticated. So that is a use case that I can tell you about Azure Key. We have implemented it for some small identity providers as well. 

Using Azure key Vault has increased the security of our organization. 

I would say its granular access control is the most valuable feature.

It would be great if it would integrate with other cloud solutions.

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

I think the stability works perfectly. I've never seen a block from the cloud side. But there might be some problems when we are configuring it. So maybe we are missing some strings or something, but I have never seen an issue from the cloud side.

A thousand people using the solution at present.

You have to configure based on, like, who should access routers, security should be generated, the identity management and everything. And Azure Microsoft people have provided a good documentation on it. They have provided a good labs also and good videos also for reference. So I believe everything is good on that part.

I would rate the overall solution an eight out of ten. 

The product’s most valuable feature is the ability to store secret information.

Azure Key Vault has been a crucial component in securing sensitive information within our organization. It includes storing critical details such as usernames, passwords, and other confidential data.

It is a simple service. I rate the stability a nine out of ten.

The service is easy to set up. However, the process requires various details, such as access controls and permissions. It includes determining who can create, read, or modify secrets. Overall, it is relatively easy and can be efficiently deployed through templates into CI/CD pipelines and DevOps workflows.

The product is inexpensive.

The platform provides straightforward integration with most of the other Azure services. It has improved the compliance and auditing processes. Earlier, we had to either store secret information inside the application or develop a custom solution to comply with it. There was a high chance of the data getting corrupted as different people had access to it.

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