Acronis Tenants and Usage
Overview
Everything in Acronis lives in a tenant. Most workflows in this plugin start
with "which tenant UUID is this client?", so this skill covers how to find
it, plus the account-level jobs an MSP does monthly: usage reconciliation,
user access reviews and MFA posture.
Key Concepts
| Tenant kind |
What it is |
| Partner |
The MSP's own tenant. A partner-level API client sees everything under it. |
| Folder |
An optional grouping of customers under a partner |
| Customer |
One client organization. Backups, alerts and incidents live here. |
| Unit |
An optional sub-division inside a customer |
Workflow: Find the Partner Tenant
- Call
acronis_fetch_current_user_info. Its result names the tenant the
API client signs in as.
- If that doesn't give a tenant ID, ask the operator for the partner tenant
ID. Don't guess one.
- Confirm it with
acronis_fetch_tenant (path.tenant_id). Check that its
kind is partner, not customer. A customer-level API client sees only that
one customer.
Workflow: List and Map Customers
acronis_fetch_tenants_batch with parent_id set to the partner tenant
and lod: "basic" returns the direct children with names. Use
subtree_root_id instead when customers sit inside folders, which returns
the whole hierarchy.
- Page with
limit and after (from paging.cursors.after) until there is
no next cursor.
- To find one client by name, use
acronis_search with tenant set to the
partner tenant and text set to the name. It searches tenants and users.
- Map each customer to its PSA company by name and save the mapping.
Acronis tenant names are free text, so expect near-misses ("Acme Inc" vs.
"Acme, Inc.") and confirm the ambiguous ones with the operator.
acronis_fetch_tenant_children returns only child IDs. Follow it with
acronis_fetch_tenants_batch (uuids, up to 100 per call) for names.
Workflow: Monthly Usage Reconciliation
- For each customer, call
acronis_fetch_tenant_usages with
path.tenant_id. It returns the tenant's usage metrics, one per usage
name (for example workstations). Narrow with usage_names or editions
(both comma-separated) once you know which ones you bill for.
- Compare each metric against the quantity on the client's PSA agreement or
last invoice.
- Report three lists: under-billed (Acronis usage higher than billed),
over-billed (billed for more than is used), and matches.
- Run reconciliation on the same day each month so the numbers compare
like for like.
Pricing, editions and offering items can't be changed through this
connector. Report differences; changes happen in the console or PSA.
Workflow: User Access Review
acronis_fetch_users_batch with subtree_root_tenant_id set to the
customer tenant, lod: "full" and with_access_policies: true returns
the customer's users (including those in its units) with their details and
access policies, which carry their roles. Page with limit and after.
- Alternatively,
acronis_fetch_tenant_users returns user UUIDs only
(pass include_grand_children: true for users in units). Follow it with
acronis_fetch_users_batch using uuids, up to 100 per call.
- Flag: users who left the client, shared or generic logins, and anyone
with an administrator role who doesn't need it.
- Check the MSP side too: run the same steps on the partner tenant to see
which technicians have partner-level access.
Disabling or deleting users can't be done through this connector. Give the
operator the list to act on in the console.
Workflow: MFA Posture
acronis_fetch_tenant_mfa_status with path.tenant_id reports whether MFA
is on for the tenant and how many users have set up TOTP. Run it on the
partner tenant first: an MSP's own Acronis logins reach every client's
backups, so partner-level MFA matters most. Then run it per customer for
clients whose staff log in to Acronis.
Gotchas
uuids, parent_id and subtree_root_id on acronis_fetch_tenants_batch
can't be combined. Pick one.
- Deleted tenants and users are hidden unless you pass
allow_deleted: true.
Leave it off for reconciliation, or retired clients show up as live.
acronis_fetch_user takes one user. For more than a handful, use
acronis_fetch_users_batch. Its uuids, tenant_id and
subtree_root_tenant_id filters can't be combined.
- Tenant and user IDs must be 36-character UUIDs. The tools reject anything
else, such as a tenant name.
Related Skills
1---2name: acronis-tenants-and-usage3description: >4 The Acronis Cyber Protect Cloud tenant hierarchy as an MSP sees it: finding5 the partner tenant, listing and searching customer tenants, mapping them to6 PSA companies, reading per-customer usage for billing reconciliation,7 listing a customer's Acronis users and their roles for access reviews, and8 checking MFA enrollment. All read-only; tenant, user and pricing changes9 are not available through this connector.10when_to_use: >-11 When an MSP needs to find an Acronis customer tenant, list all Acronis12 customers, reconcile Acronis usage against PSA contracts or invoices,13 review who has access to a customer's Acronis tenant, or check MFA14 enforcement. Use when: acronis customers, acronis tenant id, acronis usage,15 acronis billing reconciliation, acronis seat count, acronis users, acronis16 MFA, or acronis access review.17metadata:18 source: https://skillmd.com/skills/wyre-ai/acronis-tenants-and-usage19---2021# Acronis Tenants and Usage2223## Overview2425Everything in Acronis lives in a tenant. Most workflows in this plugin start26with "which tenant UUID is this client?", so this skill covers how to find27it, plus the account-level jobs an MSP does monthly: usage reconciliation,28user access reviews and MFA posture.2930## Key Concepts3132| Tenant kind | What it is |33|-------------|-----------|34| Partner | The MSP's own tenant. A partner-level API client sees everything under it. |35| Folder | An optional grouping of customers under a partner |36| Customer | One client organization. Backups, alerts and incidents live here. |37| Unit | An optional sub-division inside a customer |3839## Workflow: Find the Partner Tenant40411. Call `acronis_fetch_current_user_info`. Its result names the tenant the42 API client signs in as.432. If that doesn't give a tenant ID, ask the operator for the partner tenant44 ID. Don't guess one.453. Confirm it with `acronis_fetch_tenant` (`path.tenant_id`). Check that its46 kind is partner, not customer. A customer-level API client sees only that47 one customer.4849## Workflow: List and Map Customers50511. `acronis_fetch_tenants_batch` with `parent_id` set to the partner tenant52 and `lod: "basic"` returns the direct children with names. Use53 `subtree_root_id` instead when customers sit inside folders, which returns54 the whole hierarchy.552. Page with `limit` and `after` (from `paging.cursors.after`) until there is56 no next cursor.573. To find one client by name, use `acronis_search` with `tenant` set to the58 partner tenant and `text` set to the name. It searches tenants and users.594. Map each customer to its PSA company by name and save the mapping.60 Acronis tenant names are free text, so expect near-misses ("Acme Inc" vs.61 "Acme, Inc.") and confirm the ambiguous ones with the operator.6263`acronis_fetch_tenant_children` returns only child **IDs**. Follow it with64`acronis_fetch_tenants_batch` (`uuids`, up to 100 per call) for names.6566## Workflow: Monthly Usage Reconciliation67681. For each customer, call `acronis_fetch_tenant_usages` with69 `path.tenant_id`. It returns the tenant's usage metrics, one per usage70 name (for example `workstations`). Narrow with `usage_names` or `editions`71 (both comma-separated) once you know which ones you bill for.722. Compare each metric against the quantity on the client's PSA agreement or73 last invoice.743. Report three lists: under-billed (Acronis usage higher than billed),75 over-billed (billed for more than is used), and matches.764. Run reconciliation on the same day each month so the numbers compare77 like for like.7879Pricing, editions and offering items can't be changed through this80connector. Report differences; changes happen in the console or PSA.8182## Workflow: User Access Review83841. `acronis_fetch_users_batch` with `subtree_root_tenant_id` set to the85 customer tenant, `lod: "full"` and `with_access_policies: true` returns86 the customer's users (including those in its units) with their details and87 access policies, which carry their roles. Page with `limit` and `after`.882. Alternatively, `acronis_fetch_tenant_users` returns user **UUIDs** only89 (pass `include_grand_children: true` for users in units). Follow it with90 `acronis_fetch_users_batch` using `uuids`, up to 100 per call.913. Flag: users who left the client, shared or generic logins, and anyone92 with an administrator role who doesn't need it.934. Check the MSP side too: run the same steps on the partner tenant to see94 which technicians have partner-level access.9596Disabling or deleting users can't be done through this connector. Give the97operator the list to act on in the console.9899## Workflow: MFA Posture100101`acronis_fetch_tenant_mfa_status` with `path.tenant_id` reports whether MFA102is on for the tenant and how many users have set up TOTP. Run it on the103partner tenant first: an MSP's own Acronis logins reach every client's104backups, so partner-level MFA matters most. Then run it per customer for105clients whose staff log in to Acronis.106107## Gotchas108109- `uuids`, `parent_id` and `subtree_root_id` on `acronis_fetch_tenants_batch`110 can't be combined. Pick one.111- Deleted tenants and users are hidden unless you pass `allow_deleted: true`.112 Leave it off for reconciliation, or retired clients show up as live.113- `acronis_fetch_user` takes one user. For more than a handful, use114 `acronis_fetch_users_batch`. Its `uuids`, `tenant_id` and115 `subtree_root_tenant_id` filters can't be combined.116- Tenant and user IDs must be 36-character UUIDs. The tools reject anything117 else, such as a tenant name.118119## Related Skills120121- [api-patterns](../api-patterns/SKILL.md) - Headers, pagination and errors122- [backup-health](../backup-health/SKILL.md) - Alert triage per customer123- [protection-coverage](../protection-coverage/SKILL.md) - Coverage audit per customer