Additional features, settings, or issues not covered by specific Microsoft Teams categories
A factory-reset of my device is simply not an acceptable solution for this issue =^( This an epic fail, Microsoft.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
So recently our organization decided to use Microsoft Teams for our communication. And It is working fine on Web and iPhone But no one is able to login on Android Device. Whenever we try to login on Android Device using Team App, we get this error.
There was a problem with the network. Try signing in again
I have logged in using same credentials on iOS and Web and It worked but same credentials are not working on Android.
Please guide me, how to fix this issue as it is very urgent for us.
Additional features, settings, or issues not covered by specific Microsoft Teams categories
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
A factory-reset of my device is simply not an acceptable solution for this issue =^( This an epic fail, Microsoft.
I had the same issue. Reason: MS Teams cannot properly operate together with MS Authenticator app - this will remember formerly into MS Teams logged it accounts. Solution was to remove those formerly remembered MS Teams accounts from MS Authenticator. Then the MS Teams app asked OAuth2 authentication again over web and I could log in again. No need to completely remove MS Authenticator. Certainly after successful login in MS Teams you will see again those accounts under MS Authenticator app.
But yes - it is a shame that Microsoft has not fixed that issue despite it was reported long time ago.
Hi ShabirJan,
I have consult related engineer, since the iOS and Web side can login to Teams normally, so the account should be OK. to check if it's caused by the DNS resolution failed, please go to Settings > Network & Internet > Tap the menu button (three vertical dots) > Network settings reset > RESET SETTINGS to reset his phone’s network to check it.
Meanwhile, to confirm if any group policy is assigned to this domain to block the Android devices to access the Teams for Android. please go to connect to Exchange Online PowerShell, after connecting successfully, then input following cmdlets and check the result.
Get-GPO -All -Domain "sales.contoso.com"
(Note: sales.contoso.com is your domain)
If it still doesn't work, to do further troubleshot and help you better, we also need to collect additional log information, please check my PM and share the log information for us in Private Message.
Regards,
Bryan
Hi ShabirJan,
Greetings, I am the colleague of Anna and I am here to follow up on this thread, if every one in your organization can't sign in Teams for Android, may I confirm that if it's the same Android Device? If yes, please clear the Teams Cache to see if it helps. you can tap “Settings” > “Applications” > “Manage Applications” > find your Teams app from the app entry then tap it > tap "Storage" > Tap the "Clear Cache" button to delete the cache > return to Android’s home screen > restart your Teams app > sign in your account again and check the result.
If it still doesn’t work, please provide us your accurate account environment, could you please contact your admin to confirm this? Hybrid, on-premises Office 365 pure cloud.
Regards,
Bryan
Hi Bryan
Thanks for getting back. To answer your questions. No we are facing issues on different android devices used by other colleagues.
I followed the steps you mentioned, Cleaned and deleted the email app (Curious why email app) restarted the email app and logged in using my enterprise account and I was able to login in the email app. But again tried the Teams login and getting the same old error I shared before.
Our Office365 is on-premise account environment.
Waiting for update from you,
Hi Bryan
Rather than doing Network reset, I did factory reset on my Android Device, I have the same issue. I ll share additional logs in private message.