Microsoft has begun letting Frontier early-access users run Project Opal, a Copilot capability that executes task-based work on a secure Windows 365 Cloud PC. The company's support documentation describes Opal as an agent that works asynchronously in the background across an organization's browser-based applications, sites, and data, while the user watches, steers, or takes over at any point.
Access is narrow. Opal is available only to users in the Frontier early access program with a Microsoft Copilot subscription, and administrators must complete setup before anyone can start a job. Frontier itself is opt-in: organizations enable it in the Microsoft 365 admin center, and IT admins decide which users or groups see the agent.
Confirmed
The mechanics are documented in some detail. A user opens the Microsoft 365 Copilot app, selects Opal from the app launcher, starts a job with +New, describes the work and expected outputs, and clicks Start. Opal generates a plan, initializes a Windows 365 Cloud PC, and prompts the user to sign in so it can act on their behalf. Browser pop-ups may need to be allowed for authentication.
From there the agent uses an advanced reasoning model and computer use to drive Microsoft Edge, clicking, typing, and navigating like a human user. Microsoft says the reasoning model converts natural-language requests into dynamic plans and adjusts the sequence of tool calls as the job progresses. A separate supervisor provides independent checks on that reasoning model, monitoring actions and prompting for human input when needed.
Microsoft lists the work Opal is meant to absorb: managing security group membership requests, collecting and validating audit evidence for compliance reviews, triaging IT incidents by updating ticket status and closing duplicates from meeting transcripts, and compiling Excel data into a financial close deck. In its early preview, Microsoft says its own engineers saved up to 20 hours per week on audit tasks by delegating evidence collection to Opal.
Control surfaces are explicit. Users can maximize the computer view to watch actions live, pause and resume, or select Take Control to drop into a Remote Desktop session on the Cloud PC. Returning control lets the user describe what they did so Opal can resume in the right place. Jobs can be duplicated with the original prompt or deleted, and up to three jobs can run at once — starting a fourth closes out the oldest.
Skills let users package repeatable instructions. From the Settings menu, a user can add a skill by importing a.md file, writing one from scratch, or building it conversationally with Opal, then reuse it in later jobs.
Unknown
Two things remain open. The first is scope: Opal is a Frontier experiment, and Microsoft's own documentation says features may change as it improves them, so nothing here should be read as a general-availability commitment. The second is the security posture, which has shifted. According to Microsoft's admin documentation, Opal now allows access to all websites by default, with administrators able to block specific URLs; previously it blocked everything unless URLs were individually allow-listed. Organizations that prefer the older behavior can re-enable block-by-default in the Opal Admin Center.
File interaction is also new and conditional. Microsoft says that following internal security reviews, Opal can download and upload files on the Windows 365 Cloud PC, but only when administrators manually update the Opal App Device Policy in Intune — enabling the File System API for reading and writing, and setting download restrictions to Block. Tenants that onboarded before April must make those changes by hand.
Licensing adds another gate. Administrators need an Intune license and a Microsoft Entra ID P1 license; individual users need Microsoft Copilot licenses. Setup runs through the Microsoft 365 admin center and then the Opal Admin Portal, which creates a device group, device policy, and a pool of Cloud PCs. Microsoft warns admins not to delete or adjust those resources, since changes may break the app entirely.
Microsoft has not published independent benchmarks for Opal, and the 20-hour weekly saving is a company-reported figure from internal use rather than a measured customer outcome.
Our take
The interesting part of Opal is not the agent loop; it is the default. Flipping website access from block-by-default to allow-by-default lowers the setup burden that killed many earlier agent pilots, but it also moves the security decision from the admin who never configured anything to the admin who now has to remember to configure a blocklist. Microsoft's own note that pre-April tenants must hand-edit Intune policies suggests the guardrails are still catching up to the convenience.
