Microsoft 365 Backup: Delegate Administration & Configure Billing Policies

Introduction

Data protection at enterprise scale is no longer a monolithic IT responsibility. As organizations grow — spanning multiple departments, regions, subsidiaries, and business units — the need to decentralize backup management while maintaining centralized governance has become one of the most pressing demands in Microsoft 365 administration.

On March 2, 2026, Microsoft announced the general availability of departmental billing for Microsoft 365 Backup, a major enhancement that directly addresses this challenge. The new capability introduces three fundamental improvements to the backup management experience: granular billing scoping across Azure subscriptions, Role-Based Access Control (RBAC) for delegated administration, and the ability to implement formal chargeback models across departments, regions, or business units.

Bottom line for IT administrators: You can now assign department-specific backup admins, connect multiple Azure subscriptions to a single Microsoft 365 Backup configuration, and bill backup costs back to the exact teams generating them — all without surrendering central IT governance or visibility.

What Is Microsoft 365 Backup?

Microsoft 365 Backup is Microsoft’s native, first-party backup and recovery service integrated directly into the Microsoft 365 Admin Center. Launched initially for OneDrive, SharePoint, and Exchange Online, it provides fast, point-in-time recovery for the three most critical Microsoft 365 workloads.

The service operates on a pay-as-you-go billing model at a flat rate, with backups stored natively within Microsoft’s infrastructure. This eliminates the need for third-party backup agents, separate storage accounts, or complex export processes for basic recovery scenarios.

The Challenge Departmental Billing Solves

Before the introduction of departmental billing, Microsoft 365 Backup operated as a tenant-wide, all-or-nothing administrative model. A Global Administrator or SharePoint Administrator controlled all backup policies across the entire organization, and all backup costs landed in a single Azure subscription. This created three compounding problems for enterprise customers:

The Three Core Capabilities of Departmental Billing

1. Granular Billing Scoping Across Azure Subscriptions

Organizations can now connect multiple Azure subscriptions to a single Microsoft 365 Backup configuration. Each connected subscription acts as a billing policy, and backup costs are attributed to the subscription that covers the protected data. This maps backup spending to the correct cost centers at the Azure billing layer, making charge allocation automatic rather than manually calculated.

For example, a global enterprise might connect three Azure subscriptions — one for the EMEA region, one for North America, and one for APAC — each responsible for the backup costs generated by their respective departments. Backup administrators in each region can then manage their own protection policies independently, with costs flowing to their own Azure subscription.

2. Role-Based Access Control (RBAC) for Delegated Administration

Departmental billing introduces RBAC enforcement at the Azure subscription level for Microsoft 365 Backup. Only administrators holding the Owner or Contributor role on an Azure subscription connected to Backup can create or modify backup policies that incur costs against that subscription. This is the delegation mechanism that makes decentralized backup management possible without compromising security.

The practical effect is that a department-level IT administrator — who may not have SharePoint Administrator or Global Administrator privileges at the tenant level — can still manage backup protection and recovery for the data within their department’s scope, provided they have been granted Owner or Contributor on the relevant Azure subscription.

3. Chargeback Model Support

Chargeback is the formal process of internally billing business units for the IT services they consume — in this case, Microsoft 365 Backup storage. By connecting each department’s backup policies to a dedicated Azure subscription, the costs are automatically separated at the Azure billing layer. Finance teams can then generate per-subscription cost reports and invoice departments accordingly.

This is a significant operational improvement for organizations that already run mature FinOps (Cloud Financial Operations) practices. Rather than manually splitting a single backup bill by estimating which department owns which data, the costs are inherently separated from the moment backup protection is configured.

Prerequisites for Departmental Billing

Before configuring departmental billing in your tenant, ensure the following are in place:

How to Configure Departmental Billing — Step-by-Step

Sign in to the Microsoft 365 Admin Center at admin.microsoft.com using a Global Administrator or SharePoint Administrator account.

In the Admin Center left navigation, select Billing. On the Billing page, navigate to the Pay-as-you-go tab. This is the new billing experience for Microsoft 365 Backup — new customers will find backup billing managed here rather than under Setup.

On the Pay-as-you-go page, select the Services tab. From the list of available services, select Microsoft 365 Backup to open its billing configuration panel.

In the Billing Policies tab on the Microsoft 365 Backup page, you can connect additional Azure subscriptions as billing policies. Each connected subscription can be designated to cover backup costs for specific departments, regions, or business units.

1. Click Add billing policy.
2. Select the Azure subscription you want to connect from the dropdown. Only subscriptions in the same Entra tenant will appear.
3. Assign a descriptive name to the billing policy (e.g., EMEA-Backup-Policy or HR-Department-Backup).
4. Click Save. The new billing policy will appear in the Billing Policies tab.
5. Repeat for each department or business unit that requires separate billing.

To enforce RBAC-based delegation — preventing administrators from billing backup charges to subscriptions they do not own — enable the departmental restriction:

• In the Settings tab on the Microsoft 365 Backup page, locate the departmental billing option.
• Select the checkbox to limit backup management within departments.
• Click Save.

Once this setting is enabled, only administrators with the Owner or Contributor Azure role on a connected billing policy subscription can create and edit backup policies that bill to that subscription. Administrators without this role on a specific subscription cannot create backup policies against it, even if they are SharePoint Administrators.

To grant a department-level administrator the ability to manage backup for their scope, assign them the Owner or Contributor role on the relevant Azure subscription in the Azure Portal:

• Sign in to portal.azure.com with Owner or User Access Administrator privileges.
• Navigate to Subscriptions and select the subscription connected as the department’s billing policy.
• Select Access control (IAM) from the left menu.
• Click Add > Add role assignment.
• Select the Contributor role (or Owner if full subscription management is appropriate).
• Search for and select the department backup admin’s user account.
• Click Review + assign to save the role assignment.

The department admin can now sign into the Microsoft 365 Admin Center and create or modify backup policies that bill to their assigned Azure subscription.

Real-World Deployment Scenarios

Additional Microsoft 365 Backup Updates (March 2026)

Alongside departmental billing, Microsoft announced several additional updates to Microsoft 365 Backup at the same time:

Pricing and Billing Model

Microsoft 365 Backup operates on a pay-as-you-go consumption model with no upfront commitment required. The current pricing structure is straightforward:

With departmental billing, the $0.15/GB/month charge is split across the connected Azure subscriptions according to which subscription’s billing policy covers each protected resource. There is no premium or additional charge for using departmental billing — the cost model remains the same; only the attribution of charges changes.

Known Limitations and Considerations

Native Microsoft 365 Backup vs. Third-Party Backup Solutions

With departmental billing now available, Microsoft 365 Backup has closed a significant enterprise gap — but it remains a relatively streamlined service compared to specialist third-party backup solutions. Understanding where each fits is important for IT decision-makers:

For organizations with straightforward backup and recovery needs, the native Microsoft 365 Backup service now offers compelling value — particularly with departmental billing enabling cost transparency and delegated administration that previously required expensive third-party solutions. Organizations with advanced compliance, multi-workload, or cross-cloud requirements should evaluate whether a third-party solution better meets their needs.

Conclusion

The general availability of departmental billing for Microsoft 365 Backup, effective March 2, 2026, represents one of the most significant maturity upgrades to the service since its launch. For enterprise IT administrators, it resolves the three major blockers that previously made Microsoft 365 Backup unsuitable for large, decentralized organizations: single-subscription billing, lack of delegation, and inability to implement chargeback models.

With multiple Azure subscription support, RBAC-enforced departmental administration, and native chargeback capability now in place, Microsoft 365 Backup can realistically serve as the primary backup solution for a much wider range of enterprise deployments — particularly those with regional IT teams, multiple business units, or mature FinOps practices that demand cost transparency and accountability.