New personal outlook.com accounts ship with IMAP OFF by default, so OAuth succeeds but the IMAP AUTHENTICATE step fails — a confusing dead-end (on-device 2026-07-06). #390 handles this reactively (detect the failure -> tell the user to enable IMAP). This ticket handles it proactively: an interstitial shown when the user taps Outlook in onboarding, before launching auth.
The screen (tap "Outlook" in onboarding -> this screen, before the OAuth flow)
A prompt asking whether IMAP is enabled — e.g. "Have you enabled IMAP for your Outlook account?" — with a short explanation that new Outlook accounts often have IMAP turned off and the app needs it.
A link to Microsoft's help article on enabling IMAP (canonical MS doc — verify the current URL, likely the "POP, IMAP, and SMTP settings for Outlook.com" support article).
A link to Outlook account settings (where to toggle it: Outlook.com -> Settings -> Mail -> Sync email -> "Let devices and apps use POP/IMAP"; use a deep link if one exists, else the settings URL).
At the bottom of the visual hierarchy, a "Sign In" button that continues the existing Outlook auth flow (the AppAuth / in-app-browser OAuth path).
Behavior / scope
The screen sits between tapping "Outlook" and launching OAuth; "Sign In" triggers the existing Outlook OAuth (no change to the auth mechanism itself). Links open in a browser (external or in-app custom tab).
Outlook-only (the provider with the IMAP-off-by-default gotcha); other providers' onboarding is unchanged.
DoD
Unit tests (screen state + the nav: tap Outlook -> IMAP screen -> Sign In -> OAuth) + instrumented/E2E for the onboarding flow; PII-free AppLog on the navigation. Copy + the exact MS/settings URLs finalized in the PR. Relates to #390 (reactive complement), the onboarding epic, and the Outlook login flow.
## Context
New **personal outlook.com** accounts ship with **IMAP OFF by default**, so OAuth succeeds but the IMAP `AUTHENTICATE` step fails — a confusing dead-end (on-device 2026-07-06). **#390** handles this *reactively* (detect the failure -> tell the user to enable IMAP). This ticket handles it **proactively**: an interstitial shown when the user taps **Outlook** in onboarding, *before* launching auth.
## The screen (tap "Outlook" in onboarding -> this screen, before the OAuth flow)
- A prompt asking whether IMAP is enabled — e.g. **"Have you enabled IMAP for your Outlook account?"** — with a short explanation that new Outlook accounts often have IMAP turned off and the app needs it.
- A link to **Microsoft's help article** on enabling IMAP (canonical MS doc — verify the current URL, likely the "POP, IMAP, and SMTP settings for Outlook.com" support article).
- A link to **Outlook account settings** (where to toggle it: Outlook.com -> Settings -> Mail -> Sync email -> "Let devices and apps use POP/IMAP"; use a deep link if one exists, else the settings URL).
- At the **bottom of the visual hierarchy**, a **"Sign In" button** that **continues the existing Outlook auth flow** (the AppAuth / in-app-browser OAuth path).
## Behavior / scope
- The screen sits between tapping "Outlook" and launching OAuth; "Sign In" triggers the existing Outlook OAuth (no change to the auth mechanism itself). Links open in a browser (external or in-app custom tab).
- **Outlook-only** (the provider with the IMAP-off-by-default gotcha); other providers' onboarding is unchanged.
## DoD
Unit tests (screen state + the nav: tap Outlook -> IMAP screen -> Sign In -> OAuth) + instrumented/E2E for the onboarding flow; PII-free AppLog on the navigation. Copy + the exact MS/settings URLs finalized in the PR. Relates to **#390** (reactive complement), the onboarding epic, and the Outlook login flow.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Context
New personal outlook.com accounts ship with IMAP OFF by default, so OAuth succeeds but the IMAP
AUTHENTICATEstep fails — a confusing dead-end (on-device 2026-07-06). #390 handles this reactively (detect the failure -> tell the user to enable IMAP). This ticket handles it proactively: an interstitial shown when the user taps Outlook in onboarding, before launching auth.The screen (tap "Outlook" in onboarding -> this screen, before the OAuth flow)
Behavior / scope
DoD
Unit tests (screen state + the nav: tap Outlook -> IMAP screen -> Sign In -> OAuth) + instrumented/E2E for the onboarding flow; PII-free AppLog on the navigation. Copy + the exact MS/settings URLs finalized in the PR. Relates to #390 (reactive complement), the onboarding epic, and the Outlook login flow.