Skip to content

Commit 0442f14

Browse files
Merge pull request #30964 from MicrosoftDocs/main
[AutoPublish] main to live - 03/02 10:39 PST | 03/03 00:09 IST
2 parents d68fe3e + 8c42ea3 commit 0442f14

File tree

1 file changed

+46
-3
lines changed

1 file changed

+46
-3
lines changed

microsoft-365/backup/backup-billing.md

Lines changed: 46 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -16,9 +16,52 @@ ms.localizationpriority: medium
1616
description: Learn how to set up and manage usage and invoices in the Azure portal for Microsoft 365 Backup.
1717
---
1818

19-
# Manage consumption and invoices for Microsoft 365 Backup
19+
# Departmental Billing for Microsoft 365 Backup
2020

21-
You can view actual and accumulated cost breakdown by tenants and service type for OneDrive, SharePoint, and Exchange in Microsoft Cost Management in the Azure portal or access the information by using the [Cost Management public APIs](/rest/api/cost-management/operation-groups). Cost breakdown by application ID is coming soon.
21+
If you're a large organization with multiple departments and want to manage Microsoft 365 Backup within departments or groups, departmental billing may be the right fit for you. With Departmental billing, you can manage Backup with the following features:
22+
23+
1. Breakdown backup costs by different azure subscriptions.
24+
2. Limit Backup management (creation and update) to certain admins within departments with Role-based-access-control(RBAC).
25+
3. Prevent admins from another department using your azure subscription to cause unapproved backup charges.
26+
27+
28+
**Role-Based-Access-Control within departments(RBAC)**: To limit admins who can manage Backup within a department or group, every backup admin should also have an Owner or Contributor role on the subscription. This way only an approved admin who is given spending power on a subscription can create and edit backups and cause consumption to the department's azure subscription. If you're an owner for the department's subscription, we recommend giving the lower privileged 'Contributor' role to backup admins in your department if they don't need privileges to add other admins to the subscription.
29+
30+
### Set up departmental billing
31+
32+
To set up departmental billing for your tenant, follow these steps.
33+
34+
1. Create billing policies and connect them to Microsoft 365 Backup following the instructions in <a href="/microsoft-365/commerce/services/pay-as-you-go-setup-billing-node" target="_blank">**Pay-as-you-go Setup**</a> for Microsoft 365 Backup.
35+
2. In the **Services** tab of **Pay-as-you-go** page, select **Microsoft 365 Backup**.
36+
3. To enable departmental billing, in the **Settings** tab of Microsoft 365 Backup page, select the checkbox for limiting management of Backup within departments.
37+
38+
<img width="1148" height="665" alt="image" src="https://github.com/user-attachments/assets/31bdf6c3-966f-40ce-8abf-f144ed2fe893" />
39+
40+
Now that departmental billing with Backup is enabled for your tenant, Admins are assigned Owner / Contributor Azure roles to the billing policies connected to Backup can only create and edit backup policies.
41+
42+
5. You can create backup for your department by creating <a href="/microsoft-365/backup/backup-setup?view=o365-worldwide#2-create-backup-policies-to-protect-your-data" target="_blank">**backup policies as outlined here**</a>.
43+
In Create / Edit policy wizard, admins need to associate a Billing Policy with a Backup Policy. In the billing policy list, admins are shown only billing policies that they have Owner/Contributor access.
44+
<img width="907" height="431" alt="rbac" src="https://github.com/user-attachments/assets/91221de4-63e8-41a2-a2c4-528faa38b296" />
45+
46+
> [!NOTE]
47+
> **Once you have enabled departmental billing, admins who have been assigned Owner / Contributor Azure roles to the billing policies connected to Backup can only create and edit backup policies.**
48+
49+
Admins who don't have RBAC rights to your backup policies will not be able to use your billing policy to create backup policies or edit backup policies created by admins in your department. Billing policies show as **Confidential** for admins who don't have access.
50+
51+
<img width="559" height="352" alt="image-confidential" src="https://github.com/user-attachments/assets/07ba1426-fe4a-4023-8ebd-ab4904f2d789" />
52+
53+
### Change Billing policies associated with Backup policies
54+
Once a Billing Policy is associated with a Backup Policy, it can be updated from the Backup Dashboard
55+
56+
1. Select the Backup policy you want to update the Billing Policy. Click on the 3-dots next to backup policy name and select **Update Billing policy**.
57+
<img width="944" height="448" alt="image-updatebillingpolicy" src="https://github.com/user-attachments/assets/510a8756-113d-4403-941a-8366366d1800" />
58+
59+
### Disable departmental billing
60+
If you wish to manage Backup without the RBAC control of restricting Backup management to Owner or Contributor of subscriptions, uncheck the box in Settings tab Microsoft 365 Backup page.
61+
62+
### Manage consumption and invoices for Microsoft 365 Backup
63+
64+
You can view actual and accumulated cost breakdown by tenants and service type for OneDrive, SharePoint, and Exchange in Microsoft Cost Management in the Azure portal or by accessing the [Cost Management public APIs](/rest/api/cost-management/operation-groups). Cost breakdown by application ID is coming soon.
2265

2366
</br>
2467

@@ -77,4 +120,4 @@ To view tags:
77120
5. Set up budget alerts on cost by following the steps in the [Cost Management public APIs](/rest/api/cost-management/operation-groups).
78121

79122
> [!WARNING]
80-
>The **MailboxDbGuid** tag in the Azure consumption report is intended for Microsoft internal use only. We recommend that you do not rely on it because its value might change. Note that this is different from the MailboxId.
123+
>The **MailboxDbGuid** tag in the Azure consumption report is intended for Microsoft internal use only. We recommend that you don't rely on it because its value might change. Note that this is different from the MailboxId.

0 commit comments

Comments
 (0)