Microsoft Azure Block Storage Reviews

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.

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.

We have embarked on the journey of the global data list. All the data from the SAP systems, all the data from external vendors, and all the data from our enterprise data warehouse are staged onto the Azure Block Storage. It forms the basis of the Lakehouse architecture. That's the staging layer for us.

It has helped to centralize the data. People see it as the central source of truth. Everybody sees the same set of data across data analysts, business analysts, data scientists, and all the visualization people. It provides a centralized view of the same data.

The product offers hierarchical storage and we like the main space storage with business.

It's easy to set up.

We find the product to be stable. 

It is very scalable. 

The solution needs a direct connection to visualization. Power BI connectivity on this platform is not that great. We need a direct connection to any of the visualization tools. There should be more BI integrations.

Block Storage is something which I use on a day-to-day basis. I've used the solution for six years at least.

It's pretty stable. It has cloning and therefore has data redundancy. The disaster recovery is pretty easy with this solution.

The solution can scale well.

The solution is used across the organization in BI and data visualization leads. There are more than 300 people using it.

The use is increasing month to month with more and more data being placed into it. It's an ongoing process.

Technical support is very good. 

This was the default product we went with thanks to our partnership with Microsoft.

The initial setup was straightforward, not that complex. 

Setting up was probably a month's time, not more.

The DevOps engineers would be required for the deployment. In fact, data engineers can do it if there's no proper CIC mechanism, however, any DevOps expert can do it.

We handled the deployment in-house. 

I'm from the technology side, so I have not done that ROI comparison. It is not visible to me directly. However, I have heard that there was a bottom-line increase. 

The storage part costs us $223. That's on a monthly basis for 20TB of data storage. There are no additional costs.

We did not look into other options. 

I am a customer of Microsoft products.

We are dealing with the Azure Block ADLS Gen 2.

People should use the mechanism to save more costs. We have a hot tier and a cold tier, wherein, say you want to save more on your cost, the frequently accessed data should be in the hot, and data that is not accessed frequently should be moved to the cold tier. It helps in reducing costs by almost 50%. The tiering mechanism should be used and new users should know it is possible to arrange their data that way. 

I'd rate the solution eight out of ten.

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.

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.

This solution is integrated to the backup console, so there's no user interaction. We're using Azure Block Storage as our second copy storage.

We're working as a distributor.

We use this solution for backup storage on our on-premise backup.

There are capacity limitations that could be expanded.

When freeing the backup capacity on our disk, we have to create another block storage and integrate with that. The limitations may be an issue with the customer.

It should be more flexible for customers. For example, if a customer needs 10TB of capacity, it should be flexible for the customer to expand to that capacity.

I have been using this solution for one year.

It's a stable solution.

There are some limitations when it comes to the capacity and scalability.

Installation is simple. You don't need an integrator or consultant for setup.

We compared this solution with AWS S3. It mostly works like object storage.

I would rate this solution 9 out of 10.

We use the solution for application hosting only - in terms of giving an application which is serving to some customers, for a particular location service. 

From a UI perspective, we like the workflows. Its look and feel are quite good. 

The initial setup is quite simple and straightforward, especially if you have IT knowledge. 

It is very flexible and scalable. It's very easy to adjust the data. 

The stability is good.

As a technology product, it's always evolving. There are some feature challenges from my side, however, I am hopeful they will fix the issues. 

The integrations right now are limited, however, we are hopeful this will improve as the cloud continues to develop. We would like to see more capabilities in specifically hybrid scenarios. There are some third-party tools in Oracle and Linux we'd like to have access to via this product.

We'd like more failover capabilities or data recovery options. 

I've been using the solution for six months. 

The solution is stable. There are no issues with bugs or glitches and it doesn't crash or freeze. It's reliable. 

It is a scalable solution. If you need to expand it, it's not a problem. 

We have about 50 users on this solution currently.

The initial setup is very simple and straightforward. It's not very complex. It's much easier if you do some planning and can anticipate some outcomes. Doing that work makes everything easier as you do the implementation. Those with IT backgrounds will find it easier to handle the setup as opposed to those who are not so technical.

The pricing varies. You might have different pricing, for example, in relation to your country or region. It's not standard. We pay around $300 to $400 a month for some scenarios where consumption is limited. However, going forward, we're seeing the likelihood of the cost coming to around $2,000 as consumption rises. 

We have never actually attempted to evaluate this solution in comparison to others. 

I would recommend the solution to others.

I would rate it eight out of ten.

We use the hybrid version of Microsoft Azure Block Storage. We have a client based in the UK who utilizes the hybrid cloud. We also have a couple of archiving solutions there, as well as NetApp on TapCloud. 

The NFS solution goes into that, deployment is purely on the Azure cloud. The production areas and archiving solutions are mostly done on-premises, while testing and application development in some areas is purely cloud-based.

Block storage is used for the data that is configured for our servers. We have it for auditing purposes and as a compliance method.

Microsoft Azure Block Storage is a stable solution.

As for scalability, we use other archiving solutions, NetApp on TapCloud, for example, because there are some limitations with capacity unless you extend the terabytes of data.

It has been a couple of years since I contacted support. However, at that time, it was difficult to get someone on the call even though it was an issue of high severity.

Positive

The initial setup for the production areas was on-premises, which is very simple.

Azure Block Storage is higher priced than its competitors. It is costly. The pricing is difficult to calculate as there are different tiers to select from. 

Microsoft Azure Block Storage is widely accepted. People are choosing the enterprise solution. I would rate the solution an eight out of ten.

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.

We have a few clients that use the solution. 

The use cases have been huge. One of the applications we are developing is an internal tax system. We tend to get a lot of client files through different channels and store them in the Block Storage. It's standing on a huge system. It's a multi-cluster, multi-AG kind of informer.

The features are pretty good. Our company mostly uses Java and Microsoft technology. We get good metadata and can save different metadata within the solution.  

It can scale. It's at 99.99%. We can always use a different life cycle on objects so that means we don't want to store the object. On one side probably we can do cold storage and kind of thing. 

Basically, there are a lot of features that are provided and we have a lot of options.

The solution is stable. 

We found the initial setup to be straightforward. 

The solution could use a couple of security features. They still have a lot of other features and everything is coming along quite nicely now, however, I would expect more features in the near future. We'd like more policies and authentication.

We've used the solution for about five years or so.

The solution definitely offers durability, and, stability-wise, we have no complaints. AWe tend to make a backup since it is working on the cluster side, so we do a backup every day. We are also able to access it at a global level.

Speed-wise, I don't see any latency issues.

The solution can scale quite well.

We have 100 clients using the solution. We have a big team in general. 

We have a relationship with and are directly partnered with Microsoft. That means we have our own technical support directly from Microsoft. They are our dedicated architects. We have a data communication channel open, so we can talk to them anytime about anything. We're quite happy with the arrangement.

We have a lot of internal products. The development team has been using Azure Storage and Block Storage and Databricks and other products from Azure.

The initial setup is pretty simple. It's not overly difficult or too complex. 

The solution is pay-as-you-go. We don't have any subscriptions; it is more like an on-demand arrangement.

Our company has ties with Microsoft. We kind of partner with Microsoft so we always attempt to propose Azure Solutions, especially in the cloud.

I would recommend the solution to others.

I'd rate it nine out of ten.