Microsoft Entra ID and Totango integration

Govern stale Entra ID guest accounts with SharePoint and Microsoft Teams

Quick overview This template runs two scheduled workflows to govern Microsoft Entra ID (Azure AD) guest accounts by detecting stale users via Microsoft Graph, staging deletions in SharePoint with a 72-hour window, notifying sponsors in Microsoft Teams, and deleting overdue guests while auditing outcomes. How it works The Scanner (Runs Weekly): Fetches all guest users using native Microsoft Graph API pagination. Filters Stale Accounts: Identifies guests with no sign-in activity for over 90 days. Stages Deletions: Writes new stale accounts to a SharePoint PendingGuestDeletions list with a 72-hour countdown. Alerts Sponsors: Mentions the assigned manager in a Microsoft Teams message, warning them of the impending deletion. The Executioner (Runs Daily): Queries SharePoint for records where the 72-hour countdown has expired. Checks Exceptions: Verifies if the sponsor added the guest to a SharePoint GuestRetentionExceptions list. Deletes & Audits: Safely deletes the Entra ID account (if not retained), updates the staging list status, and logs the final outcome to an Audit SharePoint list. Setup SharePoint: Create three lists: PendingGuestDeletions, GuestRetentionExceptions, and GuestAccountAuditLog (ensure columns match the workflow JSON). Azure AD: Create an App Registration with User.ReadWrite.All, AuditLog.Read.All, Sites.ReadWrite.All, and ChannelMessage.Send (Application permissions). n8n Credentials: Connect your OAuth2 (Client Credentials) setup to the "MS Graph - Guest Governance" credential. Configuration: Open the two Config nodes (Scanner and Executioner) and paste your SharePoint Site ID, List IDs, and Teams Team/Channel IDs. Error Handler: Go to Workflow Settings and bind your preferred Error Handler workflow to catch API routing failures. Requirements Microsoft Entra ID (Azure AD) tenant Microsoft SharePoint (for database state management) Microsoft Teams (for sponsor alerts) Azure App Registration with Application-level Graph API permissions Customization Modify the inactivityThresholdDays (default 90) and responseWindowHours (default 72) in the Config nodes. Adjust the Teams message HTML payload to match your internal IT branding. Change the Cron triggers to match your specific IT operational cadence. Additional info This template completely avoids the severe limitations of long-running 72-hour Wait nodes by decoupling the discovery and deletion phases into two distinct workflows bridged by a SharePoint database. Combined with native node pagination and built-in rate-limit retries, this engine is highly resilient and safe to run in massive enterprise tenants with tens of thousands of guest users.