Microsoft Azure Block Storage Reviews

We use it for high-speed data and a very critical mission.

Block storage is typically used when you have structured data. For example, RDP systems like SQL Oracle and the SQL DB tool. If you have structured data, you need Microsoft Azure Block Storage.

The solution should also support unstructured data. There is a different file format for unstructured data. It would also be good if the solution notification features.

We have been using this solution for three years. Microsoft Azure Block Storage is deployed as per the requirement. It can be deployed independently and supports every kind of deployment.

It is very stable, and I rate the stability an eight out of ten.

It is scalable, and I rate the scalability an eight out of ten.

The technical support is very good.

The setup is not as simple as File Storage, and it requires a lot of investment because block storage requires a high-speed network, and you have to deploy a lot of fibre cables. It is also costly and not cheap compared to Internet-based networks. So the initial investment cost for deploying the block storage is very expensive.

The price depends on the requirement. If the data is critical, you must deploy block storage. But if it is not that critical, you can choose cheaper storage options. I rate the pricing for Microsoft Azure Block Storage a two out of ten.

Multiple vendors offer good block storage solutions, such as BMC Storage, NetApp Storage, Azure, Google and Oracle. Microsoft Azure Block Storage is deployed for mission-critical and business-critical data. When deploying these kinds of data, you must have a data center to control moving the data and allow multiple storages. You can know where the data is stored, which software controls the data, and who manages your data. But for cloud, the customer does not have any visibility or know who is responsible for managing data or whether it's secured. Therefore, transparency, control and storage deployment is significant.

I rate this solution an eight out of ten, and I would recommend this to others.

We're mainly using this solution for cloud container data and backup data. 

It's deployed on a hybrid cloud.

There are around 500 users in my organization.

In terms of latency, bandwidth, and productivity, Azure Block Storage is better than other solutions.

There have been problems with integration, but it's getting better.

I have used Microsoft Azure Block Storage for more than a year.

I would rate the stability as seven out of ten. We sometimes face issues.

I would rate the scalability as six out of ten.

Setup was simple. Between 5-10 people are required for maintenance.

I would rate the pricing as five out of ten.

I compared Azure Block Storage with AWS. The cost is the main difference.

I would rate the solution as six out of ten. I would recommend it to others.

The most valuable feature of Microsoft Azure Block Storage is the security and the management of user access from on-premise to the cloud.

Microsoft Azure Block Storage could improve by allowing the switching of the hot tier to the cold tier.

I have been using Microsoft Azure Block Storage for approximately five years.

Microsoft Azure Block Storage is stable.

The solution can expand, and it is scalable.

We have approximately 200 users using this solution. We plan to increase the usage of this solution in the future.

I did not use the support from Microsoft Azure Block Storage. However, I did use the support for other solutions. 

We deploy Microsoft Azure Block Storage with Linux SUSE or Red Hat, but Microsoft will not give us support for these solutions.

I rate the support from Microsoft a three out of five.

Neutral

The initial setup of Microsoft Azure Block Storage is simple.

The price could be more flexible, and it can be expensive.

I rate the price of Microsoft Azure Block Storage a three out of five.

I have not evaluated other solutions.

I rate Microsoft Azure Block Storage a seven out of ten.

Our primary use case of the solution is for objects search, objects with information, and documents file search.

The most valuable features of this solution are the ease with which you connect and use it.

The solution can be improved by including quicker hard drive access and larger bandwidth as part of the standard licensing fee.

I have been using the solution for seven years.

The solution is extremely stable.

The solution is easily scalable.

The initial setup is straightforward.

The implementation was completed in-house.

The solution requires an input-output operations fee as well as pay per gigabyte of storage. The solution also offers a quicker hard drive option and a higher bandwidth output for an additional cost.

I give the solution an eight out of ten.

We have 23 people in our organization currently using the solution.

We do not require anyone for maintenance or deployment.

I suggest to anyone wanting to use this solution to be careful with the design of the folders because if you add files without folders it can get messy.

It's mainly for financial institutions and customers. These customers are all using Cloud Native types of applications, whether it is Oracle Fusion or whether it's AWS. We are using the solution to handle the APIs.

Its integration is very easy.

The accuracy is relatively high.

It is stable and reliable.

The product can scale well.

The implementation can be quite technical.

We would like the solution to lower the costs as much as possible. It’s always better for the customer if it is less expensive.

I’ve been dealing with the solution for six months.

The solution is stable. It’s reliable, and the performance is good. There are no bugs or glitches. It doesn’t crash or freeze.

The solution is definitely scalable. It’s not a problem to expand it. If a company wants to, it can scale the product.

One client usually has about 1,000 assets to scan.

I’ve never had to use technical support. So far, the solution has been trouble-free.

My engineer can complete an installation in one or two days. I don't directly deal with it as it's quite complex. You need to be technical. It’s not for non-technical people.

We have five people that can handle deployment and maintenance. They are systems and ops engineers.

I would recommend the solution to other users and organizations.

I’d rate the solution seven out of ten.

The most valuable feature of Microsoft Azure Block Storage is the backing up of files.

Microsoft Azure Block Storage could improve by having integration with Amazon AWS. The file transfer could be easier.

I have been using Microsoft Azure Block Storage for approximately two years.

Microsoft Azure Block Storage is stable.

The scalability of Microsoft Azure Block Storage is good.

We have approximately 30 people using this solution in my organization.

The technical support from Microsoft Azure Block Storage is good.

I rate the support from Microsoft Azure Block Storage a five out of five.

I have not used another solution in the category of Microsoft Azure Block Storage.

The installation of Microsoft Azure Block Storage is simple.

I did the implementation of Microsoft Azure Block Storage myself.

The price of  Microsoft Azure Block Storage could be less expensive.

I rate the price of Microsoft Azure Block Storage a four out of five.

I rate Microsoft Azure Block Storage a seven of ten.

We deployed our website on Azure, and Block Storage is for storing large objects. We use Azure Block Storage for embedded videos that any person coming on the website needs to use. 

The most important reason we use Azure Block Storage is the ability to store large files. When we were building the solution, we knew we needed to store images and video files that are 100 MBs or more. The second thing is speed when dealing with such large file sizes. 

It would be nice if the Azure Block Storage could integrate with microservices-based mobile apps, too. 

We started using Azure Block Storage for a project two or three weeks ago.

Block Storage is stable. 

I can't say much about scalability because these are small projects, so it's not like we've utilized Block Storage for a million users. We only have a few hundred users.

The setup process is pretty straightforward.  The documentation from Microsoft is clear enough for anyone to set up a storage account. Two or three people are enough to maintain the solution we've built. It's a stable solution that more or less works on its own.

There should be a discount on Block Storage for people who use it more often. Right now we pay somewhere around maybe 30,000 rupees monthly.

Most of our solutions are built on Azure, so that is our first choice. However, we also considered AWS Storage Services. We thought about using the AWS S3 bucket, but our in-house team mostly has experience on Azure, we stuck with that. I think the Azure documentation is easier to understand than AWS's, so that's the main advantage. The costs are more or less the same.

I rate Azure Block Storage eight out of 10. My biggest concern is the pricing.

Of all the features I have used, it works great. While some require development, you don't need to for all of them. 

There are various types of storage to choose from - blob, table, and queue.

The initial setup is simple.

It has great documentation and community support.

When I installed Azure Explorer on my system, I connected easily, and, for uploading data and uploading any value or any files from there, it was very easy. However, when it's there in Azure Blob, Azure Portal, then uploading, downloading, or viewing the file is a little bit difficult. That's the part they need to improve. Downloading and uploading could be easier.

They could create more readability of files. We can use other solutions in desktop versions and then we can connect those Azure files. However, if anyone is working maybe in Linux or other things, then the Azure Portal is best for them. The readability is easier.

I've been working on the solution for more than 12 months.

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

It's like creating normal Windows files. Each time you have to create a file though, you can create it using CLI. However, if it's only a storage file and you can store large amounts, large volumes, of details. Scaling is simple. I have not had any challenge regarding Blob Storage, as I do not have much data actually. I haven't used it on a large scale. That's why I don't find any scalability challenges myself, actually.

While we have Microsoft technical support, I didn't take any Microsoft technical support yet, as their documentation is enough for me. If I get into any problems, I look for solution documentation or community help. That's enough for me.

The initial setup is very simple and straightforward. It's not difficult.

I haven't compared the solution to any other solutions just yet. We only deal with Azure.

I'm an end-user. I'd recommend this solution to others. I would rate it as eight out of ten.