Teams Insider

Michael Tressler, from Tandy RadioShack to Microsoft to Jabra

Prefer audio?

Who should listen: Microsoft 365 service owners and UC/AV professionals evaluating Android-based Teams Rooms, planning device lifecycle and refresh, or assessing intelligent speaker and multi-stream ahead of Copilot rollouts — plus anyone interested in the career path from on-premises voice into the device ecosystem.

Guest: Michael Tressler — Senior Solutions Consultant, Jabra

Michael Tressler, Senior Solutions Consultant at Jabra and formerly of Microsoft's device partner team, traces his career from BASIC on a Tandy TRS-80 through Windows NT consulting, OCS and Lync deployments at Deloitte, authoring the Teams Rooms and Teams Android partner boot camps, and now pre-sales for Jabra's video portfolio. The conversation covers PanaCast camera engineering, intelligent speaker's new relevance with Copilot, and what a Microsoft-built Android for Teams devices would mean for OEMs.

Many thanks to Jabra, sponsor of this episode.

Key insights

The migration from Microsoft Mail to the first version of Exchange had no tooling — a colleague documented an 83-step manual process, including individual 'click OK' steps, with no bulk import from the MS Mail post office. ▶ 10:11
Tressler paused an in-flight OCS 2007 R2 rollout at around 75 users when he heard Lync was two months away, and migrated straight to Lync instead — a decision made easier by the fact that LCS had only ever been trialled with 15–20 people. ▶ 12:42
Microsoft's Teams Rooms Windows training existed because partners told device partner sales they wouldn't sell the product they didn't understand — a lack of enablement was a direct sales blocker. ▶ 22:53
The term 'Resource Account' for Teams Rooms was chosen by Tressler and Nate Smyre because Docs used three different names for the same object; it stuck simply because it is an Exchange resource account. The Surface Hub team still says 'device account'. ▶ 25:27
The PanaCast 50's 180-degree view comes from three 13MP 4K sensors at 80 degrees each, real-time stitched with a dynamic seam that can shift between 0 and 30 degrees of overlap to keep a person inside a single sensor rather than across the join. ▶ 37:10
Intelligent speaker was a niche compliance feature for regulated users needing named transcripts; Copilot and Teams Premium intelligent meeting recap now make named attribution valuable to everyone, and Jabra's bar removes the need to run USB cables to table pucks. ▶ 41:45
Tressler expects Microsoft's own Android for Teams devices in the first half of 2024 (his estimate, not engineering's), and argues its real appeal is security sign-off: a security team choosing between an OS a headset vendor shipped a month ago and one from a company that has shipped operating systems for 45 years. ▶ 45:19
Feature staggering across Android room devices — Neat and Yealink on one date, Logitech weeks later — stems from each OEM's own firmware cycle; a common Microsoft-built Android would leave OEMs responsible only for drivers and could deliver same-day feature parity, as already happens on Teams Rooms Windows. ▶ 49:51
Android room device lifespan is governed by chipset choice plus AOSP support for that chipset, not the vendor's stated three-to-five-year warranty; buyers need to know where in the Android lifecycle a device sits, and distributors often don't. ▶ 46:49