Microsoft Azure Object Storage Reviews

I think it is not an improvement from the tool, but we were able to arrange our layers on the data lake using objects and a best practice for speeding them up or for making partitions in objects to protect against security vulnerabilities and increase the performance of data access. I don't think there are improvements in our company from the use of the tool. It is just the best practice that we are using in our company.

Microsoft Azure Object Storage makes some valuable compliance certifications for healthcare, and we need to obey the compliance part. In the healthcare sector, we have HIPAA, and in Brazil, we have LDPD compliance, which is similar to GDPR compliance. When we have to make proof of data access, proof of deletion, or datasheet reading, we can do it all easily with Azure.

Microsoft Azure Object Storage is like other cloud providers. It is just a simple object storage and the first kind of cloud product in the market. Amazon started off with S3, but our company didn't see any advantages against other competitors with the product specifically.

I believe AI will be available in the tool, but we don't know whether such a feature exists. We didn't use AI in our case to see if our team and our customers would see the difference during deployment.

The tool doesn't offer Microsoft Copilot and Microsoft AI. It would be great to see Microsoft Copilot and Microsoft AI in Microsoft Azure Object Storage. When you speak about Microsoft Azure Object Storage is a new kind of database. You have the better parts from two worlds, which are the vector and index features, and you can use them for your products without any migration or any other condition. It will be good to be tested.

I have been using Microsoft Azure Object Storage for three years. My company develops solutions, so I am a Microsoft customer.

The scalability of the tool has no limits.

Considering that we have many direct and indirect users, I would say there are 100 users.

In the future, we want to multiply the number of users of the tool by ten times.

For my team, the first level of support from the tool could be better. For the technical account, the tool's consultants are very good as they bring in some of the best practices into our company, and so we have the solution's validated design. I think the type of support depends on the customer, but for our use case, we try to follow all the product's recommendations. I rate the technical support a six to seven out of ten.

Neutral

I use Azure Service Fabric, some storage pools, and all things related to Microsoft.

The product's initial setup phase is similar to the processes required to follow for other tools in the market. I think Azure's initial setup phase is harder than Amazon or GCP.

The product's installation phase has some limitations. I have to set up more parameters on Azure than other tools. I had some issues with the tool's setup phase.

Most of the time, when we deploy the tool on a complete rack and stack, we write every line in Terraform. I think every time you need to deploy the tool, the first time, you have to keep it totally focused, so it is a manual process.

The solution is deployed using a public cloud. We may change our model to a multi-cloud one, but it is not like a hybrid model.

I think the ROI depends on the product. When it comes to Microsoft Azure Object Storage, it doesn't deliver entire value to our customers. The product made is totally fit, but for the market, I think we are not able to get hold of the market fit.

The price will be more competitive when we increase the time spent using the tool. For our company's size range, I think the price is okay.

The tool's maintenance is not complex. We have deployed an observability platform on Microsoft Azure Object Storage, and all the parameters in our dashboards are not complex.

I rate the tool an eight out of ten.

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.

The storage account is one of the primary components in all implementations, including cloud implementations. It is a common resource in Azure.

We mostly work with Blob Storage, and it is a very good resource for unstructured storage. Blob Storage is one of the best resources in Azure for storing unstructured data such as files, video files, audio files, and Excel files. Currently, Blob Storage is the cheapest and best solution, with very good features for unstructured data.

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.

I work with an Azure storage account that includes a blob bin and file storage. I have used Azure Blob Storage for almost five years. Also, I am not sure if we are partners with Microsoft since I joined a month ago.

For stability, I rate it a nine out of ten. This is because it offers one of the best features. Also, I have not faced any complaints regarding the storage account in my five years of experience. There might be other resources I feel that I couldn't access or have some service-related issues. But, I didn't face any issues with the storage account.

I rate the solution nine out of ten in terms of its ability to scale. Since it is a management service, we should not bother about scaling. This is because we have a very good scaling policy for management services. As I recently joined the organization, I am not aware of how many employees are currently using this solution.

The technical support you receive depends on the plan you choose, whether it is the basic plan, standard plan, or premium plan. In my current organization, we have a premium plan for which the technical support is awesome. I raised three tickets with the technical support team while using the premium plan and received the best support from Microsoft. So, I rate the technical support a ten out of ten.

Positive

I am working with AWS, Azure, and GCP, but my major contribution to the cloud is towards Azure.

It is a very simple process.

Currently, it is a flexible price policy.

Amazon S3 is equivalent to Azure Storage accounts, as they offer almost the same features. Based on my experience, I find Azure to be a more comfortable tool to work with compared to Amazon S3. The UI is better designed, and I could easily understand the features and other things. Therefore, even though the two solutions are similar, I rate the storage account solution higher than Amazon S3.

It is one of the best features or resources, especially for people who want to use Blob Storage for unstructured data. For us, it is a very cost-effective resource since we can understand it easily. I haven't experienced any issues with this solution for the past five to six years. I rate this solution a nine 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.

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.

We use it basically for binary or any text data that needs to be there. Or if we want to solve something like data redundancy problems.

And some image processing. We have also done some image processing in one of the POCs. So that's one of the use cases for us.

The index search and block storage are valuable features.

In future releases, I would add something like a better lifecycle management system, and for integration purposes, I would add some stuff related to newer concepts like data products and databases. I would like to have a seamless flow between those things.

All my companies that use Azure use Object Storage.

More than 2,000 people were using those kinds of things.

The initial setup is usually easy.

It is neither cheap nor expensive. So, the pricing is in-between. 

I would recommend it. But I would also suggest that you check your requirements, and then we can discuss things like performance optimization, security, and stability. Also, consider cost optimization and potential interruptions. Once you're satisfied with those things, it will be easy for you to go for it.

Overall, I would rate the solution a seven out of ten. 

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 use Microsoft Azure Object Storage for file sharing.

Microsoft Azure Object Storage is flexible and has all the features we need.

The solution’s stability could be improved.

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

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

Microsoft Azure Object Storage is a scalable solution. Around 1,000 users are using the solution in our organization.

The solution's technical support is good.

The solution’s initial setup is easy.

We have seen a return on investment with Microsoft Azure Object Storage.

We don't need to pay for the solution's license.

Microsoft Azure Object Storage is a cloud-based solution. I would recommend Microsoft Azure Object Storage to other users.

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