Cookie Consent by Free Privacy Policy Generator
microsoft365copilot cowork agents
•
• 2 min read

Enabling Cowork: The Frontier Path

The four-step Frontier enrollment path for Cowork — tenant opt-in, admin account enrollment, user availability, and the first-run experience.
Holger Imbery
Written by Holger Imbery
Enabling Cowork: The Frontier Path
Photo generated by AI

Enabling Cowork: The Frontier Path

Post 2 of 14

Introduction

Cowork is not a feature you flip on like Loop or Designer. It is a Frontier preview feature, which means access is gated by a tenant-level opt-in plus an admin enrolment of their own account. If Cowork is missing from your Microsoft 365 Copilot view, the most common cause is step zero.

The Four-Step Path to Access

Prerequisites.

  • An active Microsoft 365 Copilot license on the user account.
  • A tenant enrolled in the Frontier preview program.
  • A modern browser (Edge or Chrome) or the Microsoft 365 Copilot desktop app for Windows or Mac.

Step 1 — Enroll the tenant in Frontier. In the Microsoft 365 Admin Center, go to Copilot → Settings → Frontier and enrol your tenant. Frontier previews are subject to your existing customer agreement preview terms.

Step 2 — Enroll the admin account. This trips up most teams. If Cowork does not appear in Agent management, it is because the admin’s own account is not enrolled in Frontier. Enroll the account, sign out, and back in.

Step 3 — Make Cowork available to users. In Agent management, manage which users see Cowork. Pilot rings first, broad rollout later.

Step 4 — Open Cowork. Users navigate to m365.cloud.microsoft, the desktop app, or the agent surface in Outlook or Teams, and select Cowork (or find it under All agents).

What users see on first run. A chat input, a side panel for files, suggested prompts (Catch me up, Organize my inbox, Prep for a meeting), the Tasks view in the navigation, and an output panel where generated files land.

What admins should pre-decide.

  • Which security groups get Cowork.
  • Whether the Anthropic subprocessor toggle is enabled (default in many regions; opt-in for EU/UK/EFTA — Post 3 covers this).
  • Sensitivity labels and DLP policies that should apply before broad rollout.

Disabling Cowork for specific users. Add them to a security group configured to exclude them from the Copilot experience, or manage availability through the Copilot settings in the admin center.

Takeaway

The single most common rollout issue is the admin enrolment step. Enroll both the tenant’s and the admin’s accounts in Frontier before troubleshooting anything else.

Sources

Holger Imbery
Written by

Holger Imbery

Start the conversation

Related

See all microsoft365copilot
microsoft365copilot cowork agents
•

Microsoft Copilot Cowork: A Practical Introduction

A hands-on guide to Microsoft Copilot Cowork: what it is, how it works, and how to use it effectively in your Microsoft 365 environment.

Holger Imbery
Written by Holger Imbery
copilotstudio agents applicationinsights telemetry monitoring
•

Connecting Azure Application Insights to Microsoft Copilot Studio: Unlocking Deep Analytics for Agentic Systems

Transform your Copilot Studio agents from a black box into a fully observable, debuggable system. Learn how to connect Azure Application Insights for enterprise-grade monitoring, real-time diagnostics, and data-driven optimization that reduces support costs, improves user satisfaction, and demonstrates measurable ROI.

Holger Imbery
Written by Holger Imbery
copilotstudio agents agentevaluation testing qualityassurance
•

Testing Copilot Agents: When to Use Agent Evaluation vs. the Copilot Studio Kit

On March 31, 2026, Microsoft launched Agent Evaluation in general availability, fundamentally changing how teams validate Copilot agents. This guide explains how Agent Evaluation and the Copilot Studio Kit serve different—but complementary—roles in your quality assurance strategy, and when to use each one.

Holger Imbery
Written by Holger Imbery