The problem
Account lockouts caused by failed-login thresholds are a top-three L1 ticket category. The pattern is simple: too many bad password attempts, the account locks, the user can't work until IT unlocks it. The operation itself takes seconds, but routing the request to a human, verifying identity, and updating the user takes 10-15 minutes per ticket.
What AscendCore does
A user requests an account unlock in Microsoft Teams or Slack. AscendCore validates the lockout reason, proposes the unlock with the option for identity-factor challenge, and on approval unlocks the account in Microsoft Entra ID or Okta and resets the failed-login counter.
Workflow
- Detect — chat request (natural language or
/account-unlock <email>) - Resolve — locate the user in the IDP and confirm the lockout state
- Propose — admin approval card with lockout reason, recent login attempts, source IPs
- Approve — one-click approval (auto-execution for low-risk requests is planned)
- Execute — unlock the account and reset the failed-login counter
- Notify — user notified that they can sign in
- Audit — lockout cause + unlock approver logged
Integrations
- Microsoft Entra ID — Account-status update via Graph API
- Okta — Account lifecycle API for unlock and counter reset
- Slack + Microsoft Teams — Request and confirmation
Status
Live in production. Verified end-to-end against real Microsoft Entra ID and Okta tenants.
