Why Teams Underdelivers in Most Organisations

Microsoft Teams ships major updates every month. By the time a typical organisation finishes its initial rollout, some of what was deployed is already out of date. New features arrive quietly, without a rollout plan. Governance settings default to something reasonable but not necessarily right. Users develop workarounds around friction points that could have been solved with a configuration change.

The result is an environment that technically works – but does not perform.

For a 200-seat organisation on Microsoft 365 Business Premium, the annual licence cost is in the range of AU$100,000–$120,000 per year. Getting full value from that investment requires more than deployment. It requires ongoing management, governance, and a team that knows what the platform is capable of.

Area 1: Calling and Telephony Configuration

Teams Calling is one of the most underutilised components of the Microsoft 365 stack – and one of the areas with the highest potential return.

For organisations that have migrated from a legacy PBX or are considering doing so, the calling configuration is where the complexity lives. Direct Routing versus Microsoft Calling Plans. Emergency calling compliance under Australian Telecommunications Act requirements. Number porting timelines. Call queues and auto attendant design. Voicemail integration.

Each of these is a decision point that affects daily operations. Organisations that cut corners during the calling migration typically discover the consequences within six months – missed calls, misdirected transfers, or emergency calling configurations that do not meet regulatory requirements.

What optimised looks like: Every Teams Calling deployment should include a network readiness assessment before go-live, not after. Teams Calling is a real-time voice workload. It requires adequate bandwidth, proper Quality of Service (QoS) tagging, and a network that has been tuned for the purpose. A fast NBN connection is not a substitute for a network that has been configured to prioritise voice traffic.

Area 2: Meeting Policies and AI Features

Microsoft has shipped more AI capability into Teams in the last 12 months than in the previous five years combined. Video-based meeting recaps. Real-time transcription with language detection. Automated action item extraction. Copilot in meetings, summarising discussion and surfacing context.

For knowledge-worker-intensive organisations – professional services, healthcare, education, financial services – the productivity case for Teams AI features is compelling. Microsoft’s own data shows users saving 30–40 minutes per person per week once automated recaps and action items are fully deployed.

The challenge is governance.

AI-generated transcripts capture everything said in a meeting. By default, in many Teams deployments, those transcripts are accessible to any user in the tenant. They are retained indefinitely. They surface in search results. For organisations handling commercially sensitive discussions, client conversations, or information that is subject to privacy obligations – this is a material risk.

Before enabling Teams AI features at scale, confirm these governance decisions are made and documented:

  • Who can initiate recording and transcription?
  • Who can access meeting recordings and transcripts after the fact?
  • How long are recordings and transcripts retained? (The default is often longer than most organisations intend.)
  • What happens to transcripts when a staff member leaves the organisation?
  • Are there meeting types – board sessions, HR discussions, client calls – that should be excluded from automatic transcription?

These are not hypothetical questions. They are the questions that compliance teams, boards, and legal counsel will ask when something goes wrong.

Coming in Part 2 – Publishing 28 April 2026

Calling and AI features are where you find the quickest returns. But the three areas that determine whether a Teams environment stays healthy over time are harder to fix once they go wrong.

Part 2 covers:

  • Area 3: Channels, Teams, and Information Architecture – why most deployments deteriorate from the inside out
  • Area 4: Integration with Business Applications – where the real productivity gains are hiding
  • Area 5: Security and Compliance Configuration – what Australian regulatory obligations actually require

We will also walk through what a structured Teams optimisation programme looks like in practice – and how BluBiz delivers it.

Want a structured Teams environment review? BluBiz delivers M365 assessments that identify exactly where your investment is underperforming – and what to do about it.

Contact our team: [email protected]

Want to know more?

Contact now