Senior Consultant at a tech vendor with 5,001-10,000 employees
Consultant
Top 10
2023-09-27T03:01:00Z
Sep 27, 2023
The solution can be quite slow. Having some sort of caching algorithm could be quite good so that it is placed on the edge of the customer network. But this will lead you back to on-premise infrastructure, so it cannot fix the whole cloud.
Learn what your peers think about Microsoft Azure Object Storage. Get advice and tips from experienced pros sharing their opinions. Updated: April 2024.
Senior DevOps Engineer at a tech services company with 501-1,000 employees
Real User
Top 5
2023-02-13T20:28:00Z
Feb 13, 2023
One of the things that are currently important is consistency. To achieve this, another database called Cosmos DB is available. We want to have a similar consistency to the one in Cosmos DB but at a cheaper price. Although Cosmos DB is known to be expensive, it has a guaranteed consistency level of 99.99%. I want Microsoft to explore how they can provide the same consistency level as Cosmos DB but at a lower cost. Speaking of consistency, we are currently using GRS or GZRS as our storage redundancy types. It would be great if we could achieve the same guaranteed consistency level as with Cosmos DB. It would be of great use if we could apply the same approach to our storage account. Currently, I do not have any suggestions regarding Blob Storage. The storage account allows for storing VHD, which is a type of blob, along with other blob types, such as append blobs and page blobs. These blob types are already well-matured designs, and I don't have any suggestions. The storage account also offers different tiers, such as cool, hot, and archive tiers, as per the access. These features meet the needs of data and application engineers for storing data. Mostly, it has all the features to meet the current requirements, and it is one of the well-designed resources from Microsoft.
DevOps and Cloud Engineer at Neudesic Technologies Private Limited
Real User
Top 10
2022-06-28T11:31:00Z
Jun 28, 2022
The solution needs to improve the custom domain integration with static web pages. Even though Blog Storage is providing the static content hosting feature, due to the custom domain availability, the integration is not available. In most cases, we withdraw from that service and use our app service to host our static data feeds. For future releases, I would like to see the graphical representation of the Blob Storage and the analytics to be in the value review panel so we can go to the cost in subscriptions to get them. We need some graphs with the presentations.
While we defined the solution, it was not fully implemented before I left. Therefore, it would be difficult to point to an area that was lacking. Technical support with Microsoft is a bigger challenge as finding the right person to support you and actually getting that person on the call is hard. If you are able to get the right person on the call, then he is able to help fast. That said, in most cases, getting the right person on the call itself is a challenge. The setup process could always be a bit easier. It's hard to find good resources. With the cloud being new, it's difficult to find the people who have done it already.
Information Technology & Cloud Systems Manager at a hospitality company with 51-200 employees
Real User
Top 20
2022-05-27T19:40:36Z
May 27, 2022
Currently, the Microsoft Azure Storage Explorer is just a Windows app. I don't know if it's available on mobile, such as iOS or Android. I don't know if the app is mobile-friendly. It should be mobile-friendly.
Manager-Platform Team / Technical Lead at Sana Commerce
Reseller
Top 5
2022-05-24T16:58:31Z
May 24, 2022
We have experienced a data copy bottleneck with the AZ copy using Microsoft Azure Object Storage, this should improve. It has high CPU consumption. There are a couple of ways to copy files fast, we have tried a few ways. Other than AZ copy, we can use Azure Fluent Storage, which also takes a lot of time to copy files. The AZ copy is faster but it takes a lot of time and CPU operations. Microsoft Storage Explorer is used for connectivity but it needs to be improved. On the backend side, it is not an easy implementation, and if they introduced a solution roadmap, that would be great.
If we look at the different versions of that ADLS, it really does not have a hierarchical storage mechanism. If you want to store any document, you have to go and create one blob storage account, in case you want to store any hierarchical data.
Owner at a tech services company with 11-50 employees
Real User
2021-03-15T16:28:26Z
Mar 15, 2021
They could improve AI and ML-based modules. They should add more modules based on artificial intelligence and machine learning. Pricing is a little bit tricky with Microsoft Azure. They do provide the estimates, but it is not easy to guess the exact amount that we will be billed after a month or two because it is based on usage. This is a little confusing.
Architect at a recreational facilities/services company with 1-10 employees
Real User
Top 20
2021-01-24T08:58:09Z
Jan 24, 2021
There are a lot of points for improvement at the moment. For example, in the case of this product, we are not able to do a backup of what we call NAS, network-attached storage appliances, directly to the cloud. We can do to all the repositories in our premises on the storage that we have here, however, it's not possible to entirely upload this to the cloud. To me, this is the major problem of this solution, at the moment. There are other problems that I imagine other solutions can have the problems too, for example, there are some errors if the network is unstable and there are network failures sometimes, and it's not easy to recover data. The administration of the solution is not as easy as we would like it to be.
Principal Enterprise Architect at a construction company with 201-500 employees
Real User
2020-08-19T07:57:30Z
Aug 19, 2020
The cost should be reduced to make it more competitive. There are other vendors that provide good solutions, so if Microsoft were more competitive in terms of pricing then it would be one reason for us to continue with them. I would like to have out-of-the-box connectors to make integration with other products easier.
Lead - CIO at a tech services company with 51-200 employees
Real User
2020-03-03T08:47:00Z
Mar 3, 2020
We've seen some performance issues with Azure Table storage. It's quite slow. The performance surrounding it should be improved to speed things up a bit. Moving data from cold storage to the hot storage, or, to put it another way, moving data back and forth between regular storage and archival storage is difficult. There's no easy way to do it. In the past, we've been required to download the data and then upload it to cold storage. It's an annoying process. If the solution could fix this it would be much better.
They could provide multiple tools to provide you with cost calculations, giving you a better picture or providing you with better details of the cost calculations over the years.
Information Technology Project Manager at a logistics company with 5,001-10,000 employees
Real User
2020-01-22T12:44:00Z
Jan 22, 2020
Support and cost are areas that can be improved. The cost of support is always expensive. They can be more competitive in their pricing and the data center doesn't compare to other solutions such as Google. Microsoft is still growing. In the Middle East and these areas, there is less support.
Object re-use should be improved in order to get better performance and reduce the cost. We have experienced performance issues on the website. The interface on the homepage can be improved. When we are uploading items into storage, we only get information from a high level. This makes it difficult to find and delete specific files.
REST-based object storage for unstructured data in the cloud
Store infrequently accessed data in a low-cost cool storage tier
Store frequently accessed application data in a hot storage tier
Stream video, audio, and other media to web, mobile, or desktop applications
Power big data analytics
Access your data more securely, both over the wire and at rest
Microsoft Azure Object Storage needs to improve stability and cloud user interface.
The solution's stability should be improved.
The stability could be improved.
The solution’s stability could be improved.
The tool should be a little bit cheaper.
The solution can be quite slow. Having some sort of caching algorithm could be quite good so that it is placed on the edge of the customer network. But this will lead you back to on-premise infrastructure, so it cannot fix the whole cloud.
The product's cost needs improvement during the POC stage. Additionally, its user interface could be better compared to AWS and GCP.
The pricing of the solution can be improved.
One of the things that are currently important is consistency. To achieve this, another database called Cosmos DB is available. We want to have a similar consistency to the one in Cosmos DB but at a cheaper price. Although Cosmos DB is known to be expensive, it has a guaranteed consistency level of 99.99%. I want Microsoft to explore how they can provide the same consistency level as Cosmos DB but at a lower cost. Speaking of consistency, we are currently using GRS or GZRS as our storage redundancy types. It would be great if we could achieve the same guaranteed consistency level as with Cosmos DB. It would be of great use if we could apply the same approach to our storage account. Currently, I do not have any suggestions regarding Blob Storage. The storage account allows for storing VHD, which is a type of blob, along with other blob types, such as append blobs and page blobs. These blob types are already well-matured designs, and I don't have any suggestions. The storage account also offers different tiers, such as cool, hot, and archive tiers, as per the access. These features meet the needs of data and application engineers for storing data. Mostly, it has all the features to meet the current requirements, and it is one of the well-designed resources from Microsoft.
The initial setup is not easy to understand and the scalability can be improved.
The solution should integrate better with other vendors and products. A more comprehensive training option is needed.
We are not missing any features. We would like it if we did not have to use another encryption solution to encrypt the storage.
The solution needs to improve the custom domain integration with static web pages. Even though Blog Storage is providing the static content hosting feature, due to the custom domain availability, the integration is not available. In most cases, we withdraw from that service and use our app service to host our static data feeds. For future releases, I would like to see the graphical representation of the Blob Storage and the analytics to be in the value review panel so we can go to the cost in subscriptions to get them. We need some graphs with the presentations.
While we defined the solution, it was not fully implemented before I left. Therefore, it would be difficult to point to an area that was lacking. Technical support with Microsoft is a bigger challenge as finding the right person to support you and actually getting that person on the call is hard. If you are able to get the right person on the call, then he is able to help fast. That said, in most cases, getting the right person on the call itself is a challenge. The setup process could always be a bit easier. It's hard to find good resources. With the cloud being new, it's difficult to find the people who have done it already.
We're still testing the solution. It's too early to make any suggestions as to what may be missing.
Currently, the Microsoft Azure Storage Explorer is just a Windows app. I don't know if it's available on mobile, such as iOS or Android. I don't know if the app is mobile-friendly. It should be mobile-friendly.
We have experienced a data copy bottleneck with the AZ copy using Microsoft Azure Object Storage, this should improve. It has high CPU consumption. There are a couple of ways to copy files fast, we have tried a few ways. Other than AZ copy, we can use Azure Fluent Storage, which also takes a lot of time to copy files. The AZ copy is faster but it takes a lot of time and CPU operations. Microsoft Storage Explorer is used for connectivity but it needs to be improved. On the backend side, it is not an easy implementation, and if they introduced a solution roadmap, that would be great.
If we look at the different versions of that ADLS, it really does not have a hierarchical storage mechanism. If you want to store any document, you have to go and create one blob storage account, in case you want to store any hierarchical data.
They could improve AI and ML-based modules. They should add more modules based on artificial intelligence and machine learning. Pricing is a little bit tricky with Microsoft Azure. They do provide the estimates, but it is not easy to guess the exact amount that we will be billed after a month or two because it is based on usage. This is a little confusing.
There are a lot of points for improvement at the moment. For example, in the case of this product, we are not able to do a backup of what we call NAS, network-attached storage appliances, directly to the cloud. We can do to all the repositories in our premises on the storage that we have here, however, it's not possible to entirely upload this to the cloud. To me, this is the major problem of this solution, at the moment. There are other problems that I imagine other solutions can have the problems too, for example, there are some errors if the network is unstable and there are network failures sometimes, and it's not easy to recover data. The administration of the solution is not as easy as we would like it to be.
Technical support should be a little bit faster.
The cost should be reduced to make it more competitive. There are other vendors that provide good solutions, so if Microsoft were more competitive in terms of pricing then it would be one reason for us to continue with them. I would like to have out-of-the-box connectors to make integration with other products easier.
I would like to see a reduction in pricing so that they can be more competitive.
Technical support should be faster at resolving issues for tickets that we create.
We've seen some performance issues with Azure Table storage. It's quite slow. The performance surrounding it should be improved to speed things up a bit. Moving data from cold storage to the hot storage, or, to put it another way, moving data back and forth between regular storage and archival storage is difficult. There's no easy way to do it. In the past, we've been required to download the data and then upload it to cold storage. It's an annoying process. If the solution could fix this it would be much better.
They could provide multiple tools to provide you with cost calculations, giving you a better picture or providing you with better details of the cost calculations over the years.
Support and cost are areas that can be improved. The cost of support is always expensive. They can be more competitive in their pricing and the data center doesn't compare to other solutions such as Google. Microsoft is still growing. In the Middle East and these areas, there is less support.
Object re-use should be improved in order to get better performance and reduce the cost. We have experienced performance issues on the website. The interface on the homepage can be improved. When we are uploading items into storage, we only get information from a high level. This makes it difficult to find and delete specific files.