Skip to main content
Glama

cipp_offboard_user

Destructive

Queues an irreversible offboarding job for a user. Requires at least one opt-in action; confirm completion in CIPP's Offboarding view.

Instructions

⚠ DESTRUCTIVE — IRREVERSIBLE. Queues CIPP's offboarding job for a user. Every action is opt-in: at least one must be enabled or the call is rejected. Returns once the job is QUEUED — CIPP reports success on task creation, not completion, so confirm the outcome in CIPP's Offboarding view before reporting the account as offboarded. Confirm with the user before invoking.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
OOONoOut-of-office auto-reply message to set on the mailbox. Omit to leave the auto-reply unchanged.
userIdYesThe target user's Azure AD object ID or User Principal Name (UPN, e.g. alice@contoso.com).
forwardNoUPN to forward the user's incoming mail to. Omit to leave forwarding unchanged.
KeepCopyNoWhen forwarding, keep a copy of each message in the original mailbox. Only meaningful alongside forward.
ResetPassNoReset the account password to a new random value.
DeleteUserNo⚠ Delete the account outright. Do not combine with actions that need the account to exist afterwards.
HideFromGALNoHide the mailbox from the Global Address List.
RemoveRulesNoRemove all inbox rules from the mailbox.
RemoveGroupsNoRemove the user from all groups they are a member of.
RemoveMobileNoRemove the user's registered mobile devices.
tenantFilterYesTenant domain name or ID to scope the operation. Use 'allTenants' to target every managed tenant.
AccessAutomapNoUPNs to grant full access to the user's mailbox, automapped into their Outlook.
DisableSignInNoDisable the account so the user can no longer sign in.
OnedriveAccessNoUPNs to grant access to the user's OneDrive.
RemoveLicensesNoRemove every license assigned to the user.
RevokeSessionsNoRevoke all active sign-in sessions and refresh tokens.
AccessNoAutomapNoUPNs to grant full access to the user's mailbox without automapping.
ConvertToSharedNoConvert the mailbox to a shared mailbox so it can be retained without a license.
ClearImmutableIdNoClear the immutable ID, breaking the link to an on-premises AD object.
RemoveMFADevicesNoRemove all registered MFA methods for the user.
disableForwardingNoRemove any existing forwarding configured on the mailbox.
removePermissionsNoRemove the user's delegated access to other mailboxes across the tenant.
RemoveTeamsPhoneDIDNoRelease the Teams phone number (DID) assigned to the user.
removeCalendarInvitesNoCancel calendar invites the user organised.
DisableOneDriveSharingNoRevoke sharing links on the user's OneDrive. Requires a recent CIPP build; older ones ignore it.
removeCalendarPermissionsNoRemove the user's permissions on other users' calendars across the tenant.
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description discloses critical behaviors beyond annotations: it queues a job (not immediate), returns on queue success not completion, is irreversible, and requires opt-in actions. This complements the destructiveHint and readOnlyHint annotations without contradiction.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise, front-loading the destructive warning, and uses two effective sentences to convey purpose and critical caveats without unnecessary detail.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers key aspects: purpose, destructive nature, opt-in requirement, async behavior, and verification step. It lacks details on expected return structure but that is acceptable given no output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, with each parameter well-described. The tool description does not add additional parameter information beyond the schema, warranting the baseline score of 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool queues CIPP's offboarding job for a user, using a specific verb and resource. The destructive warning distinguishes it from sibling tools like cipp_disable_user or cipp_reset_password.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides important usage guidance: every action is opt-in with at least one required, confirm with user before invoking, and the job is only queued so outcome must be verified. However, it does not explicitly compare to alternative tools or give 'when not to use' scenarios.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/wyre-technology/cipp-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server