Microsoft Teams

What Teams brings together

Microsoft Teams is Microsoft’s communication and collaboration platform for persistent conversations, meetings, calls, and access to documents and applications. Its relationship with Microsoft 365 is central: one interface can display resources belonging to different services. It is more than a video-calling application, and it is not a single drive that stores every type of content in the same way.

Businesses, educational institutions and personal groups use Teams, but its editions do not provide identical capabilities. Understanding a deployment requires three layers: the account and its licences, the collaboration space, and the services storing each content type. This explains how someone can join a meeting yet be unable to open a document shared during it.

Reference documentation: Microsoft — Teams preview, 2016 · Microsoft — General availability, 2017 · Microsoft Learn — Current clients.

Origins, development and client generations

Teams entered preview on 2 November 2016 and became generally available on 14 March 2017. Microsoft’s earlier work in business communication included its 2007 announcement that it would acquire Parlano, maker of the persistent group-chat application MindAlign. That is background to its communications strategy, not the launch date of Teams.

• 2018: a free edition broadened access beyond commercial Office 365 subscriptions.
• 2019–2020: frontline-worker development included Shifts scheduling and the announcement of Walkie Talkie push-to-talk communication.
• 2021: Skype for Business Online retired on 31 July. This transition is distinct from server editions and consumer Skype.
• 2023: the new client changed interface and execution components: React replaced Angular and, on Windows, WebView2 replaced Electron. General availability for the new Windows and Mac clients arrived in October.
• 2025: Skype retired in May, with Teams Free offering a migration route. Microsoft announced redesigned application icons, including Teams, in October.

This history matters when using tutorials: instructions for the classic client, the former free edition or Skype may describe different interfaces, licences and capabilities. A guide’s date is part of its practical value.

Reference documentation: Microsoft — Teams preview, 2016 · Microsoft — General availability, 2017 · Microsoft — Parlano acquisition announcement · Microsoft — Free Teams release, 2018 · Microsoft — Frontline workers and Shifts · Microsoft — Walkie Talkie announcement · Microsoft Lifecycle — Skype for Business Online retirement · Microsoft Support — Skype retirement · Microsoft — New Teams architecture · Microsoft — New Teams general availability · Microsoft — Updated app icons.

Conversations, channels and connected files

Microsoft Teams brings communication and collaboration into the Microsoft 365 environment. For preventive work, distinguish the team, its channels and associated files. A standard channel is available to team members; private and shared channels serve different collaboration scopes. Choose the channel type according to who needs to participate.

Files displayed in channels are stored in SharePoint. Microsoft documents that standard channels share the team’s site, while private and shared channels have their own associated sites. This explains why a conversation and document can have different access routes. Posting a link in Teams does not remove the need to check file permissions. Identify the reference location rather than relying on where a link was last mentioned.

Reference documentation: Microsoft Learn — Teams and SharePoint integration · Microsoft Learn — Standard channels in Microsoft Teams.

Conversations, files and retention

A team brings people and resources together; channels organise conversations by subject. Individual and group chats serve a different relationship: they are not equivalent to channels with a shared document structure. A message may contain a file or link without making that conversation the resource’s sole owner.

Messages use an Azure-powered chat service, with copies in Exchange supporting retention operations. Channel documents rely on SharePoint; files shared in chats use OneDrive. Each standard, private or shared channel does not receive a separate Microsoft 365 group: the team has a group, while associated sites depend on the channel type.

A useful information map records what is published, where it is stored, who maintains it and how long it should remain available. Archiving a space, deleting a visible message and removing retained copies are different operations. Removing a link does not establish that its source file has disappeared. This distinction prevents promises of deletion or recovery based solely on the client interface.

Reference documentation: Microsoft Learn — Teams and SharePoint integration · Microsoft Learn — Security and information protection · Microsoft Purview — Teams retention · Microsoft Support — File storage.

External access, guests and shared channels

External access supports communication with other organisations without making every contact a team member. Guest access creates a guest identity in Microsoft Entra for collaboration on authorised resources. Shared channels can include another organisation’s users through administrator-configured B2B direct connect; guest accounts cannot simply be added as ordinary shared-channel members.

These are different models, not three names for the same permission. When coordinating with suppliers, first establish whether they need a meeting, a particular document or continuing collaboration. Configure the corresponding access and test it with an identity matching that participant type.

Departure also needs an explicit process. Removing someone from a conversation does not necessarily revoke every file permission. A practical review checks membership, sharing links and derived resources, especially where documents have been copied elsewhere.

Reference documentation: Microsoft Learn — Guest access · Microsoft Support — Guests and shared channels · Microsoft Learn — Standard channels in Microsoft Teams.

Meetings, events and hybrid rooms

Meetings support interaction through audio, video, screen sharing and chat. Events structure organiser, presenter and attendee roles; the current model adjusts registration and interaction to the scenario. Webinar and town-hall policies remain relevant even as event creation becomes unified. Format selection should consider who needs to speak, ask questions or share material, rather than just an advertised maximum audience.

Live Events is a retiring legacy capability. Microsoft set retirement for 30 June 2026, while allowing previously scheduled events to run through 28 February 2027. A new guide should describe the current event alternative rather than present Live Events as the ordinary choice for a new project.

Teams Rooms adds room equipment; Front Row arranges remote participants, content and chat for hybrid sessions. Breakout rooms support smaller-group activities. Screen layout alone cannot ensure participation: check audibility from each seat, document readability, speaking turns and an alternative channel for anyone unable to contribute by voice.

Reference documentation: Microsoft Learn — Meetings and events · Microsoft — Live events retirement · Microsoft Learn — Front Row · Microsoft Support — Breakout rooms.

Recordings, transcripts and AI summaries

Recordings and transcripts are stored in OneDrive or SharePoint according to the session and context. Identify ownership, audience and retention before recording. A recording may remain accessible after group membership changes, or expire before the work requiring it is complete.

Copilot can summarise discussion and suggest actions. Settings distinguish use during a meeting from later consultation; subsequent questions about spoken content require the corresponding transcript. Access depends on licensing, policies and configuration. Intelligent recap and Copilot are not interchangeable names for every capability.

A useful control checks names, figures and agreements against their source. If someone says, “We could close the action when the test arrives,” minutes should not turn this into “Action closed.” Retain the outstanding condition and identify who will verify the test. AI can accelerate a draft; responsibility for an agreement remains within the team’s approval process.

Reference documentation: Microsoft Learn — Recording storage · Microsoft Support — Copilot in meetings.

Telephony, connectivity and technical security

A call between Teams users does not itself provide public telephony. Teams Phone can connect to the telephone network through Calling Plans, Operator Connect, Teams Phone Mobile or Direct Routing. The choice depends on licences, operator, country and existing architecture; a number, a calling plan and a policy are distinct components.

Teams separates signalling from real-time media. ICE helps select communication paths, while SRTP protects audio and video streams. One successful call does not establish equivalent quality across routes and devices. Test meetings on the actual network, microphone, speaker and display, rather than only between two laptops in a quiet office.

Transport encryption does not mean every meeting automatically has end-to-end encryption with identical functionality. Authentication, lobby settings, roles and presentation rights also matter. An OSH exercise needs a fallback if connectivity fails; internet push-to-talk should not be presumed equivalent to an emergency communications system.

Reference documentation: Microsoft Learn — PSTN connectivity · Microsoft Learn — Call flows · Microsoft Learn — Teams security guide.

Applications, education, platforms and licences

Tabs embed web experiences; bots and agents provide conversational interaction; message extensions insert content or initiate actions. Adding an application requires checking its provider, permissions and data destination. Displaying a page inside Teams does not automatically move its information or control into the same service.

Legacy Office 365 connectors stopped functioning after the retirement rollout of 18–22 May 2026. Microsoft directs these scenarios towards Power Automate-based Workflows. When migrating a notification, test delivery, failure handling and continuity when ownership changes.

Teams for Education adds class teams with assignments, submissions, rubrics and grades. Viewing a file, submitting it and receiving an assessment are different states. This distinction is useful in training design, but organisations should not assume a business licence includes every educational feature.

Windows and macOS clients, iOS and Android applications, and web access through compatible browsers are available. The Linux client is no longer supported; check the supported web route. Teams Free, business offerings, Teams Premium, Phone and Rooms serve different needs. Since April 2026, some previously Premium-only capabilities have been included in Teams Enterprise. Check the current feature matrix and the licence actually assigned, not merely the subscription’s marketing name.

Reference documentation: Microsoft Learn — Current clients · Microsoft Learn — Meetings and events · Microsoft Learn — Apps in Teams · Microsoft developer blog — Connector retirement · Microsoft Support — Education assignments.

Adoption and competition debate

The expansion of remote work accelerated Teams adoption. Microsoft reported 44 million daily active users in March 2020 and more than 320 million monthly active users in October 2023. These are historical provider figures using different units; they should not form a series that confuses daily and monthly activity, or be presented as current users independently verified for this profile.

Office integration also prompted a competition debate covered by independent reporting. On 12 September 2025, the European Commission accepted Microsoft commitments covering cheaper suites without Teams, switching opportunities, interoperability and portability. They last seven years, with ten years for interoperability and portability.

The practical selection lesson is to compare the cost and operation of the complete arrangement needed. A suite may simplify identity and documents; a combination of services may suit particular teams better. Evaluate export, format dependence, external collaboration and the ability to change providers alongside initial convenience.

Reference documentation: Microsoft — March 2020 usage · Microsoft investor relations — FY2024 Q1 · European Commission — Teams commitment decision · Associated Press — EU accepts Teams commitments.

Coordinating people around a common reference

• Preventive meeting preparation: collect agendas, documents and questions before a session, clearly identifying the reference material.
• Coordination across sites: maintain topic-based conversations and links to authorised records instead of forwarding copies that evolve separately.
• Questions about materials: collect questions and route them to the competent owner without turning an informal reply into an automatic procedure change.

These are Sabentis proposals for organising communication. A published message does not prove everyone understood it or that an action was performed. Agreements requiring follow-up need an identifiable register, owner and evidence. Distinguish information shared for discussion from instructions approved for use.

Worked example: a meeting with identifiable documents

Hypothetical example. An internal committee is preparing a monthly meeting and wants participants to use the same action-report version.

1. Identify the required group and choose an appropriate channel. Review members, guests and access scope before adding internal documents.
2. Store the reference report in the authorised location and share its link, stating reporting date and version. Avoid attaching another copy whenever it is discussed.
3. Publish an agenda with specific questions and links to preparation information. Separate confirmed data from unresolved points.
4. During the meeting, record relevant decisions and disagreements. Identify who will verify each action and by when, without treating chat discussion as implicit approval.
5. Afterwards, reconcile the summary with agreements and retain it at the stable reference. Verify that recipients can open documents and unintended users do not gain accidental access.

Acceptance means participants and owners can find the same information and reconstruct the decisions. A meeting taking place and an action being completed remain different facts. Where a decision is amended later, update its reference clearly rather than leaving contradictory messages unexplained.

Additional check: the committee reviews 12 actions. Nine have validated evidence and three remain outstanding: documented closure is 9/12, or 75%. An automatic summary proposes ten closures because it interprets a promised delivery as completed work. The owner corrects that item and links the evidence for the nine closed actions. An external participant is also tested for access to the authorised minutes, while internal appendices remain inaccessible. Acceptance means reconstructible agreements and correct permissions, not message counts, attendance or recorded minutes.

Reference documentation: Microsoft Learn — Teams and SharePoint integration · Microsoft Learn — Standard channels in Microsoft Teams.

Distributed permissions and messages without context

Team membership, channel type and file permissions influence access. Check the real case, especially with external people or reused links. Do not assume a document is restricted merely because it was discussed in a limited conversation.

Fast communication can fragment decisions across messages, files and meetings. Establish where the approved conclusion is retained and who maintains it. If recordings, transcripts or summaries are used, check their configuration and accuracy before treating them as minutes; availability depends on the environment. For urgent safety communications, use the organisation’s defined procedure and channels rather than an informal expectation of immediate reading. Keep a clear route for people who cannot access the digital workspace.

Reference documentation: Microsoft Learn — Teams and SharePoint integration · Microsoft Learn — Standard channels in Microsoft Teams.

When to choose Teams and how to complement it

Teams can fit organisations already working in Microsoft 365 that need to coordinate conversations, files and working groups. Before creating channels, agree their purpose, owner and archiving criteria so the structure does not become a collection of abandoned spaces.

Microsoft Forms can complement structured response collection. Power Automate can be assessed for authorised repetitive tasks. Keep conversation, approval and execution distinct so a message is not mistaken for permission to act.

Frequently asked questions about Teams in OSH

Are channel files stored only in Teams?

Channel files rely on SharePoint. Understanding that relationship helps review permissions, versions and reference locations.

Does a private channel meet every confidentiality need?

It restricts participation according to configuration, but documents, links and organisational policies still require review.

Does a read message prove training?

Not by itself. Evidence depends on the objective and training process, distinguishing access, participation and learning.

Reference documentation: Microsoft Learn — Teams and SharePoint integration · Microsoft Learn — Standard channels in Microsoft Teams.