Skip to content
AscendCore
Back to Runbook Library
Identity Live in production

Guest Account Cleanup

Remove a stale external guest account from Slack or Teams in one approval-gated pass. A safety gate refuses member accounts, and removal is restorable for 30 days.

Integrates with

Entra ID

The problem

External collaboration leaves a trail of guest accounts. Vendors finish projects, partners move on, and the guest invitations stay in the directory with access to whatever they were once shared.

What AscendCore does

A requester names the guest account (and optionally why) in Slack or Teams. AscendCore resolves it in Microsoft Entra ID and posts an approval card with destructive-action styling, because this one deletes. At execution the account's directory type is re-verified: only an account marked Guest is removed, and a member account is always refused, even if one was somehow proposed. Removal is a soft delete with a 30-day recycle bin, restorable from the Entra portal, and every decision lands in the audit chain.

Status

Live in production. Runs against real Microsoft Entra ID tenants today with the execute-time guest safety gate verified in production (a member account was refused before any guest was removed) and a full audit trail.

How it runs

Deterministic, approval-gated, auditable

Each runbook is a fixed, reviewed sequence of steps with an explicit approval policy. The AI only works out what was asked; the runbook decides what happens, a named person approves it, and every decision lands on the tamper-evident audit chain. Chat is just the interface that triggers it.

Ready to deploy

Run guest account cleanup from Teams or Slack today

AscendCore deploys in days, not months for Slack + Okta or Teams + Entra stacks. See your first automated resolution the same day.