What Microsoft announced at Ignite
On 17 November Microsoft announced that a skills recorder is coming to Edge for Business. A staff member completes a multi-step web process once while Edge records it. The recording is saved as a Copilot Cowork skill that teammates can reuse. Microsoft says the recorder will reach preview by the end of 2026. It needs a Microsoft 365 Copilot licence with usage-based billing turned on. The Ignite 2026 Book of News adds that IT decides whether the recorder is enabled, and recorded skills run within the permissions and policies the employee already has.
The recorder builds on agentic browsing in Cowork, which Microsoft made generally available on the same day. Cowork can now carry out multi-step tasks across websites for a user. According to Microsoft's Edge blog, Cowork hands sign-ins and payments back to the person and asks before taking sensitive actions. Windows Mode reports that browser access is off by default. Admins turn it on in the Microsoft 365 admin center, either for everyone or only for chosen security groups and users. Microsoft advises running Edge 152.0.4191.53 or newer. Windows Report cites early internal tests in which Microsoft's agents used an average of 30% fewer tokens on common web tasks. Microsoft hasn't published any measurements for the recorder itself.
Several details are still unpublished. A WindowsForum review of the announcement notes that Microsoft hasn't said what the recorder captures, which sites it supports, or how long a recording can run. Microsoft also hasn't said how a skill behaves when a website changes its layout. Anyone planning to rely on a recorded skill for routine work needs those answers before go-live.
Why a recorded skill needs an owner
Record-and-replay automation has been around for a long time. Desktop RPA tools have shipped recorders for years, and teams that used them found that a recording captures one path through a process as it looked on the day. When a supplier portal moves a button or adds a confirmation screen, a scripted bot fails. An AI-driven skill might cope with small layout changes better than a fixed script. Microsoft hasn't promised that kind of resilience, though, and a skill that improvises on a changed page could enter the wrong value without anyone noticing.
Sharing raises the stakes. A private recording affects one person's work. A shared skill runs the same steps under every teammate's permissions, so a flaw in the recording repeats each time someone calls the skill. Costs grow with use as well. Microsoft's Cowork admin documentation lists tool and skill calls and browser tasks among the activities that count toward consumption. A skill the whole office picks up will show on the bill.
The same documentation describes the controls admins already have. Access to Cowork is granted through spending policies that select Cowork, and Microsoft warns that a low credit limit doesn't block access. Each browser task Cowork starts is recorded in the unified audit log. Cowork also follows the Edge allow and block lists an organisation already applies. Automated tasks run as the user who created them, and by default Cowork asks for approval before it sends an email, posts a message or changes a shared system. Agent identity has a limit, too: WindowsForum points to commentary arguing that giving an agent its own identity doesn't protect it from prompt injection, so a skill that visits a hostile page is still exposed.
What it means for NZ organisations
A lot of routine admin in NZ firms runs through web portals with no usable API, such as freight bookings, wholesaler ordering sites, insurer claim forms and government portals. The recorder will look most appealing for exactly that work, because a staff member can automate a weekly chore without waiting for an integration project. The person best placed to record a portal task is often the person least likely to hear when the portal changes. Without an owner and a test routine, a broken skill is usually found after it has done damage, when a supplier rings about a wrong order or a filing is late.
Licensing will decide who sees the recorder at all. Many smaller NZ organisations run Microsoft 365 Business plans without Copilot, and the recorder requires Copilot with usage-based billing. Managed agent browsing, which gives each agent its own window and Entra identity, is in preview for Microsoft 365 E5 customers. Few small and mid-sized NZ firms hold E5. For firms without Copilot, the practical options are still Power Automate desktop flows or a proper integration, and that choice deserves a fresh look whenever a vendor's portal adds an API.
Data handling needs the same attention as any other automation. Microsoft says Cowork follows the same data residency model as Copilot and processes task files in a temporary environment inside the Microsoft 365 service boundary. A recorded skill that types customer details into a third-party website still sends that data to the third party, and your privacy obligations go with it. We'd treat any skill that touches personal information or payments the way we'd treat a new integration: someone approves it and someone reviews it.
We think the recorder is a reasonable tool for low-risk, repetitive portal work that a person can check afterwards. It's a weak fit for high-volume or financially sensitive processes, where a supported integration or a designed workflow will hold up longer. Our process and automation team sees the same split in RPA projects. When deciding which processes suit AI-driven automation, firms can apply the governance questions in our AI consultancy work.
Next steps before the preview arrives
- Decide now whether the recorder stays off when the preview reaches your tenant. The Book of News confirms IT controls enablement, so set the default deliberately.
- Scope Cowork access through a spending policy tied to a security group, and set per-user limits. A low limit doesn't remove access.
- Apply Edge allow and block lists so Cowork browsing reaches only the sites you've approved.
- Keep a short register of candidate tasks. For each one, record the portal, how often the task runs, who owns it and what a failure would cost.
- Require every shared skill to have a named owner, a test after any portal change, and a periodic check of its entries in the unified audit log.
- Keep payments, sign-ins and anything involving personal information under human control, even where a skill could technically run them.
- For tasks that run hundreds of times a month, price a Power Automate flow or an API integration against Cowork's usage-based charges before standardising on a recorded skill.
Sources
- Edge for Business becomes the most used enterprise browser and unveils Ignite 2026 innovations (Microsoft Edge Blog)
- Microsoft Ignite 2026 Book of News
- Manage Copilot Cowork for your organization (Microsoft Learn)
- Edge for Business at Ignite 2026: What's New (Windows Mode)
- Microsoft Edge for Business Gets Smarter With AI Agents and New Enterprise Security Tools (Windows Report)
- Microsoft Edge Skills Recorder for Copilot Cowork: Preview Timeline, Licensing and IT Controls (WindowsForum)
Want to know what this means for your organisation? Our team in Auckland can show you your top three opportunities in a free 30 minute assessment.
Get my free assessment How we help