Microsoft introduced a workplace chat service intended to take on Slack. It was positioned as part of Microsoft’s productivity offering and joined the longer-running enterprise social tools the company already offered.
What these workplace-chat apps do
Workplace chat apps are built around persistent, searchable conversations rather than email threads. Typical elements to look for are:
- Channels or rooms for teams, projects or topics so conversations stay organised. - Direct messages for one-to-one or small-group chats. - Threaded conversations to keep replies tied to a particular message. - Integrated file sharing and collaboration so documents are attached, previewed and opened without leaving the chat. - Built-in or add-on voice and video calling for quick meetings. - Search across messages, files and people so information can be found later. - Integrations with other services (calendars, task systems, CI feeds, helpdesk tools), plus bots or automation to reduce repetitive work. - Admin controls, single sign-on and compliance features for workplace security and governance.
Microsoft’s product was one of several major contenders created to bring these capabilities to organisations that already relied on a particular ecosystem — in this case, Microsoft’s productivity tools.
How to choose and roll a chat app out at work
Choosing a chat app isn’t just about features; it’s about fit with how your organisation actually works.
- Match to your ecosystem: If your organisation already uses a particular productivity suite, a chat app from the same vendor will often give tighter integrations with calendars, file stores and identity systems. That can simplify sign-in, file access and administration. - Prioritise discoverability and governance: Search, message retention and export options matter for knowledge sharing and compliance. Make sure admins can set policies and that you know how long messages and files are retained. - Look at integrations you’ll actually use: A long list of third‑party apps looks good, but focus on the few integrations that will make a real difference (task tracking, file storage, helpdesk, CI/CD, etc.). - Consider control and administration: For larger organisations, the ability to manage users, audit activity and apply security policies centrally is essential. - Start small and iterate: Pilot with one team or project before a company-wide roll-out. Use the pilot to define channel structure, naming conventions and etiquette. - Define simple rules: Establish basic expectations around when to use channels vs direct messages, how to name channels, how to handle notifications and how to surface important announcements. - Train and support users: Short guides, a few lunchtime sessions and visible champions help adoption more than a long rollout memo. - Manage notifications and boundaries: Chat apps can increase interruptions. Encourage people to use do-not-disturb when heads-down time is needed and to set notification preferences sensibly.
Competition among chat apps has pushed faster development and better integrations, which benefits organisations and end users. Evaluate options against how your teams collaborate day to day, and choose the tool that reduces friction rather than adds another place to check.
