Microsoft Teams Online: Browser Version for Business

How do you open Microsoft Teams online?

Go to teams.microsoft.com in your browser and sign in with your Microsoft 365 work email, completing any multi-factor authentication (MFA) prompt. Teams loads inside the tab with your channels, chats, calendar and meetings — no download, no admin rights, no install.

The browser version runs on any device with a supported browser: Windows PCs, Macs, Chromebooks, Linux machines and tablets. That makes it genuinely useful when you are on a borrowed device, or when your IT policy blocks software installs on managed endpoints. If you run Microsoft 365 across your business, the web app is the quickest way to get a new starter into Teams on day one — and a properly configured tenant, which our Microsoft 365 security team handles, makes that sign-in safe by default.

Microsoft documents the supported browsers and feature limits in its own Teams web client guidance, which is worth a look before you standardise on a browser.

Which browser works best for Teams online?

Microsoft Edge and Google Chrome give the most complete Teams web experience, including the best video performance and full background-effects support. Firefox works for everyday chat and meetings but limits some screen-sharing and meeting controls. Safari is functional, but Mac users are better served by the desktop app.

Internet Explorer is retired and unsupported. If anyone in your organisation still uses it, that is a security problem in its own right — the NCSC is clear that unsupported software is one of the easiest routes in for an attacker.

What features are available on Teams web?

The browser version covers the essentials most staff use every day: chat, channels, meetings, calendar and file editing. The gaps are around Teams Phone calling, offline access and background notifications — areas where the desktop app is simply more reliable.

Available in the browser:

• Chat — one-to-one and group messaging with full history and search
• Channels — team channels, posts and file tabs
• Meetings — join and host with audio, video and screen sharing
• Calendar — schedule and view meetings, linked with Outlook
• Files — open and edit OneDrive and SharePoint files via the Office web apps
• Notifications — browser alerts while Teams is open in a tab

For most informational, scheduling and collaboration work, that feature set is enough. The differences start to bite when Teams is someone's primary phone line or always-on presence tool.

Where does the browser version fall short of the desktop app?

The web client is strong, but five gaps matter for business use: Teams Phone calling, background effects, notifications when the tab is closed, granular screen sharing, and offline access. None of these block casual use — but together they explain why daily users belong on the desktop app.

• Teams Phone (PSTN) calling — making and receiving external calls can be limited in the browser; internal Teams-to-Teams calls work fine. If you run Microsoft Teams calling as your phone system, the desktop app is the reliable choice.
• Background effects — blur and custom backgrounds work in Edge and Chrome but perform worse than the desktop app and may be missing elsewhere.
• Background notifications — browser alerts stop the moment you close the tab. The desktop app runs in the background and keeps staff reachable.
• Screen sharing — browsers often share the whole screen rather than a single window, which limits what you can keep private.
• Offline access — the web client needs a live connection and caches nothing; the desktop app shows recent messages and files offline.

If telephony is the deciding factor, our Microsoft Teams Direct Routing service connects Teams to the public phone network with a setup that the browser alone can't match.

When should you use Teams online instead of the app?

Use the browser version for occasional, device-flexible access: borrowed machines, Chromebooks, Linux, locked-down endpoints, or a second account in a separate browser. Use the managed desktop app when Teams is someone's primary daily tool, phone line, or always-on presence channel — which describes most office and hybrid staff.

Use the browser version when:

• You are on a device where you can't or don't want to install software
• You are using a Chromebook or Linux machine
• You need Teams temporarily on a borrowed device
• You want a second Teams account signed in alongside your main one

Use the desktop app when:

• You use Teams every day as your main communication tool
• You need reliable Teams Phone calling
• You want background notifications and always-on presence
• You use background effects in video meetings regularly

For most UK office and hybrid staff, the desktop app delivers a materially better day-to-day experience, and the web version is the practical fallback. The deciding factor is rarely features — it's deployment and security. A desktop rollout should be configured, patched and monitored, not left to each user. That's what AMVIA's managed Microsoft 365 service is built to do.

Is Microsoft Teams in the browser secure?

Teams web uses the same Microsoft 365 security stack as the desktop app — encrypted connections, MFA and Conditional Access all apply. The real risk is the device and the user: shared computers, saved credentials and unmanaged browsers. Hardening Teams sign-in is a configuration job, not a default.

Microsoft sets out the underlying controls in its Microsoft 365 security documentation, and the same identity protections that guard the desktop app guard the browser. Where businesses get caught out is the human layer: a staff member signing in on a public machine and leaving a session open, or a tenant with MFA switched off. Locking those down — and monitoring for risky sign-ins — is exactly the kind of work covered by dedicated Microsoft Teams security controls.

One provider, security-first, with Microsoft-certified engineers means the same standard applies whether your team is on the app or the web.