well, this is a great overview, but there are substantial lacks that make Admins' life extremely difficult.
When MS moved away from the Common Area Phone License to the Shared Device License, they have removed the option to run the MeetingSign in mode default calendar view (or calendar as a whole at all as it seems). To give those phones the full user experience is way too much, and giving them the calls only experience is way too less.
Which means, for Common Area Phones that are the Yealink CP96x or the Poly Trio (voice only devices), you either need to assign an Fx-License with PhoneSystem - which for those Devices is overkill - they simply need to call... Or you assign the Meeting Room Pro, which is complete overkill. (or Basic - yes, but 25 free licenses for a 10.000+ user company - you do not come very far with that...)
in turn, it is stated here, that "People, Walkie Talkie and Voicemail" can be enabled with the CommonAreaPhone Signin, by enabling advanced calling. Problem: if i want the CAP experience only, but the Phone(-account) itself should be part of a Call Queue/Group Pickup, i am screwed as well. quote: ("
Then, choose from the below home screen experiences you want to enable for your users. On touch and non-touch phones you can choose to enable one of the following experiences:
- Basic Calling Experience: On an account signed in with CommonAreaPhoneSignIn mode you can offer a basic Dialpad and Speed Dial view by disabling the “https://learn.microsoft.com/en-us/microsoftteams/set-up-common-area-phones#step-6---set-up-advanced-calling-on-common-area-phones-optional” setting."
Then, a little off topic,
What to do if you want a shared device (android smartphone, not Teams Phone) enrolled in intune as such and with an F- or E- Licensed user signed in to receive the reduced Teams Android client experience - similar as an account that would sign in with a Shared Device License?
Also off topic: on Android devices (Teams Phone + Android Smartphone) the Teams client when attempting a new call in the dial pad view and search is enabled, a "," (comma) is NOT accepted when searching. it simply is ignored. A Ticket with MS lead to nowhere and the statement was that the issue does come from the underlying SDK, where Teams is programmed with... (sigh...). (Workaround option suggested: "Do not use commas in Displaynames"...) (sigh)
(btw - my list is longer...)