Security Policy Errors

Fix Microsoft 365 iOS App Sign-In Error 2002 on Managed iPads

Olivia MillerOlivia Miller Oct 10, 2026 868 views

Question details

Users need to know which URLs to whitelist to resolve sign-in errors in Microsoft 365 apps on managed iPads.

How to Fix Microsoft 365 iOS App Sign-In Error 2002 on Managed iPads
Product
Microsoft 365
Device & OS
iOS / iPadOS
Scenario
Attempting to sign in to Microsoft Word, Excel, or PowerPoint on iPads managed by MDM solutions like JAMF or filtered by Sophos.
Observed behavior
The apps display sign-in error 2002 because the required Microsoft authentication URLs are blocked by network web filters or MDM policies.
Before you start

Ensure you have administrative access to your organization's Mobile Device Management (MDM) portal (e.g., JAMF) or network web filtering software to modify URL whitelist policies.

Solution 1Recommended

Whitelist Required Microsoft 365 Authentication URLs

Add the essential Microsoft 365 endpoints to your MDM or web filter allowed list to permit app sign-in.

Network filters and MDM solutions block unapproved traffic by default. Allowing the specific authentication domains used by Microsoft 365 ensures the iOS apps can successfully connect to Microsoft's servers.

1
Access Network Policies

Log in to your MDM portal (such as JAMF) or your web filter dashboard (such as Sophos) and navigate to the web filtering or URL allowlist section.

2
Add Official Microsoft 365 URLs

Consult the official 'Microsoft 365 URLs and IP address ranges' documentation and add the required authentication endpoints, including learn.microsoft.com.

3
Whitelist the Specific ODC Endpoint

Explicitly add odc.officeapps.live.com to your allowed list. DNS trackers indicate this specific URL is heavily relied upon for iPad authentication.

4
Deploy the Policy

Save your changes and push the updated network payload or policy to the managed iPads, then attempt to sign in again.

Whitelist Required Microsoft 365 Authentication URLs
Instant Resolution: Whitelisting odc.officeapps.live.com frequently resolves the 2002 error instantly on Sophos-managed and JAMF-managed networks.
Free Microsoft Office alternative

Try WPS Office for a Seamless Document Experience on iOS

If managing complex Microsoft 365 authentication policies and sign-in errors becomes cumbersome on managed devices, consider WPS Office. It is a lightweight, highly compatible alternative that allows users to seamlessly edit Microsoft Office files without the heavy sign-in and network overhead.

  1. 1. Install on iPads: Deploy WPS Office to your managed iPads via Apple Business Manager or download it directly from the App Store.
  2. 2. Open Documents: Launch WPS Office and open your existing Word, Excel, or PowerPoint files without encountering strict sign-in hurdles.
  3. 3. Edit and Save: Use the robust editing tools and save your documents locally on the iPad or to a designated cloud storage service.
Fully compatible with Microsoft Office formats including .docx, .xlsx, and .pptx.Lightweight app optimized for iPads and managed iOS environments.No complex authentication blocking—start editing files instantly.Free to use with a familiar, user-friendly interface.
QA img-9

Frequently Asked Questions

What does error 2002 mean in Microsoft 365 iOS apps?

Error 2002 typically indicates a network connectivity or authentication block where the app cannot reach Microsoft's sign-in servers, often due to strict web filters or MDM policies on managed networks.

Which specific URL usually fixes the iPad sign-in issue?

Allowing 'odc.officeapps.live.com' through your web filter, Sophos, or JAMF policy often resolves the authentication block on managed iOS devices.

Can I use IP addresses instead of URLs for the whitelist?

While possible, Microsoft highly recommends whitelisting by FQDN (Fully Qualified Domain Name) because Microsoft 365 IP addresses change frequently, which could lead to repeated sign-in failures.

Why does this error primarily happen on managed iPads?

Managed devices deployed via platforms like JAMF or Sophos usually have stricter outbound traffic rules and DNS filtering. If the necessary Microsoft authentication endpoints aren't explicitly allowed in the deployment profile, the connection is dropped.