![]() The account is correctly "disabled" both in local AD and in AAD and is listed as a resource in the on premise ECP.Īny pointers or heads up on what could be wrong? Should I try to scrap the user account and recreate it from scratch? Maybe it's due to the fact that we have only on premise mailboxes and only synch AD users to AAD so this Exchange resource account (Room) does not synch correctly to the Teams Admin portal for some reason? I've also noticed that it is not listed as a device under the 365 admin panel. One thing I am not certain of is if this is enough at least for a trial setup (Teams Exploratory instead of a Microsoft 365 Basic license for ex.) so please confirm if I need any other license at least for trial purposes.Īfter having setup the account on the Tap (did not join it to AD) it doesn't appear in the Teams Rooms Devices. ![]() Created Room mailbox as per following guide:Ĭurrently I enabled a 30 day trial Teams Rooms license and have Teams Exploratory assigned to the Rooms account. Steps I took: created user in local AD, synched correctly to AAD. Jockey is committed to quality, comfort, fashion and innovation. poplin fabric thats colorfast, wrinkle resistant, and shrinkage controlled Jockey apparel products are sold in major department and specialty stores in more than 140 countries around the world. What our setup is: On Premise Exchange (2016 CU12), domain synched to AAD. FUNDAMENTALS utilize a market proven, high-performance 65/35 poly/cotton 4.25 - 5.0 oz. We're attempting to install the TAP Rooms solution - but the device does not appear in the Teams Rooms devices (though we could initiate a call).
0 Comments
Leave a Reply. |