OptyStack LogoOptyStack Logo
Product
Features
Shadow IT DiscoveryDiscover unsanctioned SaaS, shadow AI, and unmanaged subscriptions in one place.Identity Management with Zero Trust SecuritySingle sign-on and conditional access by IP, device, and region for your SaaS apps.Seamless App IntegrationsConnect Microsoft 365, Google Workspace, SSO, and 100+ SaaS brands into one live inventory.Cost OptimizationCut SaaS waste with discovery, usage-backed rightsizing, and renewal leverage—often up to ~30% savings.License ManagementFind unused seats, eliminate zombie accounts, and automate renewals with usage-backed data.Contract Renewal TrackingOne renewal calendar with notice windows, usage context, and negotiation-ready briefs.
ROI Calculator
Resources

Support

  • Support
  • Knowledge Base
  • SaaS Directory
  • Partners

Content

  • SaaS Inflation Index
  • 2026 SaaS Audit Toolkit
  • Blogs
  • Success Stories
  • Events
PricingAboutContact
Start Free Trial
Book Demo
← All postsSaaS Governance

2,800 Ex-Employees Still Had AI Accounts: Why Offboarding Now Has to Include AI Agents

Aryan Malik · November 19, 2026

3D cybersecurity infographic highlighting the risk of former employees retaining AI accounts, featuring a 2,800 statistic, an AI robot account on a laptop, a revoked employee identity, a security shield, and an offboarding checklist covering AI access revocation, account removal, and agent permission audits.
Share
LinkedInX

Oleria found more than 2,800 AI tool accounts held by former employees at one Fortune 500 company, plus about 800 unowned access points. Disabling the identity account does not end AI tool access or agent tokens. This guide explains why, how Microsoft’s agent inactivity policy helps, and gives a leaver checklist for SaaS and AI.

A Fortune 500 company that ran a full access review found something most offboarding processes miss. In a November 18, 2026 release, identity governance vendor Oleria said it found more than 2,800 AI tool accounts held by people who had left the company, plus about 800 unowned access points that let AI assistants act inside company systems. Those accounts were not in the identity provider’s offboarding path, and they kept working.

The finding comes from one company, not a survey. It still shows where the gap sits. Offboarding was designed for people who sign in through the directory. AI tools and agents often sign in another way, and they keep their own access after the person is gone.

Related reading

Explore related guides and continue your SaaS optimization research:

  • Agent Traces Are a Credential Store: What the Cursor Breach Teaches About Identity Risk
  • Cross-Tenant Sync Offboarding: What Microsoft’s Known Issues Mean for Your Checklist
  • Your AI Vendor’s AI Vendor: What the Fireworks-Notion Breach Teaches About Shadow AI Sub-processors
  • BluePhishing: Why AI Agent Consent Is the New OAuth Blind Spot (and 7 Checks for Your Entra Tenant)

Why Disabling the Identity Account Is Not Enough

When someone leaves, the usual steps are to disable the directory account, revoke sessions, and remove licenses. Those steps stop the person from signing in. They do not necessarily reach everything the person connected.

Three paths stay open:

  • AI tools outside SSO. Many AI products are used through a personal login, a local password, or a magic link. They never pass through the identity provider, so disabling the directory account does not affect them.

  • OAuth grants. An employee who connected an AI assistant to mail or files granted an OAuth consent. That grant belongs to the app, and it can keep reading data after the employee leaves. Material Security’s OAuth risk report analyzed 22,332 OAuth-connected apps across 21 Google Workspace environments. It found that 91% of AI and automation apps had appeared in the previous 16 months, mostly through individual connections rather than IT rollouts.

  • Agent tokens. An agent that runs with its own credentials does not need the person’s password to keep working. If it holds a valid key or token, it keeps acting after its owner leaves.

The problem is wider than one company. A Sagiss survey of 1,000 former U.S. employees, conducted in September 2026, found that 24% could still use a company AI tool or assistant after leaving. The survey is self-reported and did not establish which kinds of accounts were involved. A separate Sagiss finding reported in November 2026 found that 64% of former employees could still access sensitive company information.

The Agent Twist: Agents Need a Human Owner and an Exit Path

Agents change the offboarding question. An agent is software, but it acts on someone’s authority. When that person leaves, the agent’s authority does not automatically end.

Microsoft is building a backstop. Its default Agent ID inactivity policy, which is in preview, is described in Microsoft’s documentation. It notifies owners and sponsors when an agent has been inactive for 60 days. It starts a 30-day grace period, disables the agent at 90 days if no one acts, and deletes it at 455 days. Admins cannot change those timings, and sponsors cannot re-enable a disabled agent. Only an owner or administrator can.

That policy covers inactivity. It does not cover a leaver’s agent that is still running. An agent that runs every night never reaches 60 days of inactivity, even after its sponsor has left. The owner relationship has to be checked when someone leaves.

HYPR, an identity security vendor, argues that every agent needs a verifiable identity bound to a named human owner, with a time-bounded delegation model. That is the same principle. When the owner leaves, the agent’s access has to be reviewed and reauthorized, or removed.

Ownership gaps are common. SailPoint’s research, published in a sponsored CIO.com article, found that 75% of machine identities have no designated owner. JumpCloud’s Agentic IAM Pulse Report found that 83% of organizations have no designated security leader or clear accountability for what AI agents do.

A Leaver Checklist for SaaS and AI

Use this checklist whenever someone leaves, changes role, or stops owning a tool or agent.

1. Discover every app, grant, and agent tied to the leaver. Start with the identity provider’s list of connected apps and the leaver’s OAuth grants in Google Workspace or Microsoft 365. Add AI tools signed in with a personal login, browser-based tools, and agents or automations the person set up. Check expense data for AI subscriptions in the leaver’s name. Ask the manager for a list of automations the person ran.

2. Map owners and sponsors. For each item, record who owns it now. If the leaver was the owner or sponsor, assign a replacement before changing access. Anything without an owner should be disabled until someone claims it.

3. Revoke tokens, keys, and grants. Revoke active sessions and refresh tokens. Revoke OAuth grants at both the app and the identity provider. Deactivate agent connections so they cannot request new tokens. Rotate any key the leaver’s tools or agents used, and record the time of each action.

4. Verify the revocation. Test each revoked credential against the real service. A token that still works after revocation means the offboarding is incomplete. Check the agent’s runtime, its secret store, and any tool it can still reach. Disabling a user account does not confirm that the agent has stopped.

5. Reclaim licenses and credits. Remove seats and credit allocations tied to the leaver in each AI tool’s admin console. Confirm that the removal stops the next charge. Check whether unused credits return to the pool, expire, or stay attached to the account.

6. Record the outcome. Keep a record of each item found, its owner, the revocation and rotation times, the seat removal, and the verification result. Attach it to the leaver’s offboarding ticket. An auditor or incident responder will need it.

Test the process once a quarter. Pick a recent leaver’s known tools, revoke their access, and check that each one stops working. A process that has never been tested is not yet a control.

Where OptyStack Fits

OptyStack covers the discovery and ownership steps of this checklist. It finds SaaS and AI tools using signals from spend, SSO, and browser activity, so AI tools adopted outside the directory appear in one list. It maps each tool to the people who sign in to it, flags shadow AI, and ranks each finding by risk. That shows which AI accounts belong to people who may have left.

For lifecycle, the Pro plan includes user lifecycle management and unused license reclamation, which help remove access and paid seats when someone leaves. OptyStack also acts as the identity provider for connected third-party apps, according to its identity management page. It applies IP address, device, and region conditions to sign-ins for those apps.

OptyStack does not manage agent identities inside Microsoft Entra, rotate keys in your repositories, or revoke tokens that a vendor issued. Confirm in a demo whether its leaver workflows cover AI tools and agents, and whether they revoke OAuth grants and seats in the same flow.

To see the AI accounts connected to your organization, including any that belong to people who have left, you can start a free trial.

Unlock visibility. Slash SaaS waste.

Get real-time SaaS spend insights, discovery, and optimization in OptyStack Hub—start free, no credit card required.

Sign up for OptyStack Hub
PreviousAgent Traces Are a Credential Store: What the Cursor Breach Teaches About Identity Risk

Related articles

  • Agent Traces Are a Credential Store: What the Cursor Breach Teaches About Identity Risk
    SaaS Governance

    Agent Traces Are a Credential Store: What the Cursor Breach Teaches About Identity Risk

    Cursor’s November 2026 incident update shows how a key issued to a vendor led to exposed agent traces, then to access in SaaS tools, then to a malicious extension. The credentials never passed through a human sign-in. This guide walks through the chain and gives a five-point non-human identity checklist.

    Nov 16, 2026

  • Cross-Tenant Sync Offboarding: What Microsoft’s Known Issues Mean for Your Checklist
    SaaS Governance

    Cross-Tenant Sync Offboarding: What Microsoft’s Known Issues Mean for Your Checklist

    Cross-tenant sync removes only the users it provisions, and deletion behavior depends on a setting many admins miss. This guide explains Microsoft’s documented limits, adds a Microsoft 365 offboarding checklist, and covers the February 2027 SMS and voice MFA retirement to plan for now.

    Nov 13, 2026

  • Your AI Vendor’s AI Vendor: What the Fireworks-Notion Breach Teaches About Shadow AI Sub-processors
    SaaS Governance

    Your AI Vendor’s AI Vendor: What the Fireworks-Notion Breach Teaches About Shadow AI Sub-processors

    A breach at AI infrastructure provider Fireworks exposed some Notion AI chat transcripts, and Notion turned off its Insights feature. Notion says its zero data retention promise did not cover that feature. This guide explains the lesson for AI vendor risk and gives a five-step sub-processor inventory.

    Nov 13, 2026

  • BluePhishing: Why AI Agent Consent Is the New OAuth Blind Spot (and 7 Checks for Your Entra Tenant)
    SaaS Governance

    BluePhishing: Why AI Agent Consent Is the New OAuth Blind Spot (and 7 Checks for Your Entra Tenant)

    Proofpoint’s BluePhishing research shows that one consent to a malicious AI agent blueprint can create up to 250 agent identities in a Microsoft Entra tenant. Those identities skip the controls built for people. This guide explains the proof of concept and gives seven checks for your tenant.

    Nov 12, 2026

  • Your Vendor’s App Is an Identity Too: 5 Lessons from the MSP Process Breach
    SaaS Governance

    Your Vendor’s App Is an Identity Too: 5 Lessons from the MSP Process Breach

    Stolen app secrets from MSP Process reportedly reached customer Microsoft 365 tenants with no user sign-in and no MFA prompt. This guide explains why MFA and SSO did not help, and gives a five-step third-party app permissions audit covering scopes, owners, secrets, and alerts.

    Nov 11, 2026

Keep reading

More guides on SaaS visibility, spend, and governance—jump between topics without leaving the blog.

View all posts →
  • Torii Alternatives and Freshservice SaaS Management Compared
    SaaS Optimization

    Torii Alternatives and Freshservice SaaS Management Compared

    Freshworks has agreed to acquire Torii and extend Freshservice into SaaS and AI spend management. This guide compares Torii alternatives side by side and sets out what to ask vendors about roadmap, pricing, AI spend coverage, and India support.

  • What the AU Small Finance Bank Leak Teaches Indian Companies About Third-Party SaaS Risk
    Vendor Management

    What the AU Small Finance Bank Leak Teaches Indian Companies About Third-Party SaaS Risk

    The AU Small Finance Bank data leak investigation highlights the risks of relying on third-party SaaS platforms. Explore the November 2 disclosure, five essential security checks, and a practical 30-day plan to strengthen SaaS visibility, access controls and vendor risk management.

  • Stolen AI Keys Are the New Shadow AI Bill

    Stolen AI Keys Are the New Shadow AI Bill

    Stolen AI API keys can turn hidden security gaps into unexpected bills. Explore the October 2026 AI platform breaches and learn how to inventory AI tools, assign key ownership, monitor spending, and revoke exposed credentials before costs escalate.

  • How to Offboard an Employee's AI Agents: A Checklist for IT Teams
    Best Practices

    How to Offboard an Employee's AI Agents: A Checklist for IT Teams

    Employees leave, but the AI agents they created and connected can keep running with active credentials. This checklist helps IT teams find every agent, OAuth grant, and API key tied to a departing employee, reassign or retire it, revoke access, and reclaim unused licenses.

  • AI Security Checklist for Businesses: How to Assess AI Features in SaaS Tools
    Vendor Management

    AI Security Checklist for Businesses: How to Assess AI Features in SaaS Tools

    AI features are appearing inside the SaaS tools businesses already use. Before enabling them, review what data they can access, how vendors process information, which controls are available, and whether the feature introduces new costs or risks.

  • How to Track AI Spend Per User Across GitHub Copilot, Claude, and ChatGPT
    Cost Management

    How to Track AI Spend Per User Across GitHub Copilot, Claude, and ChatGPT

    Seat counts no longer explain every AI bill. GitHub Copilot, Claude, and ChatGPT offer different usage reports and spending controls. Learn how to combine vendor billing data, identity logs, and expense records into one per-user view.

Ask the smartest LLMs about OptyStack

ChatGPTGeminiClaudePerplexityGrokCopilot
OptyStack LogoOptyStack Logo

The SaaS and AI access governance platform. Import the users you already have, then allow or deny every app sign-in.

Product

  • Features
  • Integrations
  • Pricing
  • API

SaaS Directory

  • Browse All Apps
  • Slack
  • Microsoft 365
  • Salesforce
  • Zoom
  • Zoho One

Features

  • Cost Optimization
  • Shadow IT Discovery
  • License Management
  • Contract Renewals
  • App Integrations
  • Identity & Zero Trust

Tools & Resources

  • ROI Calculator
  • Knowledge Base
  • SaaS Inflation Index
  • Compare Tools
  • Getting started with OptyStack

Company

  • About
  • Blog
  • Success Stories
  • Events
  • Careers
  • Contact
  • Review us on G2

Stay updated

Get the latest insights on SaaS optimization

© 2026 OptyStack. All Rights Reserved.

LegalPrivacy PolicyTerms of Service