Filters let you narrow a calculated custom license so it only counts the users, licenses, or subscription data that match the billing rule.
This is useful when one Microsoft tenant contains different departments, business units, domains, or excluded users.
| Filter area | Example | Typical use |
|---|---|---|
| Department | Department equals Finance | Department or cost-centre billing. |
| Location / office fields | Office equals Sydney | Site-based billing. |
| User type | User type equals Member | Exclude guests from managed-user billing. |
| Account enabled | Account enabled equals true | Exclude disabled leavers. |
| Domain | Domain equals customer.com | Split billing by brand, franchise, or business unit. |
| Assigned license SKU | Friendly name equals Microsoft 365 Business Premium | Bill users with a specific Microsoft license. |
| Extension attributes 1 to 15 | extensionAttribute1 equals Managed | Use customer-specific billing flags. |
Domain filters are matched against the normalized domain from the user's UPN or email address.
Extension attributes are useful when normal Microsoft fields do not match the billing rule.
Use extension attributes only when the customer or MSP has a reliable process for keeping those values accurate.
Calculation: All active licensed users where domain equals clientbrand.com.
Use when: One tenant contains multiple legal entities or brands.
Calculation: All active licensed users where extensionAttribute1 equals Managed.
Use when: Not every Microsoft user in the tenant receives the same MSP service.
Calculation: Licensed mailbox users excluding users where extensionAttribute2 equals NoBackup.
Use when: Some users should not be included in mailbox backup billing.