When it comes to old applications, they may not be the most suitable environment for Microsoft's current focus on Azure and the latest technologies. It would be helpful if Microsoft could provide some guidelines or recommendations for transitioning from old to new. Currently, there is no established practice in the market for migrating from outdated technologies, and each company follows its own approach. At our company, we have devised our own migration process, involving a mix of traditional integration, following HI methodology, and transitioning from text services to virtual services. While Azure is suitable for modern stacks, there is still room for improvement when it comes to handling legacy systems. 

In my opinion, Microsoft should offer guidance on how to migrate from old technologies to new ones since the old technologies were also developed by Microsoft. Although they may have reached their end-of-life and end-of-support stages, it would benefit developers to have support for these old technologies.

At the very least, Microsoft should provide a clear path for migrating from old technologies to new ones. Since the old technologies were originally developed by Microsoft, they should offer support, especially considering that these technologies are still used by companies like Linea, with whom I am currently working.

The size of the solution needs to be reduced. Currently, we have 1 gigabyte of data in 23 units. However, the expected data volume is around 1075 terabytes. So the size needs to be increased accordingly. If it's not properly sized, it takes around 7 to 10 days to transfer the data. The goal is to reduce the time required.

Increasing the storage capacity is necessary, and we also need to reduce the transfer time. Currently, it takes around 7 to 10 days to transfer the data, and sometimes it takes even longer depending on factors such as the data version, security processes, and other complexities. We also need to consider firewall rules and similar aspects. Time is another important aspect to focus on.

The support provided to partners is very generic, and finding a Microsoft specialist can be difficult to get on calls. The solution is straightforward with simple application migration, but plug-and-play AI is not involved simultaneously. There needs to be human intervention for the migration. It can be automated from end to end for SMBs, reducing cost and time for SMBs.

The device must be transported off-site before the data is uploaded into the Microsoft Azure Cloud.

On an enterprise level, a per-user license for more than 1,000 users is very costly.

I think it's a single node solution. If it can be spread out across more of the enterprise and have more segregation in its virtual environment, that would be good.

For me it doesn't work well, so I work in Microsoft and non-Microsoft shops. If you're a Microsoft shop, I would – undoubtedly, blindfolded – say go with Microsoft Azure Data Box. But, if you are a non-Microsoft shop, to use Microsoft Azure Data Box, you would need to integrate it with your other vendors, and whether or not that will be possible will depend on the platform or platforms that host them. If a specific vendor is hosted on AWS and you are on Azure, you have to pay for the data and there is no way around that.

I am not confident in this device's ability to perform a network backup in our data center.