{"id":5291,"date":"2023-08-14T07:36:14","date_gmt":"2023-08-14T05:36:14","guid":{"rendered":"https:\/\/www.msb365.blog\/?p=5291"},"modified":"2023-08-31T08:01:27","modified_gmt":"2023-08-31T06:01:27","slug":"fix-teams-phone-device-rollout","status":"publish","type":"post","link":"https:\/\/www.msb365.blog\/?p=5291","title":{"rendered":"Fix: Teams Phone Device Rollout"},"content":{"rendered":"

Depending on the tenant configuration, there may be problems with the rollout of Team Certified phones.
\nHere is a solution:<\/p>\n

Teams Certified phones can be rolled out in different ways. These rollouts generally work very well. If not, however, troubleshooting can become a considerable challenge.<\/p>\n

When a company plans a rollout, there are several points that need to be considered in preparation. These points are very well described in the following Technet article<\/a><\/strong>.<\/p>\n

From time to time, however, problems can occur with a tenant regardless of the rollout method used.
\nIn the case I describe in this article, we tried the following two variants:<\/p>\n

 <\/p>\n

Normal rollout:<\/h3>\n

The device was connected to the network and the user tried to register on the new phone together with the device authentication. The registration failed with the following message:<\/p>\n

\"\"<\/p>\n

The message on the picture is in German, but translated into English the error message means the following:
\nLogout in progress…<\/em><\/strong>
\nRegistration in Intune has failed. Try again or contact your administrator.<\/em><\/strong><\/p>\n

When we look at the Teams Admin Center, the device is displayed after several attempts, but we also see that no user is logged on.<\/p>\n

\"\"<\/p>\n

Even with our second variant of registering the device with a user via the Teams Admin Center, this process is aborted.<\/p>\n

What next? Registration via the MAC address was also unsuccessful, with the same result.<\/p>\n

 <\/p>\n

The solution<\/h3>\n

Most of the time, the solution is just a click away. After also checking the sign-in logs, we could not identify the error.<\/p>\n

Teams Devices are added to a tenant through the Intune registration process, but are subsequently deposited and managed in the Teams Admin Center.<\/p>\n

In our case, it was still an Intune configuration that we had to adjust in order to find the solution.<\/p>\n

The following steps then led us to the desired solution:<\/p>\n\n\n\n\n\n
\"\"<\/td>\nIn the Intune Admin Center, browse to Devices<\/strong> > Enroll devices<\/strong>.<\/td>\n<\/tr>\n
\"\"<\/td>\nGo to Enrollment device platform restrictions<\/strong><\/td>\n<\/tr>\n
\"\"<\/td>\nIn our specific case, the Android devices administrator<\/strong> option was set to Block<\/em>. We changed this setting to Allow<\/strong><\/em>.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

 <\/p>\n

After adjusting this setting, we restarted the onboarding process…. This time with success:<\/p>\n

\"\"<\/p>\n

 <\/p>\n

Additional Points<\/h3>\n

 <\/p>\n

During this troubleshooting process, we became aware of several factors. When troubleshooting, please ensure that the devices do not get stuck with a conditional access policy.<\/p>\n

 <\/p>\n

One approach to solving this problem can be the following:<\/p>\n

 <\/p>\n

Create a dynamic Azure Active Directory group that is tailored to your hardware. As an example at Yealink:<\/p>\n

Dynamic membership rules: (device.devicePhysicalIds -contains “Yealink”) or (device.deviceManufacturer -contains “Yealink”) or (device.displayName -contains “Yealink”)<\/strong>.<\/p>\n

 <\/p>\n

This Dynamic Group can then be added to the Conditional Access Rules as an “Exclude”. This way we make sure that this does not cause any problems.<\/p>\n

 <\/p>\n

This is only a variant and is applicable depending on the security directives of the respective companies.<\/p>\n

 <\/p>\n","protected":false},"excerpt":{"rendered":"

Depending on the tenant configuration, there may be problems with the rollout of Team Certified phones. Here is a solution: Teams Certified phones can be rolled out in different ways. These rollouts generally work very well. If not, however, troubleshooting can become a considerable challenge. When a company plans a rollout, there are several points […]<\/p>\n","protected":false},"author":1,"featured_media":5336,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_crdt_document":"","om_disable_all_campaigns":false,"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"_uf_show_specific_survey":0,"_uf_disable_surveys":false,"footnotes":""},"categories":[1923,1988,15],"tags":[],"class_list":["post-5291","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-microsoft-365","category-ms-intune","category-ms-teams"],"post_mailing_queue_ids":[],"_links":{"self":[{"href":"https:\/\/www.msb365.blog\/index.php?rest_route=\/wp\/v2\/posts\/5291","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.msb365.blog\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.msb365.blog\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.msb365.blog\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.msb365.blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=5291"}],"version-history":[{"count":3,"href":"https:\/\/www.msb365.blog\/index.php?rest_route=\/wp\/v2\/posts\/5291\/revisions"}],"predecessor-version":[{"id":5300,"href":"https:\/\/www.msb365.blog\/index.php?rest_route=\/wp\/v2\/posts\/5291\/revisions\/5300"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.msb365.blog\/index.php?rest_route=\/wp\/v2\/media\/5336"}],"wp:attachment":[{"href":"https:\/\/www.msb365.blog\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=5291"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.msb365.blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=5291"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.msb365.blog\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=5291"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}