Copilot Cowork Browser Use

Copilot Cowork browsing is a powerful capability, but there is one admin setting you need to turn on first.

If you want Copilot Cowork to complete browser-based work using Microsoft Edge, browser access must be enabled in the Microsoft 365 admin center.

Where to enable Copilot Cowork browsing

Go to the Microsoft 365 admin center and follow these steps:

1. Open Copilot
2. Select Settings
3. Select View all
4. Find Cowork
5. Turn on Allow browser access
6. Select Save

This setting is off by default.

Once enabled, Copilot Cowork can use Microsoft Edge to interact with web apps and services on behalf of users. That means it can navigate pages, enter data, and complete browser-based tasks when APIs are not available.

What users see before using browsing

After browsing is available, users still see a confirmation screen before starting. The prompt explains that Cowork browsing is in preview, can perform tasks on the user’s behalf, and may make mistakes or misinterpret instructions.

This is the right pattern for enterprise use. Admins control whether browser access is available. Users acknowledge the risks before using it. Cowork asks for approval before sensitive actions.

Why this matters

A lot of business work still happens inside web applications that do not have clean APIs, connectors, or automation-friendly interfaces. Browser access gives Copilot Cowork another way to help users complete real work across those systems.

Examples I would test first

The best Copilot Cowork browsing scenarios are the annoying business tasks trapped inside web apps.

Portals. Admin screens. Expense systems. Vendor sites. Internal tools. Places where the work still requires a person to open a browser, navigate pages, enter data, review details, and decide what happens next.

Here are the types of scenarios I would start testing.

1. Expense reports in a web expense system

This is one of the cleanest examples because the work is structured, repetitive, and still needs human review.

Cowork could gather receipt context from Outlook or OneDrive, open the expense system in Edge, fill in the draft expense report, ask for missing details, and stop before submission.

Prompt idea:

File my expense report for last week's trip.
Use receipts from Outlook and OneDrive as the source of truth.
Open the expense portal in Edge and draft the report.
Ask me for anything missing.
Do not submit until I approve the final details.

2. Vendor portal status checks

A lot of finance and operations work happens inside vendor portals. Invoice status, payment status, shipment updates, support tickets, contract renewals, and order details are often sitting behind a web login.

Cowork browsing could open the vendor portal, search for the right invoice or order, capture the current status, and draft a response for the internal team.

Prompt idea:

Check the vendor portal for invoice 10482.
Find the current status, payment date if available, and any open notes.
Summarize what you found.
Then draft a short Teams message to finance with the update.
Do not send it until I review it.

3. Customer portal research

Customer service teams often need to check external portals before replying to a customer. That could mean checking an order, subscription, case, shipment, license, claim, or account record.

This is a strong Cowork browsing scenario because it combines browser work with communication work.

Prompt idea:

Open the customer portal and check the status for customer Contoso.
Look for the latest open request, current status, owner, and next action.
Summarize the findings.
Then draft a customer-ready email response.
Do not send the email until I approve it.

4. HR onboarding portal updates

Onboarding work is full of small browser tasks. Create a profile. Fill out required fields. Check what is missing. Update a checklist. Confirm access requests.

Cowork browsing could help prepare those steps while keeping the human in control for sensitive actions.

Prompt idea:

Open the HR onboarding portal for the new hire listed in this email.
Review what fields are required.
Draft the onboarding profile using the source email and attached documents.
Flag anything missing.
Stop before saving or submitting changes.

5. Municipal or government web form work

This is where I think browsing gets very interesting for public sector and municipal scenarios.

There are still many web forms, portals, service request systems, permit lookups, inspection pages, and public-facing intake tools that require browser-based work.

Cowork browsing could help collect information, check status, prepare form entries, and draft the next action while keeping final submission under human approval.

Prompt idea:

Open the permit status portal and check application PR-2026-0142.
Capture the current status, last update, required action, and any missing documents.
Summarize the result.
Then draft an internal update for the service team.
Do not submit any forms or make changes without approval.

The pattern

The pattern is simple.

• Use Cowork for browser tasks that are repetitive.
• Use it where the user already has access.
• Use it where the work involves checking, entering, preparing, or summarizing information.
• Keep human approval in place before anything sensitive is submitted.

I would not start with high-risk demos like payments, account changes, or anything that feels too close to personal data. Start with business workflow examples where the value is obvious and the review step is clean.

Before testing Copilot Cowork browser-based scenarios, check the admin setting first.

One checkbox can completely change what Copilot Cowork is able to do.