The problem
When a user loses their MFA device or needs to re-enroll a new authenticator, existing factors must be revoked and re-enrollment guided through a secure flow. Without automation, this requires multiple help desk touches plus out-of-band identity verification — often during business hours when the user can't access any of their tools. The user is locked out, the engineer context-switches, and the SLA breaches.
What AscendCore does
A user requests an MFA reset in Microsoft Teams or Slack. AscendCore proposes factor revocation and enrollment-link generation against the user's identity provider. An IT admin sees the user's currently-enrolled factors, approves with one click, and AscendCore revokes the existing factors and delivers a time-limited enrollment link to the user via DM.
Workflow
- Detect — user message in Teams or Slack ("reset my MFA" or
/mfa-reset <email>) - Classify — intent + target user resolved against the IDP
- Propose — admin approval card with currently-enrolled factors visible
- Approve — one-click human approval (always required)
- Execute — revoke push, SMS, TOTP, hardware-key factors at the IDP
- Generate — enrollment link with configurable TTL (default 30 minutes)
- Deliver — link sent via DM with onboarding instructions
- Audit — every action logged with approver identity, factor list, timestamp
Integrations
- Okta — Factor lifecycle API for revocation and enrollment
- Microsoft Entra ID — Authentication methods API
- Slack + Microsoft Teams — DM delivery for the time-limited enrollment link
Status
Live in production. Used in real Okta and Microsoft Entra ID tenants today with verified end-to-end execution and audit trail.
