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

Question

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

Joel 20

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?

Joel 20 Reputation points

2023-09-04T13:51:11.24+00:00

comment deleted

5 answers

Your answer

Joel 20 Reputation points

2023-09-04T13:51:11.24+00:00

comment deleted

Answer 1

Gary Gipstein 6

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.

Fred Beck 5 Reputation points

2024-08-19T20:19:11+00:00
On our polycoms you

unplug

LET IT SIT FOR 10 MINUTES

plug in, hold down all four corners of screen to reset the device (might be other means on other devices.. that works for mine)

It says something about an update... this must be the cause

You set the local admin password

It still fails "Can't connect to internet"

go into settings, admin mode, use that password (maybe you can skip steps if you already knew it)

I turn off DHCP and put in the address, DNS etc manually

NOW I can login to the device, etc. Not sure if this is a one off or others can use these steps. Good luck

Answer 2

Foster, Matthew 5

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.

DogPhood 0 Reputation points

2024-08-05T14:56:07.9166667+00:00

agreed - I've had the issue arise with increasing frequency recently - a reset of the device and I may be able to get the code entered before the error pops up, but it may take multiple attempts to get the device registered. When I check Entra and Intune there's nothing device limit issue - usually there's no device at all - because I couldn't register it...

Answer 3

Hello everyone, we experienced the exact same issue. The network was configured correctly, but the device did not automatically retrieve the DHCP information. Even after manually configuring the settings, it still didn’t work.

In the end, we found out that the configured NTP server was incorrect. Additionally, the previously entered NTP server was being blocked by our firewall.

The solution was to use an NTP server that is allowed through our firewall. Alternatively, you can use the Microsoft NTP server, as long as it is not blocked.

Example Microsoft NTP Server: time.windows.com

Answer 4

Suki Saniary 0

we are having same issue. any fix for this?

Catherine Kyalo 3,100 Reputation points Microsoft Employee

2024-02-13T10:55:46.5466667+00:00
The error message "Couldn't connect to workplace join. Try again or contact your admin" indicates that the device is having trouble joining the Azure Active Directory (AAD) workplace. This can be caused by a number of issues such as incorrect device settings, network connectivity problems or AAD configuration issues.

To troubleshoot the issue, I recommend the following steps:

Check the device settings to ensure that they are properly configured for AAD. You can find more information on how to configure these settings here: https://docs.microsoft.com/en-us/microsoftteams/rooms/room-devices-settings#azure-active-directory-settings

Check the network connectivity of the device to ensure that it is properly connected to the internet and that there are no network restrictions that might be blocking the connection.

Check the AAD configuration to ensure that the device is properly registered and that there are no configuration issues that might be preventing it from joining the workplace. You can find more information on how to configure AAD here: https://docs.microsoft.com/en-us/azure/active-directory/devices/overview

Answer 5

Ran Hou-MSFT 7,640 Microsoft External Staff

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.

Ran Hou-MSFT 7,640 Reputation points Microsoft External Staff

2023-09-06T01:16:03.4866667+00:00

Hi @Joel

Is there any progress on this issue?

If the reply is helpful, please click "Accept Answer" as an answer. It will help others who encounter the same issue and read this thread.

Thank you for your understanding and patience!
PS 0 Reputation points

2023-11-15T10:03:22.04+00:00

I have the same issue and have deleted out the signed in devices in intune but afterwards are still getting the same error message. Are there any other suggestions to get it working?
Linda Phillips 5 Reputation points

2024-07-19T03:42:59.3933333+00:00

same issue
André Silveira 0 Reputation points

2024-08-08T16:41:23.33+00:00

Same issue. Any progress? I appreciate any comments.
Eric Frandsen 5 Reputation points

2024-08-09T17:47:30.5833333+00:00

We just started seeing this too on our Yealink desk phones in the last week or so. We're not registering them in InTune at all, they're completely independent, so something else is going on with the Microsoft registration side.
Gary Gipstein 6 Reputation points

2024-08-13T12:51:24.46+00:00

Agree.
This just started happening at the end of last month. Up until now this notification we now seen in our environment.