You can open a second Teams window in Linux by creating a dedicated WebApp using your browser’s built-in application mode. This method isolates the second session from your primary account, allowing you to log in with a different identity without relying on Windows-specific native applications or complex workarounds.
Understanding the WebApp Approach
Most modern web browsers, including Chrome, Edge, and Firefox, support creating "Web Apps" or "Application Shortcuts." These are essentially pinned windows that run a specific website in its own isolated environment, separate from your main browsing profile. For Microsoft Teams, this isolation is crucial because it allows for distinct session cookies and login states. Unlike running multiple tabs within the same browser window, which often share authentication tokens, a WebApp acts as a standalone client. This mimics the behavior of the native Windows desktop application, providing a dedicated icon in your dock or taskbar and a separate process space.
Creating the Shortcut in Chromium-Based Browsers
If you are using Google Chrome, Microsoft Edge, or Brave, the process is straightforward. Navigate to
teams.microsoft.com and log out if you are currently logged in, or simply proceed to create the shortcut while logged into the account you wish to use in the second window. Click the three-dot menu in the top-right corner of the browser. Select
More Tools and then
Create Shortcut.... A dialog box will appear asking for the name of the app; ensure you check the box that says
"Open as window". This option is critical as it enables the standalone application mode rather than just adding a tab to your current session. Click
Create, and the browser will generate an executable shortcut that launches Teams in its own dedicated window.
Configuring Firefox WebApps
For users preferring Mozilla Firefox, the process involves slightly different steps due to Firefox's architecture. Go to the Teams website and ensure you are logged into the desired account. Click the hamburger menu (three horizontal lines) in the top right. Select
More and then
Install Page as Application.... You will be prompted to name the application and decide whether to allow it to replace the default handler for that site. Confirm the installation. Firefox will place a shortcut on your desktop or in your applications menu, depending on your distribution settings. Launching this shortcut opens Teams in a separate window with its own isolated cookie jar.
Managing Multiple Instances
Once you have created the WebApp for your secondary account, you can launch both your primary Teams instance and the new WebApp simultaneously. Your primary Teams client might be the native Linux application or another WebApp linked to your first account. Because each WebApp runs in a separate browser profile context, they do not interfere with each other. You can switch between them using your system’s window manager or taskbar. This setup effectively replicates the multi-account functionality found in the Windows desktop client, where each instance is treated as a separate process.
Troubleshooting Login Issues
Sometimes, the WebApp may attempt to sync with your main browser’s cache, causing login loops. If you encounter issues, try clearing the browser data specifically for that WebApp. In Chrome, you can access this by navigating to
chrome://settings/content/all and searching for the Teams domain. Delete the data associated with it. Alternatively, ensure that you are not using the same private/incognito window for both instances, as some browsers restrict multiple incognito sessions of the same origin. Using standard windows for each WebApp ensures maximum compatibility.
Performance and Resource Considerations
Running multiple WebApps consumes more memory than a single tab but less than running multiple full browser instances. Each WebApp has its own renderer process, which means CPU usage is distributed across cores efficiently. However, if you notice performance degradation, consider reducing the number of background tabs in your main browser. The WebApp itself does not load extensions unless explicitly configured to do so, which helps maintain performance. This approach is generally lighter on system resources compared to running virtual machines or containers solely for Teams.
Alternative: Native Client Workarounds
While the WebApp method is robust, some users prefer the native Microsoft Teams Linux client. Unfortunately, the official native client does not natively support multiple simultaneous accounts in separate windows. Users attempting to bypass this limitation often resort to complex scripting or containerization, which can be unstable. The WebApp strategy remains the most reliable and user-friendly alternative for Linux users who need dual identities. It leverages existing browser technologies without requiring third-party tools or elevated privileges.
Run Programs with Elevated Privileges: A Comprehensive Guide provides insights into managing system permissions, which can be relevant if you need to adjust security settings for your browser profiles. Additionally, understanding how to manage file paths and quoting in scripts, as discussed in
Troubleshooting Bash Script with Suspected Issues of Spaces, Dashes, Filenames and Quoting, can help if you automate the launching of these WebApps via custom shell scripts.
Frequently Asked Questions
Can I use the same browser for both Teams WebApps?
Yes, you can use the same browser to host multiple WebApps. Each WebApp creates a separate window with its own isolated session state, allowing you to log into different accounts simultaneously without conflict.
Do WebApps receive automatic updates like the native client?
WebApps rely on the underlying browser version for updates. As long as your browser is updated, the Teams interface will update automatically since it loads directly from the web server, ensuring you always have the latest features.
Is there a way to pin WebApps to my desktop permanently?
Most Linux distributions allow you to pin shortcuts to the desktop or dock. After creating the WebApp, drag the generated icon to your desktop or right-click and select "Add to Favorites" depending on your desktop environment.
Will notifications work correctly in a Teams WebApp?
Notifications should work normally, provided your browser allows permission for the Teams site. Ensure that notification settings in your browser are enabled for the specific WebApp URL to avoid missing alerts.
How do I remove a Teams WebApp if I no longer need it?
To remove a WebApp, simply delete the shortcut from your desktop or applications menu. You may also want to clear the browser data for that specific site to fully remove cached information and login states.