Enrollment Failure and Authentication Prompt Issues
Secret Double Octopus Helpdesk Guide
Level 1 support steps for incomplete enrollment and missing authentication prompt issues
Overview
This article helps Level 1 support teams resolve two common rollout and day-to-day support scenarios: users who are not fully enrolled and users who are not receiving an authentication prompt.
These issues are common during deployment, device replacement, and policy-driven login flows. Fast resolution helps maintain user confidence and supports adoption.
Why This Matters
- These issues commonly occur during rollout and expansion phases.
- If enrollment is not smooth, pilots can stall and adoption can slow down.
- Missing authentication prompts are subtle, frequent, and confusing for end users.
- Fast resolution improves confidence and reduces unnecessary escalations.
Scenario 1: Enrollment Failure / User Not Fully Set Up
Typical Root Causes
- Incomplete setup steps
- Device compatibility issues
- User error during setup
What Tier 1 Must Do
- Confirm exactly where the enrollment failed.
- Restart the enrollment process if needed.
- Verify device compatibility.
- Verify network connectivity.
- Guide the user step-by-step through the setup process.
- Validate that authentication succeeds after enrollment completes.
Scenario 2: User Not Receiving Authentication Prompt
Typical Root Causes
- Push notification issues
- Device offline
- Authentication app or service not triggering correctly
- Policy misconfiguration
What Tier 1 Must Do
- Confirm the user device is online.
- Check that the authentication app or service is functioning correctly.
- Validate that the correct policy is applied to the user and device.
- Trigger a new authentication attempt.
- Reset the authenticator or related flow if needed.
- Confirm the authentication prompt is restored.
Required Knowledge Base Coverage
Level 1 support should be familiar with the following knowledge base topics:
- Enrollment Troubleshooting Guide
- First Login Experience
- Device Registration Process
- Authentication Prompt Issues
- Troubleshooting Login Failures
- Policy Configuration
Recovery Actions When the Primary Fix Fails
If the primary troubleshooting steps do not resolve the issue, use one of the following recovery actions:
User Bypass
Use temporary bypass only when necessary to restore immediate user access while troubleshooting continues. Confirm bypass is applied correctly and document the action before closing or escalating the case.
Re-enroll Users
If setup is incomplete, corrupted, or the authentication flow is no longer working as expected, remove the existing setup and guide the user through a full re-enrollment process.
Success Metrics
- User successfully enrolled during the same support session.
- Authentication prompt restored quickly without escalation.
Notes for Helpdesk Technicians
Always document where the failure occurred, what was validated, and whether recovery actions such as bypass or re-enrollment were used. Clear documentation helps reduce repeated troubleshooting and supports clean escalation when required.