cipp-tenants skillA
cipp-tenants is agent-read markdown (skill) from wyre-ai/msp-claude-plugins: The top-level CIPP scope: enumerating managed M365 tenants, retrieving tenant detail, and the accepted `tenantFilter` identifier formats (default domain, custom domain, GUID, `allTenants`). Also covers stale-cache detection and the two common tenant-resolution failure modes..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# 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. ## Anti-triggers - **Inforcer's tenant list** — Inforcer manages the same M365 tenants but keys them by an *integer* Client Tenant ID, not a domain or GUID. A `tenantFilter` value from here will not work there; use `inforcer-tenant-management`. - **Why a tenant is missing, stale, or failing** — that is usually the GDAP delegation chain, not the tenant record; use `cipp-ops`. - **A tenant's licence, standards, or CA posture** — this skill only resolves and describes the tenant itself; use `cipp-licenses`, `cipp-standards`, or `cipp-security`. ## 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() ``` …
Read the whole file at its exact version.
How to install
mdr add wyre-ai/msp-claude-plugins/cipp-tenants@git:20260804.f49efe8mdr add wyre-ai/msp-claude-plugins/cipp-tenants@sha256:48ca21daa898b083Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_aqgkwsiah2qqhn64)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260804.f49efe8 latest | 2026-08-04 | f49efe8 | 3,613 B | A | view · diff |
| git:20260728.b7e78fc | 2026-07-28 | b7e78fc | 3,045 B | A | view · diff |
| git:20260713.1fbd3f3 | 2026-07-13 | 1fbd3f3 | 3,047 B | A | view · diff |
| git:20260507.ba09ce6 | 2026-05-07 | ba09ce6 | 3,060 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (3613 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
wyre-ai/msp-claude-plugins · 46 stars · license Apache-2.0 · pushed 2026-09-22 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_aqgkwsiah2qqhn64 GET https://markdownregistry.com/api/v1/resolve?ref=wyre-ai/msp-claude-plugins/cipp-tenants GET https://markdownregistry.com/api/v1/blob/48ca21daa898b0834436de299a7ad6392604e8ebf1831119e76b6b0c2807ce7c
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.