Skip to content
Avanet
My account
My account

Loading …

Partner Dashboard: safely change licences for multiple MSP customers

The Sophos Central Partner Dashboard lets you change licences for multiple monthly-usage customers (MSP) together. The safe workflow is to select the intended customers, open Change Licenses, check the count, names and billing type (Billing Type), change only the authorised products and reconcile the entire preview before applying the changes.

Partner Dashboard is part of Sophos Fusion partner management (formerly Sophos Central). This workflow concerns monthly MSP licensing. It is neither a general guide to renewing term licences nor to assigning licences to individual users.

Record the authorised change before selecting customers

Each affected customer needs an approved change specifying which base product or add-on will be added, which will be removed and what must remain unchanged. Base products are the underlying product licences; add-ons extend their functionality. A term licence has a fixed duration and must not be removed simply because you want to add an MSP add-on.

Before starting, record customer names and unambiguous customer identifiers, existing licences, billing type and the intended target licences in the change request. The partner administrator carrying out the change must be authorised to change licences; commercial approval for any change in monthly billing must also be in place.

Include customers in the same selection only if the same approved change applies to all of them. Handle different target products or unresolved billing types separately. For your first use, a small, explicitly authorised group of customers is advisable. Even a pilot is a real licensing transaction, not a non-binding simulation.

Select customers and open Change Licenses

  1. Open the customer list in Partner Dashboard.
  2. Select only customers covered by the approved request. Compare names and customer identifiers with the prepared list; do not rely solely on a filter or similar customer names.
  3. Select Change Licenses. The flyout header shows the selected customers, including their count and names, and their billing type (Billing Type).
  4. Check these details against the request again. For the MSP monthly-usage workflow described here, the billing type must match monthly usage. Do not proceed if the count is unexpected, a customer name does not belong in the selection or the billing type differs.

The number of selected customers is not the number of licences being changed. A customer can have multiple product licences. These two figures are therefore checked separately later.

Change only the authorised products

Products start with No Changes. This setting means that no change is intended for the product concerned. It does not mean “no licence exists”.

Base products and add-ons can be changed independently. To adjust only an add-on, you do not need to select the unchanged base product again. This does not, however, replace checking whether the intended product features are permitted and approved for the customers.

Open the required product group and set only the changes covered by the request. Leave No Changes in place for all other products and options. The dialogue takes the current licence state into account; nevertheless, verify the intended outcome in the next view rather than inferring it from a default.

Example: The same additional add-on is approved for the fictional customers “Alpenblick Test AG” and “Seeblick Test GmbH”. Their existing base products should remain in place. Select exactly these two customers, change only the agreed add-on and leave the base products and all other options set to No Changes. Replace the names and add-on with the actual approved values; this example is not a product recommendation.

Review the Add/Remove preview before applying changes

After selecting products, proceed to the confirmation view without applying the changes yet. It distinguishes additions and removals, or Add/Remove, including term licences being removed and MSP licences or add-ons being added.

Before the final action, read the entire preview, including entries further down:

  • The customer count and all listed names match the request exactly.
  • The licences being added match the approved target scope.
  • Every licence removal is explicitly authorised; check term licences individually in particular.
  • Products without an authorised change remain unchanged.

In the example, the intended add-on may be added. An unexpected removal of the base product or a term licence is a reason not to apply the changes. Return to the selection or cancel the prepared change, correct the selection and review the newly generated preview in full. Do not confirm first and then try to undo the discrepancy.

Confirm the change in the final view only when the preview matches the approval. Record the approved preview and the time in the change request; customer data must not appear in public screenshots.

Verify the result for every customer

After applying the changes, reopen the actual licence inventory for every selected customer and compare it with the starting and target inventories. For checks in the customer tenant, Check licences in Sophos Fusion explains how to access Profile icon > Licensing and interpret usage and licence duration.

Acceptance requires three separate results: authorised products are present, authorised removals have taken effect and products outside the request remain in place. Also check the displayed billing type and have the person responsible for commercial matters reconcile the change with the agreed MSP billing. A correct licence inventory alone does not prove that the invoice amount is correct.

If an error appears or completion is unclear, do not blindly repeat the same bulk action. First check the current inventory for all affected customers and document which results are known for certain. If a discrepancy remains unclear, pause further changes and clarify it with the responsible licensing or support contact. Provide customer references, the starting inventory, the approved preview, the time and the observed result.

Correct errors without promising a billing rollback

Before applying changes, you can correct the selection or cancel the preparation. After applying them, any necessary corrective change is a separate licensing and billing transaction requiring fresh authorisation.

First record the inventory that actually exists now. Then agree a permissible target inventory with the person responsible for commercial matters, clarify removed term licences and costs already incurred, and only then create a new change request. This change also requires a full preview review and a follow-up check for each customer.

Adding or removing licences again is not a guaranteed Undo. While restoration or billing remains unresolved, do not perform a presumed reversing transaction on speculation.