PnP PowerShell

Diagnoses a broken or unfamiliar machine and reports whether its environment is set up, and answers how to sign in to it. Verifies everything that must be true before anything can run: pwsh installed and on PATH, the PnP.PowerShell module present and current enough, whether this session is connected, and which app registration, persisted login or certificate this machine can actually authenticate with. Every failing check names its cause and the next command to run, filling in every value the machine's own state can supply. Call it before the first Connect-PnPOnline rather than composing one from memory, and whenever something is wrong or fails for a reason that is not obvious.

Returns this server's own guidance and recommended workflow: how to approach a task, the rules it enforces, how to treat tenant text that reads like an instruction, and the conventions to follow. The full document is long, so pass a section to read one topic.

Gets the reference documentation for one named cmdlet: its syntax, every parameter and what it means, the parameter sets, and examples. Use it once you know the cmdlet name and need to know how to call it.

Reports the connection state of one session: whether it is signed in right now, which site URL it holds, and which account it is authenticated as. Check it before connecting, so an existing connection is reused rather than opened again, and to find out who you are and where you are pointed.

Returns the next page of a result set that pnp_run_command summarised because it was too large to return whole. Pages over rows already fetched, so it costs nothing against the tenant and returns exactly the rows the original command saw. Use the cursor and offset printed under the summary.

Opens one specific sample already identified, addressed by the exact slug name a browse returned, and gives back its complete script body. Use it when you know precisely which sample you want.

Lists all active PowerShell sessions with their status and last activity time. Use this to see what sessions exist before deciding which to connect, reset, or reuse.

Returns the server version, uptime, read-only mode status, and active session count, plus (unless includeReadiness is false) a one-line readiness flag. Use this as a lightweight health check to confirm the server itself is responsive.

Signs out: ends a session and discards everything held in it, so the next call starts fresh and must reconnect. Use it to sign out or log out, to switch to a different account, or to recover a session that has wedged or stopped responding.

Runs PnP PowerShell against the connected tenant and returns what it produced. This is the tool that does the actual work: use it to create, read, update, set, change, add, remove, delete, list, upload, download, copy, move, restore or report on sites, lists, libraries, files, folders, list items, users, groups, permissions, Teams, Entra ID objects, and tenant or site settings. Chain steps with semicolons or newlines. The Connect-PnPOnline connection persists across calls sharing a sessionId, so connect once and keep going.

Saves a PnP PowerShell script to the user's own samples for reuse, so later searches and suggestions include it. Use it only when the user asks to keep or save a script. It never overwrites an existing file.

Answers the question "which cmdlet handles this, and what is it called?". Searches cmdlet names, verbs, nouns, descriptions, parameters and examples to discover whether one exists for the area you need to manage or work with. Describe the task in your own words -- "add a column to a list", "share a file externally" -- or pass keywords. Use it whenever the cmdlet name is unknown. Returns names, synopses, parameters and documentation links, never tenant data.

Browses the catalogue of community PnP Script Samples, plus the user's own, by keyword and returns titles, descriptions and reference links only, never any code. Use it to see what solutions already exist in an area.

Installs the PnP.PowerShell module for the current user so PnP cmdlets can run, choosing the released build or the latest pre-release. It installs only that module: it never signs in, never touches the tenant, and creates no app registration. For safety it installs only when PNP_MCP_ALLOW_SETUP=true; otherwise it returns the exact Install-Module command to run by hand. Use it when the PnP.PowerShell module is not installed.

Drafts a starting point for a job someone wants to automate, by matching the task against the user's own and community samples and returning their code plus guidance on adapting it. The entry point when a job is described rather than a cmdlet named.