Microsoft Azure Object Storage Reviews

The main use case that I have in my company is to store some scanned documents from our customers.

The most valuable feature of the solution is the tool's price since it is not expensive. The tools that support using Azure Blob Storage, like the open source storage accounts like Azure Storage Explorer, are really easy to use and user-friendly. When it comes to life cycle management, you have many pricing tiers associated with storage costs. You can use policies to change between the pricing tires, and it is really easy to use the policies.

For me, there are many things that are only possible to be used in the CLI for easy copying. I think if the tool puts features that only exist in the easy copying area through Azure Storage Explorer, so introducing such features in Microsoft Azure Object Storage can make it more user-friendly.

I have been using Microsoft Azure Object Storage for five or six years. I am a customer of the solution.

I didn't have any problems, so I didn't use the tool's technical support. I found everything that I needed on the internet or using the CLI, so I never had to use the tools' support. I rate the tool a six out of ten.

Neutral

I have only used Microsoft Azure Object Storage.

The product's initial setup phase is straightforward, but if you don't pay attention, you will have to delete and create another storage because some options cannot be changed.

The product's deployment phase is easy.

The solution can be deployed in a couple of minutes.

For any kind of cloud provider, when you use the correct tools instead of just putting virtual machines inside the cloud, you will always have a good return on investment. I don't see Azure to be very different from AWS.

I didn't have any problem with the tool's durability, so I guess it is okay. We have used it for many years, and there hasn't been a single case of missing documents, as it always works perfectly.

Azure Data Lake Storage Gen2 is a tool my company started to use with Azure Databricks, and it has been a good experience till now. When it comes to pricing, Azure Databricks uses a large amount of data, and the price is okay even with a lot of data to manage.

Microsoft, in general, is complicated because there are some tools that we have great support for, and there are some tools that you simply don't. For example, I worked with an application gateway, and the support wasn't great. There are lots of people working with me. When there were some issues in the application gateway, we had to figure it out for ourselves, and the the support wasn't able to help us. There are other tools for which the support is good.

Speaking about AI and Microsoft Azure Object Storage, Azure Data Lake Storage Gen2 helps us to update Azure Data Lake Storage sources, and when you enable the option in the storage account, you can connect a lot of tools, like Azure Databricks or Azure Machine Learning Studio, so you can use them as a source of data for your models. The tool helps us since it is easy to use. The tool is pretty straightforward. You don't have to think about the tool, as it just works fine.

I recommend the tool to others.

I rate the tool an eight out of ten.

I worked in Azure Cloud mostly on the Databricks side, with SQL Server or Synapse Analytics, or streaming analytics. It's a blob storage solution. We use the storage account, either the blob storage or the ADLS Gen 2.

We can do data queries easily. If it's a JSON document or XML document, mostly we deliver the APIs, calls, and all. The document is stored as an object stored in the Blob Storage. Then, using the Databricks, we try to process that JSON and then load it into a Delta Lake table. That is where we interact mostly with Object Storage.

The initial setup is straightforward. 

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. 

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

It's all scalable. It has lifecycle management where I can define a rule so that I can easily archive or move the data from the cool tier to the hot tier based on the uses and then I can also send it into the cool tier so that it can be frequently accessed. If I do that, the cost can also be minimized.

Technical support is great. We have a partnership basically with Microsoft. For my organization, Microsoft is the partner vendor. Whenever it is required, support is readily available to us.

Positive

I'm also familiar with Amazon S3. 

The initial setup is straightforward. You just have to create a storage account. You can automate that also. You have different mechanisms. You can use Azure templates, like SQL, or you can use the Terraform as well. To automate the creation of that object storage or any account. Or, if you have different APIs, like Python-based API, you can easily create what you need.

If we compare most of the other cloud vendor solutions, for example, S3 Object, S3 with the Blob Storage, more or less, both have the same capabilities. However, from a security perspective, Azure is very good. Azure offers AD integration with the storage account. That is something I find as a good feature compared to the other clouds and integration with all the Azure services is a really useful feature.

We're a gold partner with Microsoft.

I'd rate the solution nine out of ten due to the ADLS integration and the different authentication mechanisms that we have.

We need to make sure that the data which we are storing in those storage objects is highly secured. That is where Azure is providing us with the best features. We can go with the different mechanisms like its Nexus security or the AD authentication. Or, they also provide us admin encryption, including the transparent keys. With transparent encryption, we can encrypt based on customer-based keys. Those are also some good features that make it a really great product.

I appreciate the scalability of this solution; it is fully scalable and excellent for certain tasks. One thing I particularly like is the block solution, where files are divided into parts and sent through the firewall in parallel, making it incredibly fast. However, there have been some issues with disconnections, especially when downloading large files. It works perfectly for handling many smaller files, though. The initial storage options, like data lake storage, are diverse and cater to various needs such as big data analytics. As a certified professional architect expert, I find it crucial to understand specific requirements to make the most of these solutions.

Our current Azure setup faces challenges with API connectivity, particularly due to misconfigurations related to changes in Azure Graph. Version disparities in APIs and duplicated features have been flagged by Microsoft, complicating security updates. To enhance efficiency, we need improvements in the configuration process, ensuring a smoother integration of our solutions with Azure services. Additionally, naming and access control have been a bit challenging. While we start by setting private access for files in Blob Storage, syncing becomes an issue when making the Blob solution publicly accessible. It is like the Linux system, where granting access to an upper folder doesn't automatically cover internal files. Unlike Windows, here we need to be more specific about access, making it a bit tricky to manage.

I have been working with Microsoft Azure Object Storage for over ten years.

I would rate the stability as a nine out of ten. It is very stable.

Scalability is one of the strongest aspects of the product. I would rate it as a nine out of ten. We have approximately 10,000 end users of the product.

When it comes to technical support, the UK team has been good and responsive, especially with premium support. However, the Indian support team's performance is not as strong, and I would rate them around five out of ten. Advanced support, on the other hand, tends to be more efficient and timely in assisting.

Neutral

Before Microsoft products, we worked with other vendors like AWS for scalable storage solutions. The choice between AWS and Microsoft Azure largely depends on the client's existing setup – for instance, if they were using AWS before, we often stuck with that. However, in cases where object storage was a priority, we found Microsoft Azure's Blob Storage to be a fitting solution. It is all about adapting to the client's needs and the specifics of their setup.

We haven't been actively maintaining the product from our end. Currently, our technical team comprises 20 engineers.

The pricing for the product can be reasonable, especially for standard usage. I would rate it as a six out of ten in terms of costliness. However, costs can escalate if you are using storage accounts for resource-intensive cases. It is important to assess the nature of your usage and whether a more cost-effective solution exists. 

Using Microsoft Azure Object Storage depends on the specific use case. For storing numerous small files in the cloud, object storage like this is excellent -persistent, flexible, and generally a good fit. However, for tasks involving deep data analytics or databases, it is more of a case-by-case decision. Evaluating your specific needs and how well the solution aligns with them is crucial. Overall, I would rate the solution as an eight out of ten.

We have implemented the solution for some of our customers as a static file storage platform. One of our customers has a website, and they have to save some of the images the users are sending to the website. Another customer uses the product for backup purposes. They have a first backup on their on-premises software. After that, they copy the backup data to Azure Object Storage.

Versioning is a valuable feature. We use the immutable storage feature on Azure. AWS also provides such features.

The tool should be a little bit cheaper.

I have been using the solution for three to four years. I am using the latest version of the solution.

The product is stable.

The product is scalable. Veeam Backup systems are using the solution as a second backup.

We also use Amazon S3. Some of our customers want cheaper storage solutions. So, we use other cheaper local solutions sometimes.

The initial setup is very straightforward. It did not take more than an hour. To deploy the solution, we must prepare Azure Storage on Azure Portal. If the end-user or the customer doesn't have an Azure subscription, we create a subscription from our distributor channel. Then, we create the storage for our customers after granting the necessary permissions. For Veeam customers, we go to the Veeam management dashboard, create a backup job in the configuration settings, and point to Azure Object Storage.

We deployed the product in-house.

The solution has a monthly licensing fee.

I recommend the product to others. Overall, I rate the tool an eight out of ten.

We use the product for all kinds of images and static data. 

The tool's most valuable feature is performance. 

Microsoft Azure Object Storage needs to increase its response time from 25,000 per second to 40,000 or 50,000. 

I have been using the solution for nine years. 

I rate the product's stability a ten out of ten. 

My company has 100 users for Microsoft Azure Object Storage. 

The solution's support is good enough for us. 

Microsoft Azure Object Storage's deployment is straightforward. 

We deployed the solution in-house. 

Microsoft Azure Object Storage is not expensive. 

I rate the product a ten out of ten. 

Microsoft Azure Object Storage is used to install big datasets in the cloud at a reasonable price.

Microsoft Azure Object Storage provides a platform for uploading or downloading big datasets.

The solution's stability should be improved.

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

I rate Microsoft Azure Object Storage a seven out of ten for stability.

Since Microsoft Azure Object Storage is a cloud-based solution, it is easily scalable.

The solution is used extensively by our organization’s IT team.

The solution's initial setup is easy.

The solution's deployment took just a few minutes. You have to install and run the setup file and then connect that to the specific bucket. You have to provide keys to get access and get access to the specific area, and you can start uploading or downloading.

With Microsoft Azure Object Storage, you pay for the data you have stored there. You can download the application from Microsoft free of charge.

I am working with the latest version of Microsoft Azure Object Storage. Microsoft Azure Object Storage is a cloud-based solution.

Since Microsoft Azure Object Storage is a cloud-based solution, users should ensure they have a good bandwidth for uploading. Most internet service providers provide far better download speed than uploading speed. If you use the solution frequently, ensure that your uploading speed is updated with your downloading speed.

Microsoft Azure Object Storage is a very good solution if you need to safely store large datasets on the cloud.

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

Azure Object Storage is basically for storing files - if you want to process certain files. It's useful for if you want to keep images or some documents. I use it for that purpose as well.

We like the indexing feature.

The performance has been good. We haven't had any issues. 

The security has been fine.

Everything we need is already pretty much there.

It is very scalable. 

Technical support has been excellent. 

We are not missing any features. 

We would like it if we did not have to use another encryption solution to encrypt the storage. 

We've been using the solution for a couple of years. 

It's reliable and it performs well. it's stable. There are no bugs or glitches. It doesn't crash or freeze. 

It's scalable. We can increase storage as required. 

Azure Object Storage is mapped with a user. It's mapped to the server for storing files and all. So IOPS storage, probably we can talk 20,000 to 30,000 IOPS.

We monitor the usage based on there being increases.

Technical support is very good and very sound. 

Positive

There's not really an installation. It's a mapping solution. It's on the cloud. 

We have a common cloud team. They do any maintenance. It's a common cloud team who provisions the server, who manages the storage, who assigns the storage to the server. They do everything. We don't have a separate team.

I can't speak to the exact licensing costs. 

As a cloud-based solution, we are always on the latest version. It stays up-to-date.

I'd recommend the product to other users and organizations. 

Overall, I would rate the product ten out of ten. 

We use the solution on multiple levels. We deploy at the product level, production, and internal use cases.

The most valuable features of the solution are its performance and stability.

Since the solution is messy and heavy, it needs to be faster in terms of speed and latency.

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

I rate the solution’s stability a nine out of ten.

Microsoft Azure Object Storage is a scalable solution. Around 60 people use the solution extensively in our organization.

The solution provides good technical support.

The solution’s initial setup is a little complex. Around 15 technical staff are required for the solution's deployment and maintenance.

Microsoft Azure Object Storage is a stable product with good enough uptime.

Microsoft Azure Object Storage is an expensive solution. We need to pay a monthly licensing fee for the solution. We need to pay extra setup cost in addition to the standard licensing fees.

We use the enterprise version of the solution. I would recommend the solution to people who have a Microsoft ecosystem.

Overall, I rate the solution an eight out of ten.