Veeam Data Cloud for Microsoft 365 Reviews

We use this solution to protect our mailboxes, our data, and Office 365.

We use it in our office as well as for our customers who have Office 365.

I use it in a multi-tenant way.

It does what it does. I want an additional copy of my data in the Office cloud and it works. I can restore the data.

The interface is quite okay and the procedures are clear.

There are many applications in Office 365 and new applications are being added. They keep up with all of the data.

Security is the most important feature. When you are working in the Cloud security is very important.

They may have made changes recently, and may already have the two-factor integration, and following the security upgrades from Office themselves.

I have been using Veeam Backup for Office 365 for approximately two years.

We are using the latest version.

It's a stable solution. We have not had any issues with stability.

It is very scalable.

While I still have customers who are using Office 365, I will continue to use this solution to protect their data.

I am very happy with Veeam's support. They are good and very responsive.

The initial setup is straightforward. It's is very easy to install.

It can be deployed in less than an hour.

I completed the installation and deployment myself.

I have a per-user license for the number of users and the mailboxes that I have.

Definitely, I recommend using Veeam Backup for Office 365.

They are adding SharePoint and OneDrive as well as other integrations.

I would rate Veeam Backup for Office 365 a nine out of ten.

Our primary use case is the backup of 365 objects and emails. At the moment, you are just testing Veeam. We are using it for production, and we are running a few productions on APIs.

We are able to store it on various cloud providers such as Amazon S3, Rocket, Azure, and IBM Cloud. It can also do on-premise integration, and we are able to use storage from on-premise. We are also able to recover data.

It is a really good and intuitive solution. Veeam has developed a fantastic product. I've never seen anything that I don't like about Veeam. It looks like a very complete solution. It is really mature, simple to use, and quite interrogative. It also has APIs for writing scripts.

Its price could be improved.

I have been using this solution for a year or two.

It is stable.

It is scalable. We currently have about a hundred users. We are currently testing it, and we are looking at expanding to almost 2,000 users.

I have contacted them, and they are good.

It is straightforward.

Currently, we have four engineers for its deployment and maintenance. We have the same number of engineers for NetApp.

Its price is a little bit high, but it is a fantastic solution. It is more expensive than NetApp.

We are already using NetApp, and we are currently testing Veeam to see which one has a much better use case. They are more or less neck-to-neck in terms of features and the simplicity of connecting to Office 365. 

Veeam has, of course, a little bit more features than NetApp. I see a lot more options in terms of where to store your backup, but, in terms of features, they're both good products. From the price point, Veeam does seem to be a bit higher than NetApp.

I really like the fact Veeam has integrated into a single pane of glass. That's one thing that NetApp should do in the future. Instead of running it as a standalone backup solution for 365, Veeam has got it right in terms of simplicity and putting everything in a single glass for access purposes.

I would recommend both Veeam and NetApp. Both of them have got it right. The only difference I see is in the management. For Office 365, we have to go into our web console which is directly integrated on the cloud, which is good because it gives that differentiation. At the same time, if you're an administrator and you're managing backups, you should have the simplicity of having everything in a single pane of glass. 

I would recommend using the Veeam console to someone who is doing Veeam on-premise or cloud backup. It gives you the simplicity of having everything in a single pane of glass. I like NetApp, but I would've liked its integration into the Netcenter. That would really raise the game for them in terms of giving a full position in a single pane of glass. However, if there are people who are using other backup solutions and they just want to purchase Office 365, NetApp is also a good product. I would recommend both to anyone, and let them feel for themselves, regardless of price, how they scale, what features they want, and how they want to store their backups.

I would rate Veeam Backup for Office 365 a nine out of ten.

We have Veeam in place for Office 365 backup and restore. We use it for mail backup and restore, SharePoint, and Teams. We were still struggling with the backup of OneDrive, which is still a discussion. We are using its latest version.

Its ability to restore at the item level is very valuable. It is very strong at that. In the past, we had to restore a lot of data only for a couple of items. We can now restore an item as well as an email, which is good for productivity.

When you add a new site for backup, it gives you a notice that there is a new site, but the way you select that and configure that could be slightly better. It works, but it is not always very clear. For example, for the URL, you need to hover over the title or the name of the site. You should see it immediately on the screen. It should have a better user interface for selecting what you want to back up so that you get a more clear overview of the sites that are there and the ones that you want to combine in a backup.

Its user interface should be more user-friendly. It has a lot of scrolling and doesn't give you a complete overview when needed. That's the main thing why it is not very user-friendly. It should have a better user interface. 

I have been using this solution for two years.

It has been running for two years, and it has been stable. We only had an issue this week with connectivity with AD, but that's normal.

We didn't try the scalability. We made an agreement in the beginning with a view to the end. We paid more than what was necessary. We ran it for so many users for so many years, and our manager at that point thought that it was a good offer. We have a license for 750 users, but we have approximately 550 users currently. We aren't using all subscriptions, so in the end, we may have paid more, but I should see other offers as well. 

Everything went fairly smoothly from a technical point of view and from a point of view of implementation and other things.

Veeam was the first cloud backup we used, but we have several other systems in place. We have EMC's backup and recovery solution. We are now in the middle of a global Office 365 project, and we decided to use Altaro for backup and restore there. We decided on Altaro because, from the point of view of the total cost, Altaro looks cheaper than Veeam, but we can really tell that after half a year or so. In terms of features, they are very similar.

We don't have any experience with Altaro. They provided us a proposal for two years, which we found to be too long because we don't have any experience with it. We first want to be convinced that Altaro is a better option than Veeam. Therefore, we decided this week that we go for an agreement for one year to get experience, and, when we have a good feeling down the road, we will go for a commitment for a longer time.

The initial setup was straightforward. It runs very fast.

We had some support from a supplier.

We decided on Altaro because, from the point of view of the total cost, Altaro looks cheaper than Veeam. Veeam has a lot of costs that are not clear when you start it, which makes it less flexible than Altaro, but only after half a year, you can be really sure that you made a good decision.

I would rate Veeam Backup for Office 365 an eight out of ten.

Our primary use case is the backup of our education-related files and data.

The most valuable feature is the integration with our Teams environment.

The environment mainly consists of PCs, although we have students and a few teachers that use Apple computers. Sometimes, we have compatibility issues related to this and the problems can take a long time to solve. Faster response time to complaints that we have had would be of great appreciation.

When you work with these cloud-based systems, the response time could be better. I never take anything for granted. When people complain about something, I always check in three different settings with different internet connections and different locations. I find that when it comes to Office, the response time could be improved quite a bit.

Some additional training materials would be helpful.

We have been using Veeam Backup for Office 365 for a couple of years.

This product is very stable. It's not perfect because all computers have a tendency to break down at one point or another.

This system is pretty scalable. I find it good because you can start with a package that is not very big, and then just add to it as much as you like. Also, you can remove things that you don't like or don't need.

I find that technical support can be improved because for people who are knowledgeable, it is good, whereas for people who are not, the support is too technical.

Our staff is made up of rather strong individuals with personal opinions about software, so we've tried to focus on fewer solutions with the widest application.

For the past six months, Microsoft Teams has been of the biggest importance for us, both in terms of teaching and meetings. Our meetings include both in-house and outside. Office 365 is one of the things that is connected to that, and our files need to be backed up regularly.

This is definitely a product that I can recommend.

I would rate this solution an eight out of ten.

We are using this solution to back up our users' mailboxes, that is, Office 365 mailboxes.

It has got all the features. You can restore a mailbox based on an email or a calendar or based on all the emails. A user can also get access to restore the mailbox.

They can provide a dashboard for sizing. This feature might get included in the next release.

I have been using Veeam Backup for Office 365 for the last two to three years.

It is very stable.

It is easily scalable. We just need to add the licenses. We have around 50 users who use it on a daily basis.

We get support from the vendor. We didn't face many issues to evaluate them. Whenever we contacted them, the issue was fixed immediately.

The initial setup is pretty simple and very straightforward. We finished the deployment within one or two days.

We did the implementation. We had received the training for this solution. Its maintenance is also done by us. We also get support from the vendor.

We looked at a few cloud options. When we did the comparison, we found it to be a cost-effective solution, and it included everything.

I would definitely recommend this solution. It is working fine, and there are no issues. We are happy with its features.

I would rate Veeam Backup for Office 365 a nine out of ten. 

We use Veeam because — while Microsoft provides a terrific environment called Office 365 — they do not back up files that are stored there. The files most customers are concerned about are OneDrive and SharePoint files, but they often overlook their mailboxes and the Exchange piece of Office 365. It is the customer's responsibility to actually back that data up, which Microsoft does not do a good job in sharing with you. We had moved all of our file server shares to OneDrive and SharePoint, and we were just over a terabyte of data. To make sure they were being backed up properly, I implemented Veeam Office 365 Backup.  

It has given us some peace of mind when it comes to backing up Office 365 files that Microsoft does not include in the 365 backup structure.  

What I like in this particular module within Veeam is that it allows you to restore mailboxes selectively. Instead of having to restore all the mailboxes that you have backed up, you can be more targeted. Let's say you had a request from the vice president to get their entire mailbox restored. They are typically the guys who blow up their mailboxes. I could restore just their mailbox from the backup and no one else's. But it gets even more granular as I can also restore individual folders inside their mailbox. It gives you a lot of flexibility in terms of what you are able to restore.  

In SharePoint and OneDrive, you are able to restore down to the file level, which is really handy. It gives you a lot of restore options. Their GUI is just stupid easy to use. You basically go in, you browse the different modules — whether it is Exchange or SharePoint or OneDrive as the parent — you click on your tenant name, then you go to exchange the mailboxes, and then you go under the individual user that you want to restore. That could be the whole mailbox, or a folder, or whatever. It just takes a couple of clicks and it is done. It just works.  

One of the things that should probably be improved is the pricing model. The price is based on a per-user charge. I wish that was not the case because it is not really in use by most of the users. It is not all that often that people need something restored. I do not know how they would change it exactly, but it just does not seem appropriate. If they can change their pricing model, that is only going to help to get more people to adopt it. They could make it more affordable.  

A better pricing model would just make sense and be better for some companies. We do not have an issue, thank goodness. But some companies might be a little bit strapped for cash. As a solution that completes their backup regimen, it is a requirement whether they know it or not. You hate to see the pricing make the decision and exclude people from something that they essentially need. If they could make it more affordable, that would be better for everybody.  

As far as adding features, unless Office changes, they do not need to change their feature set. It is already feature-rich. It has a really nice GUI and it is very easy to manage once you get logged in. So no, right now I would not change anything. Change is not always a good thing.  

I have been using Veeam backup for a couple of years.  

The stability of the system is awesome. It all depends on what the underlying operating system is. If you are running a Windows Server, that is your biggest worry. But if you are doing all of this in Linux, then it is solid.  

The application itself is solid. You do not have to upgrade memory. You do not have to do anything like that. It is very solid. Assuming your underlying OS is running well — even if it is Windows — and you have got the current version, that is great. The product itself is very stable. I think Veeam goes a long way to validate and test this product before they send it out to the market. I find it to be very good and reliable.  

As to scalability, right now, if you wanted to expand usage because you have more users, you have to buy more licenses. There is really no limit. The only limit is your wallet. That is also why I like the idea of a different licensing model: so I do not have to constantly consider the number of licenses. That cost depends on how many people you are going to onboard just makes it cumbersome. You could pay upfront each year, and try to figure out how many licenses we are going to need, but that is just a guess. We do that and I have never taken licenses back, so I do not know how good Veeam would be with that type of request. But that is another reason why a different licensing model makes sense: it would allow me to scale a little bit easier. You change the number of users in an organization far more frequently than you change the number of cores.  

Currently, in our organization, I would say there are about 50 or 60 users on Veeam Office 365 Backup. I would call that relatively small. Veeam has lots of other companies as customers that are way larger. There are integrators out there that include this stuff in modeling for companies big and small. I'm pretty confident that it scales easily even for large organizations.  

We do not have anybody on staff to deploy and maintain the system. It is just another part of the architecture and one of the many hats that we all wear. After the set up is done, it is just a part of the monitoring checklist. You come in and get yourself all squared away. You check the backups — what completed, and what did not — then you check these backups to be sure everything backed up successfully. If it did, that is great. If not, you have to find out why. We have internal policies behind how we address failed backups. So there are a certain number of retries that we do before it leads to having to really research a failure as an issue.  

I have used the tech support for the product. They are all very good. They have a great website and there are a lot of self-help documents. That is typically what they point you to when you need assistance. But all you have to say is that you are not really so technical and you need a walk-through — even if it is stretching the truth a little bit — and they will help you out. Somebody doing the installation could download the right document, but even then they will walk you through it. It is quick and hardly takes them any time anyway.  

Of the other software that I used prior to Veeam for backup or recovery solutions, probably the most relevant is NetBackup from Veritas. We used the Veritas NetBackup Appliance. Veeam for Office 365 is more targeted.  

The setup for the product was straight forward. The actual deployment of the product was very quick. I would say it was inside of 20 minutes. After the installation, it has to go out and discover all the mailboxes and folders and stuff, and that can take a couple of hours. So I would say the amount of time it took in total was probably two or three hours. The actual keyboard time, was about 20 minutes. It depends a bit on how big the environment is. If you have a huge environment then it will take more than two hours to do all the discovery.  

We did the implementation all by ourselves. We did not need anything like an integrator or tech support or help from the vendor.  

I think the pricing model is wrong. Veeam itself is licensed according to the number of cores you have on your system. Maybe in pricing the backup solution they could just match that same model. So instead of having the Veeam license — which you have to have in order to use the Office 365 backup — and tacking on a per-user charge, they could base the cost on the CPU cores instead. Just tell clients that if they want the additional Office 365 Backup option it increases the cost by whatever amount pr billing period. It simplifies billing and cost tracking. Anything they could do to lower the actual cost of using the product would be good.  

But in the end, right now, the Office 365 Backup component is licensed separately per user. It works in conjunction with the basic Veeam license so you need that too, but it is a separate tool in terms of licensing. You can not get it independently.  

Before choosing this product, we did not actually evaluate any competition, which is not the usual due diligence. Veeam does not really have competition in the Office 365 Backup space. That really made the decision a slam dunk for me. It was the one product that solved the issue and it works.  

On a scale from one to ten where one is the worst and ten is the best, I would rate Veeam Backup for Office 365 as a seven or eight. Choosing between the two, I give it a seven. I have to ding them a little bit because of the licensing. I am really not thrilled with that.  

We've been using Veeam Backup for about a year. We get a lot of inquiries, whether it be from our partners or from end-users, who would like to backup their Office 365. They inquire about how to do so and the prerequisites, what exactly is required. Generally speaking, their concern is about how much storage is needed for the backup. Every company has a different backup policy, different RPOs, and different pre-pension policies. We help them determine how much storage they are going to need. That's basically it. That's how we deal with it.

A lot of customers have the misconception that when they host their data on the cloud, the cloud providers actually protect the data. Meanwhile, cloud providers are generally responsible for the availability of the service. The data is always the responsibility of whoever owns it. Nobody can ensure the data will always be there. So there are many news cases that happened. Sometimes people lose data on Office 365. For example, some emails get deleted and they seek the attention of Office 365. On average it has been discovered that it takes about 140 days to discover the email was deleted.

Employees can get disgruntled all of a sudden. There have also been hardware attacks on Office 365, even though there is cybersecurity in Microsoft. Nothing is bulletproof in the cybersecurity industry, so it's always good to have a second copy of your data.

A really good feature I saw is backing up company emails for the enterprises. This offers an easy ability to restore to the cloud.

The other really amazing part is that it doesn't just stop at Office 365. For example, some people have a hybrid setup. They have non-private exchange email software and then they have a hybrid with the Office 365. It is useful for that use case because it can back up both of them at the same time.

A lot of people when looking for backups usually consider a lot of sites. With the Veeam Backup application, you can have really good compression and deduplication ratios. That means you can save lots of space on your backup storage. With Veeam for Office 365 for companies that require long-term retention, they often complain about the capacity storage it might take. There's no deduplication on that level. Basically, storage capacity can be required to be huge in some cases.

But the good part is that exclusions can be made to save on the storage space. The general feedback I get from the market is that there is no deduplication.

The capacity storage is a challenge everywhere in the backup industry. The general feedback people are coming back to us about is that there is no deduplication based on it. There is compression which uses the native Office 365 compression, but there is no deduplication feature just like in Veeam Backup application.

I'm not sure technically if it's possible to deduplicate Office 365 dockets. However, I'd like to see native page support for Veeam Backup for Office 365 to be able to back up to the tapes. I'm at a company with long retention and I backup disk space storage, so it's going to cost me a fortune. Meanwhile, if I preserve a short term retention plan, like Backup, if I need to have backups for three years for example, then I'll need huge amounts of storage. Now storage can be expensive or it can be cheap. This base storage is useful for short time retention. For example, keep it for one month, and then you can archive it on tape for the rest of the year. So, this is not good in a situation where a company needs to restore from a long time retention, and tape is really inexpensive. 

I'd like to see Veeam Backup for Office 365 backup to tapes, support cloud object storage. Now, the new trend for archiving data is not just on tapes and data deduplication appliances. This is considered really old technology. Deduplication appliances are only fit for the enterprise customers but they can be expensive and save lots of data.

So the only real need for it is in enterprise but some small companies would like to archive their data for a long time. They find financial challenges to do so. Nowadays, they look to this new cloud object storage with cloud providers like Azure Blob Storage, Amazon S3, or IBM. That can really be useful for archival. So, basically supporting archive tier storage for the Veeam Backup for Office 365. Archive tier storage, whether it be the deduplication appliances, cloud object storage, or tapes.

But like I said, it's probably on the way. Veeam distributes new products as well. It's not as old as Office 365 for the market. When you look at Veeam Backup and Replication and how long they have come, it's probably on the way there. And there are programs to do all that I have mentioned if the client is also using Veeam Backup with Replication. You can basically install Veeam Backup for Office 365 with a VM and just back it up using the Veeam Backup with Replication, then you can get use out of the deduplication and archive to the cloud by a virtual machine. There are workarounds too.

Although the Veeam Backup for Office 365 doesn't natively support all the things that I told you about, like archiving to tape, deduplication appliance, or cloud object storage, it can always be installed in a virtual machine and then that virtual machine can be backed up by Veeam Backup with Replication, which supports all of this. It's considered a workaround, not native support.

To be honest, it's pretty stable. It's the third major release for it. It is showing lots of improvements. Not any issues with the product at all, whether it be with backing-up or the servers. Office 365 itself is pretty new to the regional market, where we are. It's not a new product, but its prevalence is starting to hit Saudi Arabia distribution.

I can't say I've used it that much, but I have used it enough to consider it a stable software.

This is the big one about Veeam in general. The good part about Veeam is that they make modular solutions, so you can install Veeam Backup for Office 365 and Veeam Backup and Replication in one single server. You can do an all in one installation, and roll it out.

Some scenarios may require that you scale-out. You can dedicate modular components to specific services. In that case, you need backup for Office 365, that's not like Veeam Backup and Replication.

There are basically three major Veeam components for Office 365: Backup Server, Backup Repository, and Backup Proxy. In short, Backup Server is the granular solution. It's basically responsible for managing the tasks and jobs of all the other components. Backup Proxy is basically the muscle of the solution. So, this is what actually is interacting with Office 365 and doing the actual backup. It is coordinating Veeam Backup Server to do that. Veeam Backup for Office 365 Repository is where you store your backups. Any storage that is presented to the Windows operating system, you can use as a storage for the Veeam backup storage for 365. So long as you have internet connectivity, no firewalls in place (or specifically the required firewall forced to be open would be the Office 365), and you have the administrative privileges for Office 365, it's an easy task.

There are a lot of companies that use Veeam backup for Office 365, and those companies range from 15 users to 5,000 users. There are a few use cases. Some companies have compliance standards that force them to have a specific backup policy and a specific retention policy. That is kind of hard to do manually. Some people just prefer to have a solution that also meets that and makes it easy. Some people just want to take control of their own details. Some people are actually upset about protecting their data.

Most of the users we deal with are shared. They are behind the entire IT environment. The main pitch from our end is based on the fact that this edition is really easy to use, and we think you should try it and see that. There are a lot of challenges in the market. Our companies don't usually have dedicated IT personnel for everything. They usually share one IT person or all the IT folks for all the workflows of the IT department. 

So, it's basically a decision criterion for them, whether they want to have a solution that's really easy to use and manage. It doesn't require more than one person, but from a backup perspective, the best practice is always to have some redundancy on it. You can have two, but you don't really need two people. It's just for the case that if someone doesn't show up to work or something goes wrong with backups and that guy is not available, someone else should be there. But purely speaking, it's a one man job, and he can also share with the other IT workload.

Veeam is good in general, from a technical support perspective. I've really enjoyed the fact that they have a really high response rate. You can just open a support ticket and call them on the phone so you know that they got it. You refer to the ticket number and you just have a remote engineer also engage in technical support. They are very supportive in general, I love the support there.

I enjoy it because it helps me a lot when I am with a client and an issue presents itself that I'm not able to resolve. I open a support ticket, call the toll free number, and have an engineer engage with me within five minutes, which is amazing for my establishment. They will start working on the problem and resolve it.

It's as easy as downloading the file, installing it, and then simply entering the administrative accounts for Office 365. You also need internet access. It's really an easy task to do with Veeam Backup Office 365. Literally just clicking next, next, next.

So from an ease of use perspective, it's really easy. It's just that when enterprise companies come to deploy it, they might face a bit of a challenge in this region specifically when it comes to internet bandwidth, because sometimes in Saudi Arabia bandwidth is a huge restriction for organizations that have, for example, 5,000 users or huge mailboxes. It's really expensive to have corporate internet in Saudi Arabia. So it can be a challenge backing up these environments under restricted bandwidths. It's not a restriction from the solution. It's just a regional restriction. Other markets can enjoy the privilege of backing up without any issues related to bandwidth.

It's also deployable on the cloud. That's an option. But in our region, some government entities don't allow that.

I did a proof of concept a week ago. We were backing up a physical server using the other product. That took us about half an hour. During that half an hour, I downloaded Veeam Backup for Office 365 from the website. I joined the client's Office 365 account. I downloaded and installed Veeam Backup for Office 365. Then I asked for the client to enter his credentials for the Office 365, and boom. We were seeing all the mailboxes and we just started to back up from there.

Backup does take some time, of course, because the mailbox was pretty huge. Generally, ease of use and configuration is pretty simple. It's easy to use, straightforward, actually.

Part of my job is that I install this software for proof of concepts. Some clients come to us with concerns like, "How do I backup my Office 365?" We'll provide the proof concept for them. I do that as well.

There are other options, because Veeam backup for Office 365 is the software, which you can put on your own platform by backing up from the internet, or you can install it on any Windows VM on the cloud as well. There are other options like NetApp, which has software in the server, in which you don't have to really worry about installing the software onto anything. Or you can install the software, but they'll back up the data for you and keep it. Some clients may not be keen towards that with the privacy component. Also, some clients want to have a copy of the data with themselves.

However, it is also heedless when it comes to infrastructure resources. You don't have to worry about having servers put in place, dedicated for Veeam backup for Office 365 and the storage that you need, and then worry about the bandwidth that you need. These kinds of operational costs are considerations as well. I've heard about NetApp having Office 365 backup solutions, but I've never even thought deep into it. Also, some clients kind of do the backup manually as well. It's kind of a tedious job, though. Maybe when it's a small environment, it can be manageable, but for a big environment, it can be a nightmare.

Honestly speaking, lots of people just look at it from a business point of view. They say, "I just have a business need. I just want to backup my Office 365 data." But they don't take much concern into what that also requires. Generally speaking, from a backup point of view, the biggest concern is what percentage of data you'd like to backup and the capacity of this data.

Also consider what the recovery point objectives are, meaning how frequently do you want to do backups. What kind of retention policy are you trying to achieve? The shorter the retention policy, the smaller the storage capacity you need, and the lower the cost of the solution. At the same time, some people are tied by their clients and by specific retention policies. So, tell people they need to archive their backups into deduplication appliances to save on the cost of long-term archival. However, that's not natively possible with Veeam backup for Office 365 yet. I believe it can be done manually, though.

That's what clients need to be careful of and the really important part is to make sure they have enough storage for what they are trying to achieve as they prepare their backup plan. The internet bandwidth for this also needs to be considered. It is best to have a dedicated channel for this. Think about the use of backups and make sure it is properly sized. Then they should be good to go. They should be worrying about the details, the sizing, and design of the solution to fit their needs. Other than that, so long as that process goes well, it should be pretty seamless after that.

This product is a really decent product so it would be unfair for me to rate it because I'm not familiar with other products that compete with it. Generally speaking from my experience, this solution is very good, but it also has some room for improvement. On the other hand, it's tough because the product is really amazing. It's just really new. I'm pretty sure the improvements will come along the way. I'll give it a nine out of ten.

We use the product as a data backup tool for Office 365.

Veeam Backup for Microsoft 365 is reliable and easy to use.

There could be integration with monitoring tools. They should include some more options to send alerts in existing monitoring software.

We have been using Veeam Backup for Microsoft 365 for three years.

It is a very stable product.

The product has flexible scalability. It is suitable for medium and enterprise businesses. I rate its scalability a seven out of ten.

The initial setup is straightforward. I rate the process a nine. It takes less than a day to complete.

It is an expensive product, and there is an additional cost involved in purchasing hardware. I rate the pricing an eight out of ten.

I rate Veeam Backup for Microsoft 365 a seven out of ten. I advise others to look for more secure products.