Multiple Microsoft Teams accounts on one PC
Two organisations, one workstation, and you have to sign out of one to answer in the other. It is daily life for consultants, contractors and anyone wearing two hats, and Microsoft has never really closed the gap.
What Microsoft officially recommends
Microsoft’s documentation does not hide the limitation: to use two Teams accounts at once in a browser, the stated procedure is to open a different browser, or a private browsing window. This is not a power-user trick from a forum: it is the support answer.
What the desktop client fixes, and what it leaves
The Teams client for Windows can switch between accounts, and can show several organisations attached to one account. Two caveats, and they are the ones that hurt day to day.
- Account switching is sequential: you look at one organisation at a time, and notifications from the others arrive with the lag of the switch.
- A work account and a personal Microsoft account coexist poorly, and mixed cases (guest at one client, member at another) are precisely the ones that break.
- The desktop client only fixes Teams. If the same machine also has to hold two WhatsApp accounts, the problem returns in full, service by service.
The options, compared
| Method | Accounts visible at once | The limit |
|---|---|---|
| Teams desktop client | One at a time | Sequential switching; work and personal accounts conflict |
| Private browsing window | Two | Session lost on every close, sign in again daily |
| A second browser | Two | Two applications open all day, notifications split between them |
| Browser profiles | As many as profiles | One window per profile, whole context swapped each time |
| Nexus | As many as you like | Windows application only |
Two Teams organisations with Nexus
Nexus opens the official Teams web interface in an isolated session, as many times as you need. Each instance has its own storage: the sessions cannot see each other, so none signs the other out.
- Install Nexus and open it.
- Add Teams from the catalogue, then sign in with the first organisation’s account.
- Add Teams a second time: the new instance starts blank, so sign in with the second account.
- Rename each entry after its organisation so the sidebar tells them apart at a glance.
Both organisations stay connected in parallel. Unread badges are separate, muting is independent, and you switch with Ctrl+1 to Ctrl+9 without waiting for a reload.
One point that matters more than it looks
Teams is among the services that regularly drop support for old browser engines. An aggregator whose Chromium falls behind starts showing a warning, then gets blocked outright. That is a selection criterion in its own right, and it can be checked.
Common questions
- Does this work with multi-factor authentication?
- Yes. Sign-in happens on the official Microsoft pages inside the service’s isolated session: MFA, Authenticator and SSO behave exactly as in an ordinary browser.
- Do calls and meetings work?
- Teams on the web supports calls and meetings, and Nexus exposes the microphone and camera to the service once you allow it. Some advanced features remain exclusive to Microsoft’s native client, as they do in any browser.
- Can my IT department block this?
- Nexus is a web client: your organisation’s conditional access policies, device restrictions and compliance rules apply exactly as they would in a browser. In a managed environment, ask before installing.
- Can I mix Teams, WhatsApp and the rest?
- Yes, that is the whole idea. Every service you add, including a custom URL, gets its own isolated session in the same window.