Building and customizing solutions using Microsoft 365 Copilot APIs and tools
Copilot Android app does not recognize active Microsoft 365 Personal subscription, but browser works normally
Hello everyone,
I'm hoping to find out whether anyone else is experiencing this issue, or if there is a known fix.
I have an active Microsoft 365 Personal subscription purchased through Google Play. My subscription is active, renews monthly, and was recently renewed successfully.
The problem is that the Copilot Android app intermittently reports that I do not have an active subscription and sometimes blocks access to AI chat.
Examples of the messages I receive include:
- "To access Copilot, you need an active license/subscription."
- Subscription expired warnings asking me to continue my subscription.
However:
- Microsoft Account shows my Microsoft 365 Personal subscription as active.
- Google Play shows an active subscription and successful billing.
- OneDrive works normally.
- Excel works normally.
- Copilot works on my laptop.
- Copilot works in a web browser.
- Copilot also works in a browser on my phone.
The issue only appears to affect the Copilot Android application.
Troubleshooting already performed:
- Signed out and signed back in.
- Cleared app cache and app data.
- Force stopped the app.
- Uninstalled and reinstalled the app.
- Tested on both Wi-Fi and mobile data.
- Tested on multiple Android devices (Xiaomi phone and Samsung tablet).
- Confirmed that only one Microsoft account is being used.
One workaround I discovered is that signing out and back in can temporarily restore access, but the problem eventually returns.
I contacted Microsoft Support and they verified that my Microsoft 365 Personal subscription is active.
Based on the troubleshooting and testing performed, support suggested that the problem appears to be related to the Copilot Android app's subscription entitlement or licensing recognition rather than the subscription itself.
Has anyone else experienced this issue with the Android app?
If so, have you found any workaround or received further information from Microsoft?
Thank you.