The solution could use a couple of security features. They still have a lot of other features and everything is coming along quite nicely now, however, I would expect more features in the near future. We'd like more policies and authentication.

One thing that needs improvement is authentication. They need to improve the integrated Azure Active Directory for the enterprise level. For single sign-on, we can try any authentication or portal for Block Azure Function AKS. For example, if you're an administrator or user contributor, you will generate a token, then your internal middleware connects to any Azure Cloud service. You need to generate different credentials for each service. We cannot use the same token.

Some services like Azure Key Vault support a single token for access that you should be able to use for the Kubernetes site, but some services are not supported. Authentication should be centralized. My understanding is that the data on this file path is streaming. Whenever you get this data, it is converted to streaming ByteArray and Base64. The file path is another security vulnerability.

Azure Block Storage is mainly used for streaming data nowadays. Companies are moving to digital platforms. They stream data from IoT, mobile, offline sources, and other systems. There are different styles and formats, including unstructured, semi-structured, relational, and platform data, so we cannot use a single database for all requirements.

We cannot say to a client, "Sorry, I need only to support this product in JSON." If we say that, competitors will dominate us. We must be prepared to accept any kind of free input or solution from clients. Then the Block supports any semi-structured data or structured data. If you go with File Storage, queuing or messaging will support storage, and the Block will support videos or images.

The solution should provide more training so that we can learn about and take advantage of more features. As it is, right now, we have to pay for training.

It could be easier to use. 

The product is not as stable as we would like it to be. 

The security is poor, and the sharing model is confusing, conceptually. I'd prefer not to use it. I'd like a user-friendly web interface and a better security model. 

As a technology product, it's always evolving. There are some feature challenges from my side, however, I am hopeful they will fix the issues. 

The integrations right now are limited, however, we are hopeful this will improve as the cloud continues to develop. We would like to see more capabilities in specifically hybrid scenarios. There are some third-party tools in Oracle and Linux we'd like to have access to via this product.

We'd like more failover capabilities or data recovery options. 

Microsoft Azure Block Storage could improve the SFTP. The SFTP can be used for exchanging data between two parties and it works but Microsoft is new to this market and they could be a lot better in this area with its features.

The querying could be improved in the storage system. SQL is a fundamental technology but there are only partition rules and row IDs, and it is slow to query the data.

The day and time stamps are not indexed in any way which makes it very slow. Additionally, if you wanted to remove all the data over a month, there is no option to do so. There are areas that the solution can improve on in the future.

The cost of the solution has room for improvement. Microsoft Azure Block Storage is priced higher than alternative solutions.

The solution needs a direct connection to visualization. Power BI connectivity on this platform is not that great. We need a direct connection to any of the visualization tools. There should be more BI integrations.

The solution's downside is related to its documentation, which I believe can be difficult to navigate because it is hidden between or within other pages of the product's manual. There are not a lot of core resources around to dig deep into when it comes to Microsoft Azure Block Storage. A user must do a lot of research around the product, which is a slow process.

In Microsoft Azure Block Storage, navigation through its documentation can be made easier. The documentation should also contain more examples to help users.

With Microsoft Azure Block Storage, sometimes in our company, we have noticed some errors in our error logging and management platform without providing much context as to why the error occurred. I think maybe more descriptive error messages will be helpful.

The user interface is very difficult. It is not user-friendly. We need time to understand the product and create a container. It would be nice if the user interface were made simpler. The documentation is difficult to understand. There are no videos on the website. It is difficult for a new user to understand the solution.

There is a folder inside the block storage. I am not able to delete the folder completely from the portal. I need to go delete the file inside and then I will be able to delete the folders.

We don't delete the other tools from the folder directly. There's no folder deletion option in Azure Block Storage. It would be nice if they could update this. 

I find the user interface of newer versions, particularly, the flows, not user-friendly. The UI of Azure’s initial version was very comfortable. I didn’t have to remember floor menus. I knew where I had to go to see the logs or grab configuration parameters.

I found that everything works fine in Microsoft Azure Block Storage; though it may be because I have less experience with it, I cannot give any areas for improvement.

I want to see my region added to the data center. I'm in Africa, and if a data center is specifically added under Central Africa, that will reduce data latency when accessing data. Right now, you can only find the USA, China, Europe, South Africa, and Egypt, but no Central Africa. It'll be great if Microsoft can add my region or location as a data center for Microsoft Azure Block Storage. Doing that will respect privacy, too.

The feature that requires improvement is the hierarchical naming step. Enabling this step could provide access to certain features that are currently missing.

Another area for improvement in Microsoft Azure Block Storage is the cache feature. So whenever we upload a file to block storage and then download it to check whether it was uploaded successfully or not, it downloads the older file due to caching. But when we directly download the file without clicking on the preview options, it shows the correct file. The cache issue needs to be addressed to ensure that the correct file is downloaded, especially when it's done manually into the local storage. Because I have checked in other services as well, and the issue only arises when we download it manually into the local storage.

There is a drawback or limitation to the GRS storage feature because depending on the amount of data, it could take a lot of time. There are a lot of steps from the application perspective, so it's not easy and straightforward from a business continuity perspective. That is one of the limitations I see in the solution. 

It's about the time it takes to revert back. The failover takes a couple of minutes but then it takes a lot of time to fail it back to the primary region again, so you have to do a synchronization again. That's a bit of a challenge because if it contains a lot of data in terabytes, the cost to do a replication again but reverse the direction from secondary to primary is a bit extra. Obviously, though, this only happens when there is an out, when a DR is involved, so it's not very often that companies would come across this. It's only in the worst case scenario. 

It's not a big thing, but some companies have limited time for their DR, like there's a RPO, or a recovery point objective and recovery time objective, that is very short. In that case, this product may not be suitable or may not meet their customer's requirements. That is something that Microsoft should focus on, to bring the time down or make that process, the DR process, a bit easier for this product. Maybe as they continually improve this product they can add improvements in this aspect to reduce that DR time, recovery time, for the solution.

Azure had the Blob version prior to Block. Azure also realized that Blob Storage did not really have any main space. So, that was a limitation of the Azure Blob product. But that is also the reason why they decided to develop the Gen2 version, which puts back all the right structure for the storage and capacity.  

So, it is good to explore Gen2 as another solution. I think most of the users would eventually move from Blob Storage to Gen2 only because of the space limitations of Blob.  

You also do not see the kind of folder search capability in Blob that you might expect. Like when you are in windows, you can just go to a particular folder and you can browse within that folder and you can go into subfolders and search there as well. That feature is kind of missing in the Blob product.  

So the inability to easily search subfolders and also the space limitation of Blob are really the biggest limitations of the product.  

What I would like to see in the next release — and I am not really sure if it is possible in cloud solutions — but it would be nice to provide a feature for being able to distribute large files.  

I cannot recall coming across any missing features. 

I have experience in resolving various issues, however, troubleshooting can be sometimes very difficult as items are not very well documented. If the documentation could be improved then it would be very good. Right now, if you face a question, you have to guess how it works or you have to test your hypothesis. This would be great for newer, more basic users. 

The solution’s user interface could be improved.

The solution should also support unstructured data. There is a different file format for unstructured data. It would also be good if the solution notification features.

The performance of Microsoft Azure Block Storage needs improvement because it's laggy. My company used it in different places, including the Microsoft browser, but it still lags.

Pricing for the product is another area for improvement.

Microsoft Azure Block Storage also has a lot of limitations on file sizes. The rendering and loading times also need improvement. Sometimes, Microsoft Azure Block Storage crashes, an issue that needs to be taken care of promptly, but Microsoft hasn't been able to do that for a very long time.

It would be nice if the Azure Block Storage could integrate with microservices-based mobile apps, too. 

The tool could be cheaper.

Microsoft Azure Block Storage's stability needs improvement. 

I encountered a challenge where certain metadata was located on a secured network that could only be accessed through a VPN. As there was no direct connector available to reach the private networks that require VPN access, we had to rely on manual effort to access the data. This could potentially be addressed as an area of improvement, especially with regard to accessibility issues where data is only accessible through a VPN connection.

It appears that the solution we are working with is already in a beta version, and we have been managing a large volume of files by pulling them in at fixed schedules to determine whether a file is new or has been modified, we need to obtain the last modified date and compare it with the previous value. However, there is a new concept of a rolling window that can automatically detect newly arrived files and push them into downstream processes. From the logs I have seen, it appears that Microsoft is actively working on simplifying the file management process and reducing the need for engineers to manually pull files using specific logic. This includes developing a feature that automatically identifies new files and distinguishes them from old ones based on their metadata. It would be helpful to have this feature implemented.

Microsoft Azure Block Storage can improve the configuration to be more user-friendly.

The solution's user interface can be more user-friendly.

I have used Amazon's solutions which are better than Microsoft's. However, since I have predominately Microsoft solutions it is a better choice for me to use another Microsoft solution.

The performance could be improved, but all the services in the cloud are improved every week.

The solution can be improved by including quicker hard drive access and larger bandwidth as part of the standard licensing fee.

The implementation can be quite technical.

We would like the solution to lower the costs as much as possible. It’s always better for the customer if it is less expensive.

Although cheaper than Amazon, licensing expenses for Block Storage are pretty high. 

Microsoft Azure Block Storage could improve by allowing the switching of the hot tier to the cold tier.

Microsoft Azure Block Storage could improve by having integration with Amazon AWS. The file transfer could be easier.

There have been problems with integration, but it's getting better.

Encryption, data analytics and behaviour analytics can be improved. Encryption and usage analytics optimization, built into the setup, can take it to the next level.

When I installed Azure Explorer on my system, I connected easily, and, for uploading data and uploading any value or any files from there, it was very easy. However, when it's there in Azure Blob, Azure Portal, then uploading, downloading, or viewing the file is a little bit difficult. That's the part they need to improve. Downloading and uploading could be easier.

They could create more readability of files. We can use other solutions in desktop versions and then we can connect those Azure files. However, if anyone is working maybe in Linux or other things, then the Azure Portal is best for them. The readability is easier.

I'd like them to improve the features of data gathering - sometimes you need to get the data from the block and it's usually very expensive.

Improving the pricing structure would be beneficial. If the pricing could be more flexible and reduced, Microsoft Azure Block Storage would likely see increased usage.

One of the biggest challenges on Azure infrastructure is that sometimes we don't get what we want. Either we have to wait for it or contact support because something is not working for us. Most of the time it works fine. But sometimes, when we want something critical, apart from block storage — we want to increase the capacity of the VM or we want to increase the cores of the VM — we have to wait. We get a response from Microsoft from a North American location. We want to host everything within the UAE. But we are redirected through North America or Europe. That is a challenge with Azure. It's the system availability that is the difficult point.

Also, billing is an issue. We have had a lot of problems when it comes to billing. We started working with minimal resources and we opted for pay-as-you-go mode. Microsoft needs to invest in some resources to improve the billing part. It's not about the money, but the visibility. I see a lot of invoices, but I don't see whether we have paid them or not. And if we have paid, I don't see when it was paid and through which credit card or account we paid. I see invoices, but I don't see the information related to those invoices.

The solution could have better archival policies and localization of data.

We need to do versioning each and every time, that is, check-in and check-out. If a person forgets to do that, then there could be an issue in the replacement of that particular object in the storage. It will be great if it can be automatically managed.

Microsoft Azure Block Storage should improve its stability. 

I would like to see an improvement in the networking and cost transparency part. What I mean by this, is that we provide certain workflows for our customers and we usually calculate what is local, but even then it's not really upfront. We must know what the usage will be in DMs. So the price is different, and that is where provisioning and cost transparency comes in. We must know what it will cost in the OPEX work that we do. We do have some cost analysis, overdose cloud, but still, it's not always the right amount that's reflected for our customers for each application or each analysis that they want to do. The invoice type is therefore different for each client.

It should be easier to deploy.

We cannot properly check the daily cost in the Azure portal. I'm going to raise a ticket to the Microsoft team as it is an Azure portal problem.

The technical support could be improved and the price could be more flexible for clients. 

There are capacity limitations that could be expanded.

When freeing the backup capacity on our disk, we have to create another block storage and integrate with that. The limitations may be an issue with the customer.

It should be more flexible for customers. For example, if a customer needs 10TB of capacity, it should be flexible for the customer to expand to that capacity.

I would like for the next release to replace the CDN being used for content delivery, there is currently a rather long delay.

Uploading of data could be improved. Currently, the only way you can upload your data is by using their storage explorer. You need to use a command line to do that. Then, maybe you can go online and you can use their explorer to check to see if it's there. If they had a third-party application to handle the upload, it would be better. Many people aren't familiar with command lines for uploading data. It makes it more difficult for many users.

The pricing is a bit high.

Azure Block Storage could use more capacity.

The biggest problem with Azure is the price. It's cost too high.

Technical support needs improvement.

In terms of improvement, it could use better integration with non-propriety tools. Azure pushes you down a data factory road for integrations but data factory isn't always a scalable, viable solution, particularly when using large numbers ofconnections to IoT solutions. 

The scalability of the product is an area of concern where improvements are required.

Sometimes, the support team is not aware of the issues that the tool's customers face. I feel that from any improvement perspective, the support team should be aware of the product-related issues that could arise from the customers' end.