How to Configure Workspaces, Tab Sharing, and Collaborative Session Synchronisation in Microsoft Edge

Modern enterprise workflows frequently require cross-functional teams to collaborate across dozens of shared web applications, documentation portals, and dashboard environments. Historically, coordinating browsing sessions involved emailing lengthy URL lists or maintaining fragile spreadsheet repositories of bookmarks. Microsoft Edge Workspaces transforms this paradigm by introducing shared, real-time browsing environments backed by Microsoft Entra ID (formerly Azure Active Directory) and cloud synchronisation services.

A Workspace enables multiple team members to share an isolated browser window where tabs, tab groups, and collaborative favourites stay continuously synchronized in real time. Crucially, while navigation states and tab structures are replicated across all participants, private session credentials, authentication cookies, and browsing histories remain strictly confined to each participant’s local device.

Architectural Overview: Synchronisation Engine and Privacy Isolation

Understanding how Edge Workspaces maintains real-time synchronisation without exposing sensitive authentication tokens requires examining its boundary architecture:

Component / Layer	Operational Role	Replication Boundary
Workspace Shell	Encapsulates the browser window, theme colour, custom name, and tab arrangements.	Replicated to all authorized workspace members.
Tab Navigation Engine	Monitors active URLs, newly opened tabs, closed tabs, and tab grouping structures.	Synchronised in sub-second intervals via Microsoft 365 cloud fabric.
Presence & Avatars	Displays member profile pictures on tabs currently being viewed by collaborators.	Ephemeral real-time presence indicators.
Authentication Cookies & Storage	Contains session tokens, OAuth bearer cookies, and LocalStorage data.	Strictly Local: Never transmitted or shared with collaborators.
Form Data & Credentials	Manages autofill records, saved passwords, and payment instruments.	Strictly Local: Bound exclusively to the user’s personal profile vault.

When User A navigates a shared tab to a protected internal dashboard (e.g. https://portal.azure.com), User B sees the tab change immediately. However, when User B views that tab, their own local Edge profile initiates a separate authentication handshake against Entra ID, ensuring compliance with conditional access and zero-trust policies.

Prerequisites for Enterprise Deployment

To enable Edge Workspaces within a corporate environment, ensure the following tenancy requirements are satisfied:

• Microsoft 365 Tenancy: An active Entra ID tenant with OneDrive for Business and SharePoint Online provisioned (used for storing Workspace metadata).
• Microsoft Edge Build: Version 114.0 or later on Windows 10/11 or macOS.
• Sync Enabled: User profiles must have Microsoft Edge enterprise synchronisation turned on.

Creating and Managing a Microsoft Edge Workspace

End users can create dedicated project workspaces directly from the top-left corner of the browser frame.

Step 1: Initialise a New Workspace

1. Open Microsoft Edge and click the Workspaces icon in the top-left corner of the title bar (adjacent to the Tab Actions menu).
2. Click Create new.
3. Assign a descriptive name for your project (e.g. Q4 Infrastructure Migration).
4. Choose a distinct accent colour to provide immediate visual differentiation from your standard personal browsing windows.
5. Click Done. Edge opens a dedicated, colour-accented window representing the workspace.

Step 2: Populate Tabs and Shared Favourites

1. Navigate to the web applications, Jira boards, or SharePoint sites relevant to the project.
2. Organise related links using Tab Groups (right-click a tab > Add tab to new group). Tab group colours and labels replicate across all workspace members.
3. Pin frequently accessed documentation hubs to keep them permanently docked on the left.

Step 3: Invite Team Members

1. Click the Invite button located in the top-right corner of the workspace title bar.
2. Click Copy link to generate a unique sharing invitation URL.
3. Transmit the link to your colleagues via Microsoft Teams, Outlook, or Slack.
4. When the recipient clicks the link, Edge validates their Entra ID tenant affiliation and immediately renders the workspace with all active tabs and layout structures intact.

Enterprise Governance via Microsoft Intune and Group Policy

IT administrators can enforce policy controls to restrict workspace creation, limit link sharing strictly to internal domain members, or mandate workspace enablement across endpoint fleets.

Configuring Group Policy Objects (GPO)

Download and import the administrative templates (msedge.admx) and configure the following policy paths under Administrative Templates > Microsoft Edge:

# Policy 1: Enable Edge Workspaces Feature
Policy Name: Enable Workspaces
Registry Path: HKLM\SOFTWARE\Policies\Microsoft\Edge
Value Name: EdgeWorkspacesEnabled
Data Type: REG_DWORD
Value: 1 (Enabled), 0 (Disabled)

# Policy 2: Restrict Sharing to Internal Entra ID Tenant
Policy Name: Configure sharing restrictions for Edge Workspaces
Value Name: ConfigureShareEdgeWorkspaces
Data Type: REG_DWORD
Value: 0 (Allow sharing with anyone in tenant)
Value: 1 (Block all external and guest invitation generation)

Configuring Microsoft Intune Settings Catalog

1. Log in to the Microsoft Intune admin center (endpoint.microsoft.com).
2. Navigate to Devices > Windows > Configuration profiles > Create profile.
3. Select Windows 10 and later and Settings catalog.
4. Under the Microsoft Edge category, add Edge Workspaces Enabled and set to Enabled.
5. Deploy the profile to your target user or device groups.

Troubleshooting Workspace Synchronisation and Access Faults

When collaborators encounter synchronisation latency, missing tabs, or invitation failures, consult this troubleshooting matrix:

Issue	Probable Root Cause	Remediation Procedure
“You don’t have access to this workspace” error upon opening invite link.	User is signed into Edge with a personal Microsoft Account (MSA) or an Entra ID account from a foreign tenant.	Switch the primary Edge browser profile to the enterprise account matching the workspace creator’s tenant domain.
Tabs opened by Collaborator A do not appear on Collaborator B’s screen.	Edge Sync is paused, network firewall is blocking WebSocket endpoints, or the local client is in an offline state.	Navigate to edge://sync-internals in the address bar. Check the Workspaces data type status. Ensure traffic to *.edge.microsoft.com and *.office.com is permitted through corporate proxies.
Workspaces button is completely absent from Edge title bar.	Policy EdgeWorkspacesEnabled is set to 0, or user profile is unmanaged without Entra ID sign-in.	Inspect active policies by navigating to edge://policy. Verify that enterprise synchronisation is permitted and active.
Collaborator is asked to log in to every shared application.	Expected security behaviour; session cookies and tokens are not replicated across the network.	Collaborators must authenticate independently using their own corporate SSO credentials. Ensure Single Sign-On (SSO) via Seamless SSO or PRT is operational.

By integrating Microsoft Edge Workspaces into standard operational routines, enterprise organisations eliminate browser fragmentation, streamline project onboarding, and maintain airtight security compliance across collaborative cloud sessions.