Microsoft Copilot Cowork for finance teams: when to use it, what it costs, and how to get started

You finish the spreadsheet, and then someone asks for the management summary, a list of exceptions, and a version that makes sense to the budget owners. If you are the Excel person on a finance team, you probably recognize this part of the job.

That is the work I wanted to try with Microsoft Copilot Cowork. Can it take an assignment through the analysis, write the accompanying briefing, and keep the two consistent when I ask for changes? More to the point, does that save enough effort to justify the setup, usage charges, and checking?

I would keep using Copilot in Excel when the work centers on building and inspecting a workbook. Cowork is worth considering when you can describe a larger assignment and leave it to work through the steps before you review the files. This post explains that choice, the costs and admin setup, and what happened when I tried a small accounts payable review.

Product and pricing information checked November 5, 2026. This article covers Microsoft Copilot Cowork with a work account. The AP example below was run in Cowork on that date; all four prompts and actual results are included.

What is Microsoft Copilot Cowork?

Cowork lets you give Microsoft Copilot an assignment to carry out over several steps. It makes a plan, uses the tools available to it, and shows its progress. Microsoft documents creating Office files, finding work information, preparing communications, managing files, and scheduling tasks. Work and school access is generally available; personal-account Cowork is a separate preview. See the official overview.

For example, you could ask it to prepare an overdue-invoice review workbook and a management briefing, then revise both after checking the exceptions. It can continue cloud tasks while your laptop is off, according to Microsoft's general-availability announcement. You come back to work you can inspect, rather than having to supervise each step as it happens.

There is overlap here: ordinary Copilot Chat can analyze information and create files, and Copilot in Excel can make multi-step workbook changes. Cowork's case depends on how much of the assignment you can usefully delegate. Opening a second file is not, by itself, a reason to switch tools.

The names do not help. Claude Cowork is Anthropic's separate product, with separate access and billing. Using an Anthropic model inside Microsoft Copilot does not give you a Claude subscription. Microsoft Copilot Code focuses on building software, and GitHub Copilot is another coding product. This article covers Microsoft Copilot Cowork with a work account.

I looked at a related problem in my May article about repurposing variance commentary for different audiences. The need is familiar, although the preview-era access instructions in that post have changed. Use the current setup steps below.

When would a finance team actually use it?

Think about what you would hand a colleague. "Help me fix this forecast formula" calls for working together in the workbook. "Use these agreed figures to prepare the review pack, flag the exceptions, and draft the follow-up list" is closer to the assignment I would give Cowork.

These are starting points, not product restrictions. Microsoft's Excel documentation includes edit, plan, and chat modes. If you can finish the job comfortably there, you do not need to migrate it to Cowork just because the button exists.

I would also separate a recurring data-preparation problem from a review assignment. If you clean and combine the same exports every month, a refreshable Power Query workflow may remove that work altogether. I covered that approach here:

What does Cowork cost?

For a work account, Cowork usage is metered on top of the required Copilot license. A Copilot button in Excel does not mean unlimited Cowork runs are included. There are three parts to the budget:

As of November 5, 2026, the US enterprise Copilot add-on lists $30 per user/month, paid yearly. The Business add-on lists $21, currently offered at $18 per user/month paid yearly, or $25.20 on a monthly subscription. Eligibility, promotions, and your agreement matter. Check what you already own before adding another license charge to the budget.

Usage is measured in Copilot Credits, not a fixed price per prompt. Microsoft's credits guide gives rough estimates of 100-300 credits for light work, 300-700 for medium work, and over 700 for heavy work. At $0.01 per credit, that is roughly $1-$3, $3-$7, or more than $7. Model choice, runtime, context, and tool use affect the bill; these ranges are estimates, not caps.

For a little budget arithmetic, suppose five people each run twenty assignments a month at 500 credits apiece. That is $500 in monthly usage. Five new $30 enterprise Copilot licenses would bring the example to $650, plus the base Microsoft 365 subscriptions. If the licenses are already paid for, the extra usage is still $500. This is an illustration, not the measured cost of the AP test below.

I did not capture a reliable credit total for my test, so I cannot tell you what that run cost. During a pilot, have the admin check actual consumption under Copilot > Cost Management, including revisions and repeat runs. Microsoft explains the consumption views and spending controls. The useful number is what you spend getting to a result you can use.

What needs to be enabled?

For this work-account experience, Microsoft's getting-started requirements are an assigned Microsoft 365 Copilot license, Cowork access, and usage-based billing. The Excel-and-Word example does not require the Frontier-only App skill. You do not install an Excel add-in to run it.

1. Confirm the license. Have your Microsoft 365 admin check the Copilot entitlement assigned to your work account.
2. Configure billing. A Billing or Global administrator opens the Microsoft 365 admin center, then Copilot > Cost Management. If billing has not been initialized, use Get Started, select the billing method, and configure the default spending policy. Review its scope: the default setup targets all users, so customize it for a pilot.
3. Grant Cowork to the pilot group. Under Configuration, create or edit an identity-based spending policy. Select the security group containing your pilot users, select Cowork under agents and services, and set the billing method, credit limits, and alerts. Review whether new services should be added automatically, then save.
4. Test from the user account. Open Microsoft Copilot, select Cowork, and try a small fictional-data task. If a usage-plan banner blocks you, check that a policy both includes your group and selects Cowork.

The precise screens and role requirements are in Microsoft's billing setup guide and spending-policy instructions. Current policy guidance calls for at least 2,000 credits per user per month; use the requirements shown in your tenant rather than copying an old preview screenshot.

The spending policy grants access. Making the Cowork tab visible is not enough, and the old Cowork entry under All Agents no longer grants access. A tiny credit limit also does not block access; users must be outside every policy selecting Cowork to be excluded. Limits are evaluated asynchronously, so they are not an instantaneous dollar cutoff. See the current access-control guide and admin guidance.

I ran into this myself: Cowork was visible, but a usage-plan banner stopped me from starting. Enabling Cowork in the spending policy covering my account cleared it. No amount of improving the prompt was going to fix that one.

A small test: prepare an AP review package

For the test, I asked Cowork to review ten fictional invoices and produce an Excel workbook plus a one-page Word briefing. Then I asked it to check the rules and add a useful follow-up list. I ran all four prompts in one Cowork task using Auto / Medium on November 5, 2026.

Ten invoices keep the arithmetic small enough to check by hand. The point of trying Cowork here was to see how it handled the workbook, briefing, and revisions together. I did not run a head-to-head speed or cost comparison with Copilot in Excel.

Download the reader ZIP or open the standalone GitHub repository. It contains only the fictional invoices, these four prompts, and a short README. Prompt 1 includes all the data, so you can also follow along directly from this page without uploading a file.

1. Agree on the job before building

Start a new Cowork task and paste the full prompt below. Read its plan before continuing, especially the duplicate rule: two vendors can use the same invoice number, and both copies of a potential duplicate must stay visible.

Help me plan an accounts payable review for a fictional business, as of October 31, 2026. Do not create files yet. Use only the data below; do not search my work files, email, or the web. All amounts are USD. This is a practice review, not payment authorization.

RowID,VendorID,Vendor,InvoiceNo,DueDate,AmountUSD,Approval,PaymentStatus
AP001,V001,Northstar Packaging,INV-1042,2026-10-20,12000,Approved,Unpaid
AP002,V002,Harbor Freight Co,F-883,2026-10-31,4500,Approved,Unpaid
AP003,V003,Clearview IT,MS-210,2026-11-05,3200,Approved,Unpaid
AP004,V004,Elm Facilities,INV-77,2026-10-25,2400,Pending,Unpaid
AP005,V005,Cedar Supplies,CS-501,2026-10-15,1800,Approved,Unpaid
AP006,V005,Cedar Supplies,CS-501,2026-10-15,1800,Approved,Unpaid
AP007,V006,Pine Consulting,PC-009,2026-10-10,6500,Approved,Paid
AP008,V007,Lake Office,INV-77,2026-10-28,900,Approved,Unpaid
AP009,V008,Beacon Safety,BS-38,2026-10-30,0,Approved,Unpaid
AP010,V009,Meadow Services,MD-615,2026-10-31,5100,Pending,Unpaid

Keep all ten source rows, including both potential duplicates. A duplicate is the same VendorID AND InvoiceNo; trim spaces and ignore case for this comparison. Do not identify duplicates from InvoiceNo alone.

Assign exactly one status to each row, using this priority:
1. PaymentStatus Paid: Already paid.
2. AmountUSD zero: No amount.
3. Duplicate key: Duplicate hold for EVERY row with that key.
4. Approval other than Approved: Approval hold.
5. DueDate after October 31, 2026: Not due.
6. Otherwise: Ready for review. Due on October 31 counts as due.

I want an Excel workbook with an unchanged Source sheet and a Review sheet containing the as-of date, a status summary, and row-level results with reasons. Also plan a one-page Word briefing for an AP manager using the same results. Retain the full source-row amount total as an import control, but do not describe it as the true liability balance because it includes paid and potentially duplicated rows. Never send messages or initiate payments.

Restate the rules and propose the deliverables. Flag any ambiguity before building.

2. Produce the workbook and briefing

If the plan matches your rules, use this second prompt in the same task. It asks for downloadable files and formulas you can inspect, with the briefing based on the workbook's results.

Create the agreed files now: ap-review.xlsx and ap-briefing.docx.

In Excel, put Review first and Source second. Preserve all ten original rows and all original field values in Source. On Review, put one editable as-of date, initially October 31, 2026, above the results. Use actual Excel dates and numeric amounts. Use formulas for the duplicate count, status, status counts, status amounts, and reconciliation. Keep the formulas understandable and show the duplicate comparison key. A row's reason must explain its assigned status. Include RowID so I can trace every result back to Source.

Above the row detail, show counts and amounts by status, the Ready for review amount, the full source-row amount total, and a check that all statuses sum to that source total and all status counts sum to ten. Label the source total as an import control, not the true liability balance. Keep paid and potentially duplicated rows in that control.

Create a one-page Word briefing from those calculated results: as-of date, amount ready for review, items needing attention with RowIDs, and the next decisions for the AP manager. Call duplicates potential duplicates, not proven duplicate liabilities. This is a review pack, not approval to pay.

Use white backgrounds, charcoal text, and restrained red accents. Make headers readable, freeze the row-detail headers, and provide filters. Use text statuses as well as color. No macros, external data connections, messages, or payments. Provide both downloadable files and tell me if any requested feature could not be created.

Cowork used the Excel and Word skills to build the files. It put the review summary above the invoice detail and prepared a shorter briefing for the AP manager.

3. Check the business rules and recalculation

Here is where knowing the expected answer helps. The next prompt names the rows and totals to check, including the two vendors that share an invoice number. It also asks Cowork to change the review date and actually recalculate, rather than just describe what ought to happen.

Check the files you created against the original data and business rules. Inspect the workbook's actual cells and formulas, not just your earlier response. Do not change the original source values to make a check pass.

At October 31, 2026, verify these independent controls:
- Ten source rows totaling $38,200.
- Ready for review: AP001, AP002, AP008; three rows totaling $17,400.
- Duplicate hold: AP005 and AP006; two rows totaling $3,600. Retain both.
- Approval hold: AP004 and AP010; two rows totaling $7,500.
- Not due: AP003; one row totaling $3,200.
- Already paid: AP007; one row totaling $6,500.
- No amount: AP009; one row totaling $0.
- All six status groups reconcile to ten rows and $38,200.

AP004 and AP008 share InvoiceNo INV-77 but have different VendorIDs: neither is a duplicate. AP002 is due on the as-of date and must qualify. AP009 must not be treated as missing data.

In a disposable copy, change the as-of date to November 5, 2026 and recalculate: AP003 should become Ready for review, giving four rows totaling $20,600. Other statuses and the $38,200 source control must stay unchanged. Separately test a leading/trailing space and lower-case version of CS-501 in one duplicate row: both rows must remain on Duplicate hold. Restore the original date and data before returning the final workbook.

Reconcile the Word briefing to the final workbook at October 31. Report each check as Passed, Failed, or Not executed, and distinguish inspecting a formula from actually recalculating it. Fix any confirmed errors in the generated calculations or briefing, then give me the corrected files. If your tools cannot execute a check, say so explicitly.

Cowork reported running its recalculation checks in LibreOffice. I also tested a disposable copy in Excel for the web: moving the review date to November 5 changed the ready amount to $20,600; restoring October 31 brought it back to $17,400.

4. Make the follow-up useful

The figures are useful, but the AP manager still needs to know what to do with the exceptions. This last prompt adds suggested actions and owner roles to both files. It does not send anyone a message or assign a real task.

Improve the reviewed pack by making the follow-up work clearer. Add Next action and Suggested owner role to each Review row, using this mapping:
- Ready for review: Review for payment run; AP manager.
- Duplicate hold: Verify invoice and supporting record; AP analyst.
- Approval hold: Obtain approval; Budget owner.
- Not due: Revisit on due date; AP analyst.
- Already paid: Confirm payment reference; AP analyst.
- No amount: Check whether the zero-value record should remain; AP analyst.

Use role names only, not invented people. Update the one-page Word briefing with a compact action list grouped by role, including the relevant RowIDs. These are suggested assignments, not tasks sent to anyone.

Keep the October 31, 2026 as-of date, source data, status rules, and every amount unchanged. Recheck the $17,400 Ready for review amount and $38,200 source control, and give me the revised Excel and Word files. State that the Word document is a snapshot and must be regenerated after workbook changes.

The final briefing fitted on one page, with follow-up grouped by AP manager, budget owner, and AP analyst. It is a snapshot: if you change the workbook, you need to regenerate the briefing. Keep that in mind before forwarding last week's reassuringly tidy document.

What worked, and what I would watch

The useful part was asking for a change once and getting it reflected in the workbook and the briefing. That is work an analyst would otherwise need to coordinate. For a larger review pack, I can see the appeal, provided the files are still straightforward to check.

Checking them took work. The generated duplicate count, for example, used COUNTIF. It handled these invoice IDs, but an ID containing a wildcard such as * or ? would need an additional exact-match check. Ten clean test rows cannot tell you how a workbook will behave with every export your ERP produces.

This is why I keep coming back to Excel fundamentals. You need to predict the answer and explain the exceptions well enough to catch a plausible mistake. The Learn, Confirm, Extend approach I use when teaching Excel alongside Copilot applies here, too:

A wrong business rule can also produce several files that agree beautifully with each other and are all wrong. For a first pilot, I would keep the scope as narrow as this test: fictional data, file creation, and human review. Broader searches, messages, or payment-related actions need their own permissions and controls.

And somebody still has to own the process. Cowork cannot settle a team's disagreement about the authoritative file or who handles an exception. I made a similar point in this post about finance skills and adoption:

When you review a pilot, count the time spent checking and correcting the files alongside the credits used. That will tell you more than how quickly the first download appeared. Keep the work in Excel where that is easier; expand Cowork where it actually saves the team effort.

Start with one assignment your team recognizes

For guided practice, I offer Copilot Cowork training for finance teams around familiar work and the features your organization can access. For the Excel foundations, my full LinkedIn Learning course, Excel with Copilot: AI-Driven Data Analysis, is free and no account is required.

Try this: take the next review request on your calendar and write down what needs to exist when it is done. If it is mainly a better workbook, start in Excel. If it includes a briefing and follow-up material that you can describe and check, you have a candidate for a small Cowork test.