Microsoft teams can't open on my iPhone mobile and it keeps " Loading "

Question

Microsoft Teams app isn't working on my new mobile ( iPhone 12 Pro Max ) After authentication and such, it just gets stuck at "loading"

I tried below steps, but still I can't access it, so any advice please.

• App reinstalled several times.
• Account removed and re-configured in Teams app.
• Tested with different networks (both WiFi and cellular).
• Tested after removing private network from WiFi connections.
• Cleared app data for Teams in phone settings.

Answer 1

@Mohammad Qattash ,

Does anyone else have the same issue?

Could you log in with other mobiles?

I didn’t get an iPhone 12 Pro Max. I only tested in iPhone 12 (version: 14.3). It worked with no problem.

To exclude account side issue, try to log in other types of Teams client, such as desktop client, web client. Then, observe the results.

Besides, you could contact your IT administrator to check if he creates some conditional access policies in Azure Active Directory admin center to block the mobile platform in Teams.

For more details about Conditional Access, refer to by this link.

---

If the response is helpful, please click "Accept Answer" and upvote it.

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 2

Yes, I am having the same issue. After launching the application using the organization email, it seems to start a SSO page without an option to enter the new password. Not sure if there is a place to disable the single sign on page so I can enter the password manually. Somewhere in the middle the login is stuck with the old ldap password. I have the same issue on Outlook app on the phone. But when you hit cancel, the login screen comes up with the password field so I can eventually enter the new password. But for Teams it does not have that option.

Answer 3

I have the same issue,
The app is stuck, very laggy. Impossible to typ

Removed the app and reinstalled it,
Did not help for me.

There is also no CA policy that is causing this problem