Use company licence filters to split a Microsoft tenant's licences into billing groups—for example, by office, department, or location. Where AutoMap is available, each filter can also specify the PSA agreement or contract that should receive its matching licences.

Plan the billing groups

Decide which users belong in each group and which PSA agreement should receive their licences. Check that the relevant Microsoft user attributes contain the values you intend to match.

Use the exact source values and check the resulting users and licence quantities. A filter with an incorrect value can return no results.

Find the new Filters box

1. Open Company > Companies and open the customer.
2. Open Agreement Sync > Licenses.
3. Find the blue Filters box above the licence list.
4. For the first filter, select Add filter. For an existing filter, select Edit beside that filter's heading.

After a filter is saved, use Search filters, Expand all, or Collapse all to find and inspect a billing group. Expand a filter to view its licences. An unmapped count identifies licences that still need a billing profile; it is not confirmation of a successful PSA sync.

Configure a filter and its agreement

1. Choose the Filter type and enter the value to match. For example, choose Office and enter Queensland.
2. Set Filter mode to Include to keep matching users, or Exclude to leave matching users out.
3. For Custom Attribute, select the required extension attribute and enter its value.
4. If using AutoMap, select the intended AutoMap Agreement for this billing group. The label may be AutoMap Contract, depending on the PSA.
5. Leave the agreement field empty to use the company's default AutoMap agreement.
6. Select Apply filter. Read and confirm the message shown, then allow the filtered data to reload.

Applying or changing a filter can remove existing licence mappings. The confirmation explains this before applying the change. Review the replacement mappings and resulting PSA agreement items after the next sync.

Example: bill a location separately

In this example, the company's default agreement is M365. Set Filter mode = Include, Filter = Department, and Department = QLD - Ops. Select QLD Ops agreement under AutoMap Agreement to give this group a different destination from the company default. These are sample agreement names; choose the appropriate agreement for your customer

Choose the user group and its destination agreement together, then select Apply filter and confirm the change.

After saving, expand Department: QLD - Ops and check the resulting licences. An empty result does not mean the filter failed to save: check the source user attributes and data retrieval before mapping.

The example tenant currently returns no matching licences. Confirm that the expected licensed users have Office set to Queensland before continuing. The saved filter alone is not a billing validation.

The filter controls the user/licence group. The AutoMap licence rule controls the billing profile and PSA product. Review both before approving the resulting mappings.

Add another filter

Select Add More Filters in the Filters box. In Create New Filter, choose the type, value, include/exclude behaviour, and optional AutoMap agreement. Select Create Filter and check the new result.

Check groups for unintended overlap, especially when billing several agreements or PSA companies from the same tenant.

Understand agreement selection

For automatically applied mappings, AutoMap keeps a valid agreement already assigned to an existing mapping. Otherwise, it uses the matched filter's agreement when one is set, then falls back to the company agreement settings.

Changing a filter agreement does not by itself guarantee that existing mappings move to that agreement. Applying an edited filter can also remove mappings as described above, so review the resulting state before running mapping again.

For companies requiring approval, check the Agreement on each proposal in AutoMap > Pending Mappings before approving it. If it is wrong, review both the filter and company AutoMap settings and recheck the proposal. Do not approve it until the destination is correct.

Follow Get started with AutoMap for the licence-rule and approval workflow.

Keep selected licence types outside filtering

The licence table's exclusion-from-filtering selection is separate from Filter mode. Select a licence type there only when it should remain outside the user-attribute filtering—for example, when head office pays centrally for that product. Check the resulting licence quantities before mapping.

When available, Show Unfiltered Licenses reveals an Unfiltered Licenses tab for reviewing licences outside the filtered groups. Show Available Licenses controls the additional available-licence view. Review these groups deliberately when planning how all tenant licences will be billed.

Clear a filter or bill a different PSA company

To clear an existing filter, open Edit and select Clear filter. Read the confirmation: clearing removes mapped licences and can leave products on the PSA agreement that need checking after the first sync.

If a location must be billed to a different PSA company entirely, add the Microsoft tenant as another company link and configure that company's filters and agreements. Verify the resulting groups to avoid duplicate billing.

Troubleshooting