Microsoft Azure Object Storage Reviews

For us, there was a specific use case where we were trying to collect some of the information and this was a project related to IoT information collection. That is where we used Object Storage. There was bot storage used as well. We were trying to collect some information from smart meters. That smart meter solution that we developed for the customer required both Object Storage as well as Block Storage.

There are a variety of good features. Which one is best really depends on the customer's focus or specific deployment. 

The initial setup is pretty straightforward. 

The solution offers good documentation.

When you get the right support person, you can deal with issues very fast.

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.

I've been using the solution for three to six months. It's been less than a year so far. 

I left before the solution was fully implemented. Therefore, while I did not see any instability, I can't speak to how stable it was once it was up and running. 

From our requirement perspective, the required scalability existed in the solution. We had no issues with scaling. 

I've interacted with technical support. They were okay. However, getting the person you need to assist you can be a challenge. 

Neutral

I have been comfortable with Microsoft technology, in general, and Microsoft approaches in the past as well. That's the reason, in most cases, I prefer to use Microsoft solutions as such.

The process is not that complex. There is a challenge finding resources who understand the cloud, however. With most of the technologies, there is enough documentation, however, what happens is, when you are looking at the whole ecosystem as such, you need resources that know what is happening. Generally, there are articles that can assist you with the setup. Therefore, for those who have knowledge with the solution, it's straightforward, however, newer users would find it possibly a bit complex. 

I'm not sure how many people would be required to maintain the solution. 

I haven't gotten a chance to evaluate this solution in comparison to others. For example, I've never been able to compare Object Storage on AWS.

The company I worked for was a Microsoft gold partner. We were Azure partners as well. 

We use a private cloud deployment. There were some sensitive products that were supposed to only be available as a part of the private cloud, even though they were in the Azure cloud, they were fully accessible from the internal network.

I'd rate the solution seven out of ten.

My job title is DevOps Cloud Infra, Cloud Engineer. I am an expert in Microsoft Azure Cloud and telecom. 

Inside the storage account, we use Blob Storage, mostly to store VM data, discs, and logs. We also use FileShare as an additional disc.

The features of Microsoft Azure Object Storage that are most valuable are the ones providing encryption.  Access is more controlled using private endpoints and SaaS token keys. Many access control features exist. 

I also enjoy the size of the Blob Storage, it can store up to three gigs. Another good feature is that we can host 10 static websites.

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.

I have been using Microsoft Azure Object Storage for four years.

The solution has been stable for us.

There has been no issue with scalability with this product when accessing or adding users. However, we noticed that when we generated SaaS, it is at the storage account level. This should be specific to containers. However, whenever we change the container name without changing the whole key, it works.

The solution is specific to the application and not personal usage. For most applications, I see between one or two storage accounts. Most people are logging log storage and diagnostic storage. 

During the initial setup of Microsoft Azure Object Storage, we used File Explore, so it was not that difficult. It was via GUI, which was helpful. One challenge was when using the command CLI because it was new to us. Over time, we are ok with CLI too.

We have seen a positive return on our investment in this solution. We just need to make sure we clean up our storage and services which are not used.

Microsoft Azure Object Storage requires a license. We use a pay-as-you-go model and we have an enterprise subscription model as well.

The solution is not expensive, however, when compared to other enterprise, pay-as-you-go products, it is priced higher. 

I would recommend Microsoft Azure Object Storage to anyone considering implementing this solution. The UI is easy to manage. When you go inside Blob, it looks just like your local File Explorer. Also, you can feel confident that encryption is there.

I would rate Microsoft Azure Object Storage an eight out of ten overall.

Our use case is related to a data lake. It is just a file collection.

I am using its latest version. It is in the cloud through a private company.

AzCopy is probably the best feature. It's a scripting app or a scripting function. Whether it's a Linux batch or a PowerShell script, you can essentially just send a file via a line of code with a specific key.

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.

I've been using it every day for four years.

It is stable.

I haven't hit any limitations yet, and I'd say it is scalable. There are probably different scaling solutions, such as a data lake or a data warehouse. Those would be the next version of this, as opposed to binary large object storage.

We have less than five users.

It's a Microsoft product. They're the best software company in the world. So, the support is quick. It is immediate. Sometimes, it is too quick but pretty helpful. They'll get you through the problem. Their support is definitely very good.

It is easy to set up. You just sign in. You have to have a cloud subscription. Once you deploy a disk or any sort of object that can be manipulated in the cloud on a cloud-based model, all you do is sign in, and access should be granted to that resource.

It was implemented in-house. I take care of its deployment and maintenance.

It has a pay-as-you-go model. So, you are only paying for what you store. It's an attractive model. You don't pay for a set; you pay for what you actually use.

It's definitely one of the top Azure Cloud objects out there for file storage and accessing files. Especially if you're using the Microsoft ecosystem, it's definitely one of the best tools for cloud storage for files.

I would rate it a nine out of ten just because of the mobile presence.

Our company is a managed service provider and we recommend the solution to customers. 

The solution integrates well with Microsoft Office 365 and includes important features such as SIEM, storage, SQL, and Cosmos DB. 

The solution should integrate better with other vendors and products. 

A more comprehensive training option is needed. 

I have been using the solution for one month. 

The solution is pretty stable. 

The solution is very scalable. 

We provide technical support for our customers and raise any escalations directly to Microsoft. 

The initial setup is somewhat complex. I provide the networking or underlay for services and other team members deploy the solution. 

We implement the solution for our customers. 

The solution and AWS are the most stable options in the public cloud domain so I recommend either depending on use case. A cost analysis will determine which option is the best fit. 

Services are more feasible with one cloud provider as opposed to multiple cloud providers at the same time. 

I rate the solution a six out of ten. 

We use this solution to store images and Excel files.

We used to use an on premise file system and the maintenance of on a premise server is difficult. This is why we migrated to Azure storage. Using this solution has reduced our maintenance time and cost. 

The file retention and object retention have been most valuable.

Uploading files from the UI has presented some issues. When editing work and once you delete a file, it takes some time to recreate the same file. If I have an ABC file and if I delete it and I want to recreate the file again with the same name, it is not immediate. There is at a least 30 seconds or one-minute delay.

We have been using this solution for three years.

This is a stable solution. 

This is a scalable solution. We have specifically configured it for scalability. 

We have reached out for technical support but not directly related to Azure Storage. We had a Logic app and we tried to connect it to Azure Storage. They provided a solution but it was not a limitation of Azure Storage and rather a limitation of the Logic app.

I would rate the support for this solution a nine out of ten. 

Positive

The initial setup is straightforward. We had no issues with the deployment because we used GitHub Action, Azure DevOps, terraforms as well as AMS scripts to build and deploy. Deployment did not take more than a minute.

We have used a pricing calculator to find out the general pricing for our clients. 

I would recommend this solution to those who already have an on-premise file system and who want to migrate to a cloud-native solution. This solution offers scalability at a lower cost and additional benefits compared with an on-premise file server.

There are a couple of different use cases. One is a cheaper form of storage and also robust protection of data. We also use it for its immutability. If you have enough copies, then it will always be available.

Storage accounts are used for things like logic analyzers that feed into the different archives. It also feeds into Azure Backup. You can peer into different levels of the archive.

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.

I have been using Microsoft Azure Object Storage for a few years now, but it's very sporadic.

I would rate the stability of this solution an eight out of ten.

I would rate the scalability an eight out of ten.

I contacted technical support a few times. Our technical support is under a premium plan. They were very good.

Positive

The initial setup is fairly easy. It's not difficult. It is mainly a hybrid solution.

I would rate the pricing a four out of ten because there is a lot of competition out there.

I would rate Microsoft Azure Object Storage a six out of ten.

It's a platform we're currently adapting for various scenarios like development, deployment, and security needs for new solutions. 

The performance of the solution is good. It’s also good in terms of Information Security (IS) and structured services.

I have been using this solution for the past three years.

The solution is stable. It works fine for us.

We plan to increase the further usage depending on the customer's requirements. 

The operations team handles the support. If they need anything, they deal with it directly, and I haven't heard any complaints.

The initial setup is straightforward. It’s deployed on the cloud.

Our storage capacity is cheap because we have a committed discount. 

I recommend it. However, it depends on the specific use cases and existing environments. For new users, especially, it is a good start. 

However, those with several years of industry experience should thoroughly analyze requirements to determine which suits them better. 

Overall, I rate this solution a seven out of ten.

Our primary use case for the solution is data storage and on-premises backups to the cloud.

The initial setup is not easy to understand and the scalability can be improved.

We have been using the solution for approximately two years.

The solution is stable.

The solution is scalable. I rate it a five out of ten.

We have had a good experience with customer service and support. I rate them a seven out of ten.

Neutral

I rate the initial setup a five out of ten.

We have deployed the solution on-premises.

Licensing fess are charged monthly.

I rate the solution a six out of ten. The solution is good but the scalability and initial setup process can be improved.