Couldn't connect to workplace join. try again or contact your admin

Question

Good day

We have bought a Yealink Meetingboard 65, started it up and logged in. We then held our first test meetings with a normal, personal account.

We thought a firmware update would be useful. After a successful update, we are now unable to log into teams.

We then reset the device to factory settings for troubleshooting, without success.

We tried: Several other logins, restarts, we checked the device limit per user (unlimited), network, login with hotspot, licensing with teams room pro, intune policies, we checked the box under andoid registration settings "use device administrator".

When I try to log in, at first the error message "This device is not registered with the device administrator." comes. Then its written "Couldn't connect to workplace join. try again or contact your admin".

For some users it works but for some it doesnt. There is a difference in licensing.

Can somebody help us?

Answer 1

I've seen this issue on several forums and the response tends to lean toward device limit in intune. The issue is, this error pops up before a user can log in and AFTER it has been factory reset. There is no user tied to it yet.

Answer 2

Hi @Joel

Thanks for visiting our forum. Microsoft Teams tag is mainly focused on the general issue of Microsoft Teams application troubleshooting. Based on our search, this error message appears to be about Intune. The following is for informational purposes only.

---

Based on our searches, this error usually indicates that the signed-in user has reached the device limit in Intune/Endpoint Manager. Here's a related blog, please refer to:

Couldn’t connect to Workspace Join. Try again, or contact your admin | by Graham Walsh | Medium.

(Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.)

Hope the above information is helpful for you!

---

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

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 3

we are having same issue. any fix for this?

Answer 4

We are seeing this issue with newly remote provisioned phones.
We are also now seeing it with phones that were logged in, but passwords may have to be reset or simply a reboot of the phone.
These phones are in varying locations.

All of our phones in 1 location were operational, now 20% of them are getting this issue. It's random as to if one will login or not.

1- the accounts do not show multiple devices.
2- the login says it's successful in Teams admin
3- other phones on the same data path are operational (no switch or fw issues).

Trouble shooting is not the best with no further data. We'll be submitting a ticket with support.