Azure Backup is suitable for companies of various sizes, with varying amounts of data. The cost of the investment should be thought out carefully so that there are no bad surprises with unnecessary files going to Azure Backup. The interface is friendly and easy to configure and it does not require your company to have a backup expert. It is highly recommended for companies with smaller number of servers and better if the servers are already running in an Azure environment.
Blob storage is well suited to hosting/sharing zipped files rather than several smaller files, as folder enumeration/listing is not supported. Files uploaded are case-sensitive, so users need to be educated on the correct naming convention format if they are delegating the file-sharing process outside of IT.
Azure Backup is fast! Coupled with the fact that Microsoft created Azure and Windows - these two operate phenomenally together!
Administering the backups inside of Azure is a breeze. The ability to mount, restore entire backups, or recover files, has been made very easy. You do not have to download any media to recover something, you do this all in the cloud and it gets mounted in Microsoft's systems. Making this process less than a quarter of the time you would have spent with your 'other' backup solutions.
Backup vaults should ask if you want to send notifications when you first set it up, there have been a couple of times when I noticed a month later that, backup job failures were not configured to send email notifications.
If we are transferring huge amount of data (outbound), it can get quite expensive.
With new features being added constantly, although a good thing, at times it becomes difficult to keep up with the changes. Documentation needs to keep UpToDate and should include best practices.
Performance can be improved especially when it comes to cold storage.
Blob storage is fairly simple, with several different options/settings that can be configured. The file explorer has enhanced its usability. Some areas could be improved, such as providing more details or stats on how many times a file has been accessed. It is an obvious choice if you're already using Azure/Entra.
One of the differentials of the solution is the high level of guarantee and support of the Azure Backup solution. Microsoft is a reference in a technology company with a highly trained support team and helps us with any questions or technical problems with the tool. Service is fast and efficient with trained engineers.
Microsoft has improved its customer service standpoint over the years. The ability to chat with an issue, get a callback, schedule a call or work with an architecture team(for free) is a huge plus. I can get mentorship and guidance on where to go with my environment without pushy sales tactics. This is very refreshing. Typically support can get me to where I need to be on the first contact, which is also nice.
Azure Backup works on Azure, the most famous of the cloud systems that the whole world has switched to, which is now a very large part of the Microsoft ecosystem that we have been used to using for years. Therefore, it is less tiring to use the additional service of an infrastructure that we already use, even if it is a part of it, which can be easily integrated with existing systems, which is one of the most important issues we IT professionals pay attention to. For this reason, we wanted to swim in familiar waters instead of another brand.
Azure Blob Storage is the best choice to store files when the app runs in Azure. It also has some advantages over S3, like Shared Access Signatures, that make it easy to control access to files directly via a URL. Azure Blob Storage is very fast and we have not had any major issues with it after using it for several years.
