← ClaudeAtlas

cipp-tenantslisted

Use this skill when working with CIPP tenants — listing managed M365 tenants, checking tenant details, identifying tenant ID/domain, and scoping operations to a specific tenant. The starting point for almost every CIPP workflow since most other tools require a tenant filter.
wyre-technology/msp-claude-plugins · ★ 28 · DevOps & Infrastructure · score 80
Install: claude install-skill wyre-technology/msp-claude-plugins
# CIPP Tenants Tenants are the top-level scope in CIPP. Every operational tool — users, mailboxes, standards, security — takes a `tenantFilter` parameter that scopes the call to one tenant or to `allTenants`. Knowing how to enumerate tenants and resolve a friendly name to its tenant ID is the first step in almost every CIPP workflow. ## Tools ### `cipp_list_tenants` List every tenant CIPP manages. Returns a list of tenant objects with `customerId`, `defaultDomainName`, `displayName`, and onboarding status. ``` cipp_list_tenants() ``` Use this whenever a user refers to a client by name — the response gives you the `defaultDomainName` (or `customerId`) needed for `tenantFilter` on every other tool. ### `cipp_get_tenant_details` Retrieve detailed information for one tenant: license count, domain list, GDAP relationship status, last refresh time. ``` cipp_get_tenant_details(tenantFilter='contoso.onmicrosoft.com') ``` Use `tenantFilter='allTenants'` to get a portfolio-wide aggregate — useful for fleet reports. ## Identifying a tenant Most CIPP tools accept any of these in `tenantFilter`: | Format | Example | Notes | |--------|---------|-------| | Default domain | `contoso.onmicrosoft.com` | Most readable, recommended | | Custom domain | `contoso.com` | Works if CIPP has it cached | | Tenant GUID | `00000000-0000-0000-0000-000000000000` | Most stable but opaque | | `allTenants` | `allTenants` | Portfolio-wide; only some tools support it | When a user says "Acme", alwa