Microsoft 365 Backup improves: Effective March 2, 2026, departmental billing is available in Microsoft 365 Backup. Also, file-level restore is entering public preview in March 2026, with rollout beginning in April 2026.
Summary
- Departmental billing is now available for Microsoft 365 Backup to align costs by department, region, or business unit.
- Microsoft 365 Backup is now available for Government Community Cloud (GCC).
- File-level restore in Microsoft 365 Backup lets you browse and search available restore points and recover specific files; public preview in March 2026; rollout starting in April 2026.
- Backing up Microsoft 365 data remains the customer’s responsibility, and Microsoft 365 Backup is a great solution to do so.
Departmental billing for Microsoft 365 Backup (new)
Now available, Microsoft enables organizations to manage Microsoft 365 Backup on a granular level by assigning protection and costs to departments, regions, subsidiaries, or teams. This solves a long-standing challenge: backup costs in Microsoft 365 have historically been calculated at the tenant level, making it difficult for large organizations to allocate spend transparently or support internal chargeback models.
Administrators can define backup policies per scope and map consumption to the correct Azure subscription. Central IT retains tenant-wide visibility and governance while enabling autonomous management for departments or business units. This model fits customers with distributed responsibility, regional IT hubs, or subsidiaries operating semi-independently.
Benefits of departmental billing
- Transparent cost allocation that matches organizational structure
- Simpler chargeback and budgeting processes
- Reduced billing disputes between departments
- Better cost control through scoped policies per team or region
- Less administrative burden on central IT for ongoing consumption analysis
Granular file-level restore capability in Microsoft 365 Backup (new)
Microsoft is introducing a detailed file-level restore capability for SharePoint and OneDrive. Until now, Microsoft 365 Backup focused mainly on site-level or mailbox-level recovery. For many organizations, this was too broad. When only a single file was corrupted, overwritten, or ransomware encrypted, restoring an entire site collection was inefficient and risky. Customers often had to rebuild content manually or rely on third-party tools.
With file-level restore, administrators can browse and search available restore points and recover specific files or folders either to the original location or as copies to a new location. This makes recovery faster, more precise, and less disruptive.
This feature is entering public preview in March 2026 and will start rolling out in April 2026.
What is Microsoft 365 Backup?
Now also available for Government Community Cloud (GCC), Microsoft 365 Backup is a native Microsoft 365 service for protecting SharePoint, OneDrive, and Exchange data with high-speed, point-in-time recovery managed by administrators. It offers fast, point-in-time recovery that admins can manage directly inside Microsoft 365. Microsoft Teams backups will be integrated soon.
With Microsoft 365 Backup, you can:
- Back up and restore data across the entire Microsoft 365 environment
- Protect your organisation against cyberattacks and accidental deletion
- Use secure, immutable backups stored in Microsoft’s cloud
- Recover files, sites, mailboxes, and user content quickly and at scale
It provides a simple way to strengthen data resilience without adding extra tools or complexity.
The service is billed on a pay-as-you-go basis through Azure subscriptions and is configured and governed in the Microsoft 365 admin experience.
Why do we even need this backup solution? Isn’t it built into Microsoft 365 already?
This becomes clear in the Shared Responsibility Model:
- Microsoft manages the infrastructure, physical servers, and data centre security.
- The customer is always responsible for information and data, devices, and accounts and identities.
- Some responsibilities, such as applications and network controls, vary depending on SaaS, PaaS, or IaaS models.
In Microsoft 365 (a SaaS environment), your data is your responsibility:
What this means in practice
Microsoft 365 protects you with:
- Service availability
- Disaster recovery for Microsoft systems
- Basic end-user restore options
But it does not replace a proper enterprise backup. Accidental deletion, ransomware, misconfigurations, and malicious insider actions still require independent, point-in-time copies of your data.
Meaning: Microsoft keeps the service running. You must protect your data. Microsoft 365 Backup closes this gap.
What organizations should do now
- Identify which departments or regions need their own backup policies and create clear scopes.
- Turn on departmental billing and link each scope to the correct Azure subscription for accurate cost attribution.
- Check which SharePoint sites and OneDrive accounts are currently protected and close any coverage gaps.
- Adjust RBAC so that department admins only have the permissions they actually need.
- Review usage patterns and restore activity regularly and refine policies based on business priority.
FAQ
Do I need separate Azure subscriptions for departmental billing?
No. Microsoft 365 Backup does not require separate Azure subscriptions, but each department or scope must be explicitly mapped to an Azure subscription to generate department-level cost attribution. If all departments share one subscription, billing will still work, but all consumption appears under the same subscription ID.
For customers who need clean chargeback, central IT usually creates:
- one subscription per cost center or region, or
- one subscription with multiple resource groups and Cost Management rules.
This allows expenses to be split automatically without manual cost reallocation in Excel each month.
Does file-level restore replace third-party backup tools?
In many day-to-day recovery scenarios, yes. File-level restore now covers the most common operational needs such as accidental deletion, overwriting, versioning conflicts, or targeted ransomware cleanup.
However, Microsoft 365 Backup still does not provide:
- long-term retention beyond the configured backup window,
- offline archives for air-gap strategies,
- cross-tenant restore for mergers and acquisitions,
- extended metadata reporting,
- granular admin roles tailored for compliance teams.
For advanced retention and compliance-driven sectors, third-party tools remain relevant. For standard operational restore, Microsoft 365 Backup now covers most use cases natively.
Will departmental billing affect existing backup policies?
Existing policies remain unchanged until you move them into scopes. Policies continue to run at the tenant level unless explicitly reassigned to a department or region.
If you migrate policies into departmental scopes, you must reassign:
- the backup policy,
- admin permissions via RBAC,
- the Azure subscription that should receive the charges.
Nothing breaks if you do nothing. But without moving policies into scopes, consumption continues to be billed centrally, and you do not benefit from cost separation.
How far back can I browse restore points for file-level recovery?
File-level restore uses the same retention window as your Microsoft 365 Backup dataset. Currently, Microsoft creates daily restore points and keeps them based on your configured retention settings. Customers typically configure between 30 and 180 days, depending on compliance requirements.
File-level restore does not add new retention options. It adds finer granularity within your existing restore timeline. For example, if a tenant keeps 90 days of restore points, the file-level explorer will show all restore points across those 90 days.
Does delegated administration reduce central IT control?
No. RBAC is strictly additive. Department administrators receive permissions only for the scope assigned to them. Central IT:
- retains global oversight of all scopes,
- can override or restore from any department,
- controls who can create and manage scopes,
- can revoke departmental permissions at any time.
Delegation reduces the operational workload for central IT while preserving full governance and auditability.
Ready to align backup costs and recovery to your structure?
Contact our industry-leading Microsoft licensing experts today for tailored licensing guidance and a clear strategy for Microsoft 365 Backup.
Sources
Microsoft 365 Backup: Departmental billing: https://techcommunity.microsoft.com/blog/microsoft_365blog/departmental-billing-for-microsoft-365-backup-is-now-available/4497960.
Microsoft 365 Backup: File-based restore: https://www.microsoft.com/en-us/microsoft-365/roadmap?filters=%5B%22Microsoft+365%22%5D&sortby=Rollout+Start%3A+Newest+to+oldest.
MicrosoftLearn article: https://learn.microsoft.com/en-us/microsoft-365/backup/backup-billing.
Microsoft Licensing: https://www.schneider.im/software/microsoft/.