Microsoft Azure Object Storage Reviews

I used the solution for email and messaging.

The layout of Microsoft is professional. It is suitable for office purposes.

The product hangs sometimes. The password retrieval process was very difficult.

I have been using the solution for ten years.

The tool’s stability has improved. It is much better now. It was not good 10 to 12 years ago. It used to freeze a lot. The UI has improved a lot.

The tool’s scalability is good.

The setup was complex. We created an account and decided on ways to retrieve passwords. We must also add our mobile number to the account.

I could do the deployment myself.

Google is better than Microsoft. Google's password retrieval process is very easy. However, Microsoft's layout and setup are much more professional. Google is much more user-friendly and interactive. Google is more secure than Microsoft. I often get emails on Microsoft that someone is trying to access my account.

I worked for a company that was a Microsoft Gold partner. I will not recommend the product to others. Google is a better tool. Overall, I rate the product a 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.

We use the Azure Object Storage for our IoT use case. We have thousands of vendors using our machines and they are sending machine performance data to Azure. We then use this data for analytics and product management.

We use it both in our development and production environments.

The most valuable options are performance and scalability. These two things are really effective.

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.

We have been using Azure Object Storage for the past two and a half years.

Azure is 100% stable, although there was an issue one time when the entire service was down for a day. This had a big impact, globally, although they were able to compromise with people who were affected.

This solution is used by the consumers of our products, of which there are at least 10,000.

Microsoft technical support is good because we have an enterprise agreement. We are happy with it.

We had our own servers, on-premises, and then we migrated to Azure.

The initial setup was of medium difficulty. I would not say that it is simple or complex, and they have good documentation to help.

It took more than six months to fully migrate to the Azure environment.

In the beginning, we had assistance from Microsoft. They helped us to come up with the proof of concept and the use case for our business. After that, our internal team took over. I would say that we had about 10% external help.

Azure Object Storage is a product that I strongly recommend for storing all of your unstructured data. Similarly, if you don't know what kinds of data you need to store, then this is the right choice. It also does well if you have massive volume.

There is an IoT hub that is going to be released and my hope is that it includes many advanced features.

I would rate this solution a nine out of ten.

We are using Microsoft Azure Object Storage for storing customer content. Our applications are running on Kubernetes, and the content is stored on the Microsoft Azure Object Storage. For example, we are using the queues for email. We have a couple of web jobs that are running that pick up the object from the queues. Additionally, we are using it for the files.

The most valuable feature of Microsoft Azure Object Storage is that it is on the cloud.

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.

I have been using Microsoft Azure Object Storage for approximately six years.

Microsoft Azure Object Storage is somewhat stable, but some improvements need to be applied. I can remember, it was down one time. We have faced a lot of issues since our application is tightly coupled with storage. More than 700 customers were affected during that time period. A lot of queries came, and lots of tickets were created for us because the storage was down.

Microsoft Azure Object Storage can scale in terms of users using the solution.

I am in a team of 50 and I am the manager of the team. In our company, all the project teams, and developers are using Microsoft Azure Object Storage mostly in the repair. We have approximately 300 to 500 developers using the solution.

I have contacted the support when the Microsoft Azure Object Storage could not be accessed. They did the recovery but it took them some time, approximately 10 hours.

We have only used Microsoft solutions.

The initial setup of Microsoft Azure Object Storage for me is easy, but it depends on the person. If you do not have much experience it is not as easy. The whole process of implementation took 15 to 20 minutes. We have automated a lot of the processes.

When doing the deployment of Microsoft Azure Object Storage we have experienced some issues with our scripts and the automation.

We have one person in my team that is managing Microsoft Azure Object Storage.

The licensing cost of Microsoft Azure Object Storage is monthly. We have two types of licenses. One is the EA enterprise license and the other is a CSP license.

My advice to others is if you're going to be copying the data in Microsoft Azure Object Storage it will be slow.

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

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.

Previously, all of our mail processes and mail access were on-premises and we were facing problems with storage, licenses, and maintenance. Once we moved to Office 365 Microsoft Azure Object Storage, all of the headaches were reduced.

We are using the latest version with Office 365.

Most of the brands are certified coupled with partners, such as AWS and Oracle. With Microsoft Azure Object Storage, they are an open market.

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.

I have been using this solution for the last two years.

This solution is stable. We have not had any issues to date. There are still some issues with spam in the emails, at 2% to 5%.

This solution is scalable.

Microsoft's technical support is excellent.

We are using Oracle as well.

The initial setup is straightforward and it is not complex.

It is very easy to migrate all of the mail processes.

Knowledge is very important, which is why we used the help of Microsoft integrators.

Because we are in the partner's program, they connected remotely and resolved all of the implementation tasks. They do a complete inspection.

We have a separate package and pay extra for additional technical support.

You can reduce operational costs and the cost of resources. It is easy to maintain, and I would recommend this product.

I would rate this solution a nine out ten.

We are currently evaluating this product. We have been able to explore certain things and are testing it. We are system integrators and we are not using it for our purposes but rather, for our clients. They have different applications, environments, and products, and we are looking to see if this is suitable.

Our clients want to use this for safely storing their data, and they would like high performance. At the same time, cost is an important factor for them. One of the things that they are storing is digital video.

This product is very reliable and all of the security that our client requires is available.

Technical support should be a little bit faster.

I have been using Azure Object Storage for one year.

In the time that we have used it, Azure Object Storage has been very stable.

This is definitely a scalable solution.

The technical support from Microsoft is good, although it could be a little bit faster.

As with everything from Microsoft, the initial setup is straightforward.

It took about two months for us to deploy for our client.

Based on the requirements given to us by our client, this is a product that I will recommend.

I would rate this solution a five out of ten.