Line Keys on Hardphones
how do you all manage the line Keys on Hardphones (Yealink M56 E2 with Key Module)? We have some trouble with users swithcing phones as all manually configured keys gets lost after sign out. I know that i can configure the shortcut in the teams client to get the colleagues on the keys but most of the users want to have the "consult and transfer" option on there keys. Anynone know if there is a way to configure the keys in the user profile ?
Poly devices and the transition to Android Open Source Project (AOSP)
Today we had a handful of our Poly Teams meeting devices sign out and then refused to re-enroll afterwards. Our devices included Poly Studio X30, X50, X70 and TC8 touch panels. on the screens that were attached to the equipment, upon failure of sign-in and re-enrollment we saw a message on the screen saying "Signing out... This device isn't enrolled in device administrator. Contact your admin". The devices were still available in the Teams admin center so I was able to retrieve diagnostics from the devices. Within the CompanyPortalEventsLog* file in the root of the zip file containing the diagnostic data there was the following line TIMESTAMP CompanyPortalReasonCode: WORK_PLACE_JOINED CompanyPortalStatus: UNKNOWN FailureReason: ENROLLMENT_RESTRICTIONS After further investigation, the devices also had updates applied to them during the early morning hours. After some searching and reading through this article Moving Teams Android Devices to AOSP Device Management | Microsoft Community Hub - even though my devices weren't supposed to be available until February, I followed Step 1 to create an enrollment profile for Android Open Source Project (AOSP) with the settings outlined. However, in my tenant, "For Microsoft Teams Devices" was still being marked as preview. Once this profile/policy was in place I was successful in logging our devices in with their resource accounts. Lucky us that it happened on Friday and not one of our core work days. So, watch out for your Android Teams Room devices with this change/transition happening. Try to work ahead of it to prevent Teams Meeting Room Android devices and Android phones from experiencing downtime in your offices and set the policy up as soon as you can. There's a secondary step to make sure to have a Compliance policy in place for AOSP devices as well, be sure to have that set up so that your devices are still flagged as Compliant in your tenant. https://learn.microsoft.com/en-us/mem/intune/protect/compliance-policy-create-android-aosp If anyone else sees any other symptoms of this issue post them to this thread to help others troubleshoot.
Teams phones and firewalls
A customers network people created a separate vlan for the Teams phones. When trying to use either the "Web Sign-in (Cloud)" or "CAP provisioning", they get "Web Sign-in (Cloud) failed Signing Out". Are the firewall ports required for the phones the same found in the full IP and URL list? They never get the web address link and code to sign in.