The task finished and then someone opened the files.
Imagine asking an AI Agent to update a set of documents in SharePoint. It finishes the job, and everyone gets on with their day.
A few hours later, a colleague opens a file and notices that important information is missing. Then another person finds the same problem in different document. Meanwhile, other people have been working in those files and adding information you need to keep.
You may be able to but firstly, someone has to work out exactly what went wrong and how to put it right without losing the work done since.
Why we are paying attention to this?
On 15 October 2026, Veeam announced Intelligent ResOps for Microsoft 365 as a generally available add-on to Veeam Data Cloud for Microsoft 365. According to Veeam, it helps teams identify AI agents, see which sensitive data they can access and identify and undo their file changes.
That caught our attention because it addresses a practical problem: having a copy of a file is only part of the recovery process. You also need to know which copy you need, what changed and who else has worked on it.
At Hopp Solutions, we think those questions belong in the conversation before an agent gets permission to edit business data.
Which changes do you actually want to reverse?
An agent can have the right permissions and still make the wrong changes. Perhaps the instructions were unclear, or the task covered more documents than intended. The team may only notice when someone needs the information that has disappeared.
By then, restoring everything to yesterday could create another problem. Depending on how you restore, you could also lose valid updates made today.
Recovering selected files sounds straightforward until you need to identify every affected document and choose the right version of each one.
Our view is that a Microsoft 365 recovery plan should include this situation. The team needs a way to separate the changes it wants to undo from the work it wants to keep.
Have the conversation while there is time.
Before giving an agent broader access, get the people responsible for the application, permission and backups together, Walk through a mistake that could realistically happen in your environment.
Four questions are a useful starting point:
-
What can this agent change or delete, and does it need all that access?
-
If something goes wrong, can we find out which actions it performed?
-
Do we have recovery points and retention that cover the data we would need?
-
Who can stop the agent, approve the restore and check the recovered information?
You may find that the answers sit in different people. That is worth knowing now, there is time to agree on a process.
Try putting a small mistake right
Start with a test library containing realistic documents and no sensitive business data. Have an agent make a few controlled edits, including some you will treat as mistakes. Add valid changes separately, as colleagues might during a normal working day.
Then ask your team to put things right. Can they find the unwanted changes, recover the right content and keep the valid updates? How long does it take? Where do they have to guess, ask for access or call someone for help?
That exercise gives you something concrete to improve. It also makes “we can recover” a much more useful answer.
Hopp Solutions helps organisations review Microsoft 365 backup coverage, define recovery requirements and test restores, IF you are giving agents more access to business data talk to us about a Backup & Recovery Review.
