Skip to content

Veeam ​

Reads the Veeam Service Provider Console (VSPC) and provides the protected workloads per customer.

Credentials (gear icon) ​

FieldMeaning
API URLVSPC instance, e.g. https://vspc.example.com
API keyAPI key of a VSPC account with read permissions

Metrics ​

MetricMeaning
vb365Veeam Backup for Microsoft 365 — protected users
vbrVeeam Backup & Replication — protected workloads
cloudConnectCloud Connect workloads

The dashboard tile sums all three.

Licensed users of a company (VB365) ​

Click a company's row in Multiverse → Veeam to open its user list — like a MailStore instance lists its archives. It shows the licensed users of Veeam Backup for Microsoft 365, read live from the VB365 server through the VSPC (the same API proxying as the split below, with the stored API key): per user the user principal name, the Microsoft 365 organization, Counts towards — the customer the user's licence is billed to under the company's domain rules (without rules: the company itself) —, whether VB365 reports the user as backed up, and the last backup. The search box filters by any column; Reload reads the list again.

Above the list stand the number of licensed users and the company's VB365 figure. A company split by domain rules also shows the distribution in the next snapshot: how its VB365 figure is spread over the customers (the same table as the dialog's Next snapshot). If no licensed user is found, the company's Microsoft 365 organization is usually not linked to it in the VSPC — assign it in the company's split dialog (see below).

Export of the licensed users (VB365) ​

Licensed users (CSV) in the Veeam view's toolbar exports the licensed VB365 users of every company as a CSV file, read live with one inventory of the VB365 servers (as the snapshot reads them): company, user, e-mail, organization, Counts towards, backed up (yes/no) and last backup. The customer filter of the export dialog works on Counts towards — the customer a licence is billed to under the domain rules —, so the users of a split company are exported with the customers they are billed to. Licensed users of a VB365 organization no company is known for are not in the export; the dialog says how many there are (assign their organization in a company's split dialog, see below). If the users cannot be read at all, the export fails with the reason.

The user list of a company has the same button for that company's users.

Splitting one company across several customers (VB365) ​

Some customers share one Microsoft 365 tenant — and so one VSPC company — with their sister companies; the users differ only in the domain of their user principal name. Multiverse can split the company's VB365 figure by domain:

  1. In Multiverse → Veeam click Split… in the company's row. The dialog reads the licensed users of the Veeam Backup for Microsoft 365 server — the figure the VB365 licence counts, by user principal name — through the VSPC's API proxying with the stored VSPC API key; no extra access is needed. It shows how many licensed users the company has, how many carry an address, and the users per e-mail domain. Reload reads them again. Which organization (Microsoft 365 tenant on the VB365 server) belongs to the company the VSPC says — its organization → company mapping (Configuration → Plugin Library → Veeam Backup for Microsoft 365 → Companies, "Map to" / Automap). The dialog lists the VB365 organizations under VB365 organizations of this company with the company each resolves to. Where the VSPC names none — no mapping, or a mapping table the API key's user may not read (on VSPC 8 the Portal Administrator and Service Provider Administrator roles only; the diagnostics say so) — Count towards this company assigns the organization by hand: its licensed users then count towards the company in the dialog and in the snapshot. Remove assignment undoes it; assigning an organization to another company moves it (one organization, one company). A long list has a filter box.
  2. Add a domain rule per domain that belongs to another customer (Assign… in the domain table prefills it): domain → customer. Domains without a rule, and users without an address, stay with the company's own customer. Several domains may point to the same customer (they form one part); a rule naming the company's own customer is the same as no rule.

From the next snapshot on the company's vb365 figure appears under several customers: the company itself plus one per rule customer, with the ID company ID:domain. The VSPC reports the figure per company only, so it is split in proportion to the user numbers per domain, rounded to whole users with the largest remainder; the parts always add up to the company's figure. vbr and cloudConnect stay with the company. The dialog previews the split under Next snapshot.

If the licensed users cannot be read (the VSPC does not proxy the VB365 api, a server without management agent, an api error), the snapshot spreads every split company's VB365 figure by the licensed users of the last successful read, and the snapshot carries a warning that the invoice runs repeat — the customers of the rules keep their share (only a company whose users were never read stays whole). The same applies to a company for which the read finds no licensed user although it bills VB365 licences. The dialog's Diagnostics name the VB365 servers the VSPC knows, whether its organization → company mappings could be read (and how many), the counts of licensed, unmatched and unlicensed users, the VB365 api version the proxy answered with, and the fields of a user object and of an organization object (plus an excerpt when no organization names a company) — send them along when a company shows no users. The list marks split companies with "N domain rules".

Specifics ​

  • Companies and their licence usage are read page by page — a VSPC with more than 100 companies is collected completely. An answer that carries no list, or a usage list without a single used licence after a snapshot that had some, fails the snapshot for the night — nothing is stored as 0. If the VSPC really is not used any more, the zeros are stored after three days of that answer — and the snapshot says so for as long as an invoice could still have read the figures before them (45 days); every invoice run repeats it.
  • The live table adds up every server of a product and every workload on it, like the snapshot (it used to show the first workload of the first server only).
  • Company IDs are stable → automatic rename detection.
  • The customer of a domain rule counts as a customer source (listed in the customer view before the first snapshot, renamed along with merges).
  • VSPC API proxying (/proxy/{management agent}/vb365/v8/licensedUsers, v7 for an older VB365) needs a VSPC that offers it (8.1 or newer) and a VB365 server with a management agent; the API key is the one of the gear icon.