Forum Discussion
DanHuber
Nov 20, 2019Iron Contributor
Some questions to Microsoft Teams Room hardware and Office 365 tenant setup
I understand that Microsoft Teams Room (MTR) is best implemented with dedicated hardware running the specific Windows 10 IoT image and supported periphery, i.e. Logitech Rally (let's call the whole o...
DanHuber
Nov 20, 2019Iron Contributor
Hello StevenC365 (and Vesa Nopanen ),
Thanks both of you for the extended answers.
I think I'll offer Logitech Tap with Logitech Rally to the customer. That would be a supported MTR configuration. Your arguments have convinced me to do this in favor of using a simple BE license.
Yet I still would like to comment on a few points StevenC365 made:
- I found a nice explanation on MTR setup on Office 365 on youtube. Actually, one creates a standard room and then assigns the MR license to it. So an MTR is acting exactly like a room resource, including AutoAccept and such.
- I need to look into Microsoft 365 Business Voice, also for another project. Thanks a lot for the pointer. Although, it could be that it won't be available in my country (Switzerland) for some time. Only recently, Direct Connect became available. Microsoft Dial Plan is still not offered here. I am playing with the thought of using the MTR license to connect to one of the two providers offering their own SBC to connect to. Though Swisscom will probably not be interested in SME customers for that service. The other starts only to be interesting when I move over all telephony to them.
- "Set-CalendarProcessing <...> -AutomateProcessing AutoAcceppt" won't work for BE licensed users. The cmdlet will tell me that this is only for resources. Invitation AutoAccept for users is apparently only possible by setting an option in Outlook and it has to be running all the time. Not really useful for a meeting room. Perhaps Microsoft Flow could do it, but I have not really investigated into that direction (yet).
Dan
StevenC365
Nov 20, 2019MVP
- The only real difference to a standard resource that you would create in exchange is that you configure it to allow logon, i.e. have a password then assign licenses to it.
- Just to flag the term used in US documentation is direct routing. A model of having this hosted by a third party is a good one but I wonder how small they will want to go. Even though their carrier grade SBC support multiple virtual clients it will in effect be more expensive per port for smaller clients. I expect this is why Microsoft are offering it alongside their calling plans. I know it took a long time for this feature to be cost viable for Microsoft to offer.
- Sorry I don't have any BE tenants to test, maybe there's a license limitation but it's news to me.