There are no documented general compatibility limitations for Microsoft 365 mobile apps on Android 13 in the provided information. Microsoft 365 mobile apps (Outlook, Teams, Office, Word/Excel/PowerPoint, OneDrive, etc.) are listed as supported on Android, including in modern authentication scenarios such as Microsoft Entra certificate-based authentication.
From the context, the following points are relevant to the scenario:
- Supported Microsoft 365 mobile apps on Android
- Microsoft mobile apps such as Outlook, Teams, Office (mobile), Word/Excel/PowerPoint, OneDrive, and others are explicitly listed as supported on Android for modern authentication scenarios.
- This indicates that, in general, these apps are expected to work on current Android versions when device and app requirements are met.
- General sign-in troubleshooting for Microsoft 365 mobile apps
- For Microsoft 365 or Office apps on Android, sign-in is expected to work by opening the app, tapping Sign In, and using either a Microsoft account or a work/school account associated with Microsoft 365.
- If sign-in fails, guidance includes:
- Verifying that the correct account type is used (personal Microsoft account vs. work/school account).
- Verifying that the username and password work by signing in via a browser to the appropriate Microsoft 365 sign-in location.
- Checking that the device meets the system requirements for the apps.
- Outlook/Office mobile sign-in issues on Android
- If sign-in fails or behaves unexpectedly in Outlook mobile, the guidance is:
- Use the sign-in helper for Microsoft personal accounts.
- For work or school accounts, use the self-service password reset option if enabled, or contact the tenant administrator.
- Ensure the latest version of Outlook/Office mobile is installed, as recurring prompts or failures can be related to updated security standards.
- For some Android devices, adding or syncing Microsoft 365 accounts in Outlook can fail when another Microsoft app (such as Authenticator or Company Portal) is present and restricted by power-saving or background limitations. Recommended actions include:
- Turning off power-saving mode or adjusting settings so the app can launch other apps.
- Disabling power optimization for Authenticator/Company Portal so they can run in the background.
- Opening Authenticator/Company Portal before Outlook to ensure they are active.
- Known device/app interaction issues
- Some specific Android models can experience issues adding or syncing Microsoft 365 accounts in Outlook when device power-management settings prevent required background components from running. Adjusting those settings typically resolves the problem.
- Known issues or changes with embedded browser/modern auth on Android
- The provided context does not list any specific, known global issues with embedded browser authentication or recent breaking changes to modern authentication flows on Android 13.
- The context confirms that modern authentication scenarios (including certificate-based authentication and security keys) are supported for Microsoft mobile apps on Android, which implies that the underlying modern auth stack is expected to function.
Based on the available information, the behavior described (blank white screen, stuck at “Taking you to your organization's sign-in page,” or “That Microsoft account doesn’t exist”) is not documented as a general Android 13 compatibility problem. It is more likely related to one or more of the following, which should be checked with the tenant administrator and on the device:
- App or device configuration issues (e.g., outdated app version, power optimization or background restrictions affecting Authenticator/Company Portal or the embedded sign-in component).
- Account type mismatch (using a work/school account but selecting Microsoft account, or vice versa, during sign-in).
- Tenant-specific policies or conditional access rules that affect mobile app sign-in differently from browser sign-in.
If basic checks (correct account type, browser sign-in works, latest app versions, and relaxed power/background restrictions for Microsoft apps) do not resolve the issue, escalation through the tenant administrator is appropriate so that tenant policies, sign-in logs, and conditional access can be reviewed.
References: