A backup visible in a console is not necessarily a backup that is still being updated. A small business may discover the difference too late: older copies remain available, but documents created after a configuration change are no longer protected. Microsoft's clarifications dated 4 November 2026 about Microsoft 365 Backup provide a useful reason to review this point with the person responsible for IT.
Clarifications, not automatic activation
In its what's new documentation, Microsoft explains that turning off Full Workload Backup stops new backups for items protected only by that policy. Existing copies remain restorable according to their retention settings. This feature remains in preview. These clarifications therefore do not mean that every Microsoft 365 subscription automatically includes this protection.
The backup policy guide also explains that the protection scope must be defined for the relevant services. Removing an account or site from that scope can stop its new backups. Before changing a rule, understand what it covers and what will take over.
Start with the data your organisation needs
Our practical advice is to start with your work, rather than a product's list of options. Which documents would allow you to resume work tomorrow morning? Where are your client folders, accounting files and association documents? Record the service used and the person responsible for each set. This small inventory helps you ask precise questions without sending confidential files to someone who does not need them.
For each important set, ask for confirmation of the scope currently protected and the date of the latest successful restore point. An old screenshot or the memory of an installation cannot describe the current situation. Where several solutions coexist, identify which one covers each requirement so you can spot areas with no clear owner.
Keep everyday changes under control
An employee leaving, a new shared workspace or a reorganisation of groups are useful moments to repeat this check. This does not mean running a restore after every change. It means checking that the intended result has been achieved and that an administrative change has not unintentionally altered data protection.
Keep a short record: what was meant to change, who performed the work, the planned check and its result. If protection was deliberately interrupted, record why and how the risk will be addressed. Avoid deleting a policy or shortening retention simply to make an alert disappear: first ask for an explanation of the consequences.
Plan a recovery check
A useful question for your IT provider is: “When did we last check that we could recover a representative document?” Prepare that exercise with a non-sensitive file, a suitable destination and a designated owner. The aim is to observe the result without overwriting a production document, then record any limitations and decisions required.
To review your organisation's approach, visit our Cloud and Microsoft 365 page or contact MYCIO. A clear list of what needs protection, recent changes and checks already performed is a useful starting point.