Skip to content
AscendCore
Back to Runbook Library
Identity Template: configurable per customer

Guest Account Cleanup

Review external B2B guest accounts by activity and invite age, then remove the stale ones in one approval-gated pass, audited.

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

On a schedule, AscendCore lists guest accounts by last activity and invite age, posts a review card, and on approval removes the selected guests. Each removal is recorded in the audit chain.

Status

Template. The staleness criteria and review cadence are configurable per customer. Connect it to your Microsoft Entra ID tenant to enable.

Runbook source preview

Versioned, deterministic, auditable

Every runbook is defined as a versioned YAML manifest with explicit triggers, steps, and approval policies. The runbook itself is the audit-ready record of what AscendCore can and will do. Chat is just the interface that triggers it.

name: guest-account-cleanup
trigger:
  schedule: monthly
steps:
  - query_guest_accounts       # by last activity / invite age
  - build_review_card
  - admin_approval
  - remove_selected_guests
approval:
  required: true
  approvers: [it-admins]
Want this runbook?

Configure guest account cleanup for your environment

Templates are configurable per customer environment. Talk to us about the specific systems and approval flow you need.