Repository navigation
Copilot Investment Assumptions
Copilot investment → Copilot Investment Assumptions
Available since Stable 1857 (PR #787).
The Copilot investment report can show what Copilot costs and what the time it gives back may be worth, but only from your organisation's own figures: what you pay for a licence, and what an hour of your people's time is worth. The product cannot know either, so nothing is set by default. Every figure that needs a missing input says so instead of guessing, and the evidence of use is still shown without it. This page is where an administrator enters those figures once, for everyone who opens the report.
| Where |
Administration → Copilot & reporting → Copilot investment assumptions (#/admin/copilot-investment-assumptions), next to Copilot Adoption settings. The report's Assumptions in force card has an Edit assumptions button, and its What-if dialog a Set the organisation's figures button, that open it for administrators |
| Who can open and save | Holders of the Portal.Administration app role (Portal Permissions). It is not a See PII page, and Administration does not include See PII. The page is kept to administrators because its change history names who changed what. If the web app's EnforcePortalRoles setting is false, every signed-in user holds Administration and can change these figures: see Portal permissions → Switching enforcement off temporarily
|
| Who sees the result | Everyone who can open the report sees the money it models. Readers see the version, the date it was saved and the note, but not who saved it |
| Stored | In the AnalyticsState Azure Table in the solution's storage account: partition CopilotInvestmentAssumptions, row Current. There is no SQL change |
| Applies | To the next report that is built, for every period. See When a change applies |
| Needs | A Storage connection string. Without one the figures cannot be saved |
The page, its help and its validation messages are supplied in English and Spanish. This page quotes the English wording. The note is shown exactly as you wrote it, never translated.
- Set or change the figures
- The fields
- Save, versions and history
- When a change applies
- Two administrators at once
- Where the assumptions are stored
- Errors and what to do
- Choosing figures you can defend
- Limitations
- Agree the figures first. Everyone who opens the report sees money calculated from them, so settle them with whoever owns the Copilot business case, usually finance. See Choosing figures you can defend.
- Open Administration → Copilot & reporting → Copilot investment assumptions. If the page warns No Storage connection string is configured, so assumptions cannot be saved. The report shows evidence without modelled money until one is., the fields are switched off until one is configured: see Where the assumptions are stored.
- In the Prices card, set the Currency, the Licence price a month and the Fully loaded hourly cost. Set the two credit prices only if you want credits modelled in money.
- In the Time and value card, give all three values (conservative, base and upside) for Minutes per active day and for Realisation.
- In Note, write where the figures came from.
- Select Save assumptions. The page confirms Assumptions saved (version {n}). and the change appears at the top of the history.
- Open Copilot investment. The Money is not modelled yet notice goes once every required figure is set and the Value tab shows value and return. The Assumptions in force card and the Method and trust tab list the figures with the source Organisation default, and Method and trust adds Saved by an administrator {when} (version {version}).
The page has two cards, Prices and Time and value, plus a Note. Nothing is pre-filled.
| Field | What it is | Limits |
|---|---|---|
| Currency | A three-letter ISO code, for example EUR or USD. Every price and the hourly cost are in this currency |
Three letters, trimmed and upper-cased on save. Blank means not set, but it is required as soon as any price or the hourly cost is set |
| Licence price a month | What one Microsoft 365 Copilot licence costs a person a month | Above 0, at most 10,000 |
| Price of one Copilot Studio credit | What one billed Copilot Studio credit costs. It adds the licence holders' own billed Studio use to their cost, so it lowers the return | Above 0, at most 100. Optional |
| Price of one Copilot credit | What one Copilot credit costs. It values the preview consumed-credit readings, which stay outside the return | Above 0, at most 100. Optional |
| Fully loaded hourly cost | Salary plus on-costs for an hour of a typical person's time | Above 0, at most 10,000 |
| Minutes per active day: conservative, base, upside | How many minutes Copilot gives back on a day someone uses it. Lowest to highest | Each from 0 to 480. All three or none. They must not go down from conservative to upside; equal values are accepted |
| Realisation: conservative, base, upside | The share of that time that becomes business value rather than slack. Lowest to highest | Each a share from 0 to 1, so 0.5 is half. All three or none. They must not go down from conservative to upside |
| Note | Where the figures came from: a business case, a survey, a pilot. Shown with the report and in its workbook | At most 500 characters. Trimmed |
- Required for modelled money: the currency, the licence price, the hourly cost, all three minutes and all three realisation values. Until they are all set the report shows the evidence of use and says which are missing. The two credit prices and the note are optional.
- A share here, a percentage there. Realisation is a share from 0 to 1 on this page but a percentage from 0 to 100 in the report's What-if dialog. 0.5 here is 50 % there.
- Why three values. The report shows three scenarios, Conservative, Base and Upside, and uses the matching minutes and realisation for each, so a reader sees a range rather than one confident number.
- Decimals. A full stop or a comma works as the decimal separator. The browser catches anything that is not a number before it is sent (Enter a number, using a full stop or comma for decimals.).
Worked example with made-up figures. Take one person who held a licence for the whole of a 28-day period and used Copilot on 10 days, with the licence at 25 a month and an hourly cost of 60. The licence cost is 25 × 28 ÷ 30.44 ≈ 23.0. The value is active days × minutes ÷ 60 × realisation × hourly cost:
| Scenario | Minutes | Realisation | Value | Return |
|---|---|---|---|---|
| Conservative | 15 | 0.3 | 10 × 15 ÷ 60 × 0.3 × 60 = 45 | about 2.0× |
| Base | 30 | 0.5 | 10 × 30 ÷ 60 × 0.5 × 60 = 150 | about 6.5× |
| Upside | 45 | 0.7 | 10 × 45 ÷ 60 × 0.7 × 60 = 315 | about 13.7× |
This only shows the arithmetic. These are the report's illustrative example figures, which are not Microsoft prices, your organisation's figures or measured savings: do not copy them. The report adds the same sums up across every licensed person whose use was measured; the full list is in Copilot investment → Formulas.
Save assumptions checks the figures and saves them as a new version. The line under the title says what is stored: Version {n}, saved by {who} {when}., or Never saved. where nothing has been saved.
- A save that changes nothing says Nothing has changed. and the version does not move.
- Clearing a figure unsets it. Clear a field and save, and the report treats it as missing again. The history records it, for example Fully loaded hourly cost: 60 → empty. Clearing every field is valid.
- A failed save keeps what you typed. The form is only rebuilt after a successful save or a reload.
- Reload the latest is always available. It discards unsaved edits and loads what is stored. It also works when saving is switched off.
- Change history. The card at the bottom lists the last 50 changes, newest first: version, who changed it, when, and one line for each figure that changed ({field}: {from} → {to}). The author is the administrator's sign-in name, or Unknown. An empty history says No changes yet. Older changes drop off the end.
The history is administrative personal data. It names administrators, and figures such as an hourly cost are internal. Keep a screenshot of this page out of public issues and documents.
The report reads the saved figures every time it builds. There is no separate cache of the figures, and the saved version is part of the report's own cache key, so the next report built after a save uses the new figures.
- A report already on screen keeps the figures it was built with until you refresh or reopen it.
- The figures are not stamped on past periods. A change applies to every period opened afterwards, so changing the hourly cost changes last quarter's modelled value as well. They are your current estimate, not a record of what you used at the time.
- The Excel report is built the same way, so a workbook exported after a save uses the new figures. Its Assumptions and method sheet lists each figure with its source, then the note, the version and when it was last saved.
- A reader's own What-if figures override the saved ones for that reader only, in that browser tab. They are never saved.
Every save is checked against the version the page loaded, and again when it is written to storage. If someone else saved in between, nothing is overwritten: you get Someone else saved the assumptions while you were editing. Reload to see their changes, then make yours again. Select Reload the latest, read their change in the history, and enter yours again. Whoever's write reaches storage second is the one refused, even when two saves are made at the same moment.
The figures live in one row of the AnalyticsState Azure Table, in the storage account named by the Storage connection string: partition CopilotInvestmentAssumptions, row key Current. The row holds the figures, the version, who saved it and when, and the last 50 changes. Nothing is written to SQL, so there is no database migration. Runtime State Reference explains the table, how the account is reached, and the Storage Table Data Contributor role the runtime identity needs (Storage Blob Data Contributor does not cover tables).
No Storage connection string. The page shows No Storage connection string is configured, so assumptions cannot be saved. The report shows evidence without modelled money until one is. The fields and Save assumptions are switched off. The report says Assumptions cannot be saved on this deployment: no Storage connection string is configured. on its Method and trust tab. A reader can still try figures with What-if.
Storage unreachable, and saves that time out. The store waits up to 10 seconds for storage. A save that times out may still have been written, so reload and check the version and the history before saving again. A repeat save with the old version would be refused as a conflict if the first one landed.
A row that cannot be read. If the row cannot be read as valid figures, the store does not substitute defaults and does not overwrite it. That covers a failed read of the table, invalid JSON, a member the build does not know, a schema version it does not support, and stored values that break the rules in The fields. Then:
- The report says The saved assumptions could not be read, so money is not modelled. Evidence is still shown.
- This page fails to load with The assumptions store could not be reached. Try again shortly. even though the cause is the row itself. The message is the same for an unreachable store and an unreadable row.
-
Do not edit the row by hand. Deleting it (in Storage Explorer or the portal's Storage browser, Tables →
AnalyticsState, filter onPartitionKey = CopilotInvestmentAssumptions) returns the page to Never saved, loses the history, and lets you enter the figures again.
Each message is the page's own English wording. A save reports every rule it broke at once.
| You see | Meaning | What to do |
|---|---|---|
Someone else saved the assumptions while you were editing. Reload to see their changes, then make yours again. (409, versionConflict) |
Another administrator saved first | Two administrators at once |
Assumptions cannot be saved: no Storage connection string is configured. (503, storageNotConfigured) |
The web app has no Storage connection string |
Configure it: Runtime State Reference |
The assumptions store could not be reached. Try again shortly. (503, stateUnavailable) |
The Table could not be read or written, the runtime identity lacks Storage Table Data Contributor, or the stored row is unreadable | Try again. If it persists, check the storage account and the identity's role, then a row that cannot be read |
The request was not understood. Reload the page and try again. (400, invalidRequest) |
The save arrived without figures or without the version to check against, or could not be read | Reload the page and save again. If it persists, check the web application log |
| Couldn't load the assumptions. or Couldn't save the assumptions. | An unexpected failure with no known code | Try again, then check the web application log and the Health page |
| A validation message from the table below (400) | A figure breaks a rule | Correct it and save again |
| Validation message | Rule |
|---|---|
| The currency must be a three-letter ISO code such as EUR. | Three letters, A to Z |
| Set a currency for the prices and the hourly cost. | A price or the hourly cost is set but the currency is blank |
| The licence price must be above 0 and no more than 10,000. | |
| The credit price must be above 0 and no more than 100. | The Copilot credit price |
| The Studio credit price must be above 0 and no more than 100. | |
| The hourly cost must be above 0 and no more than 10,000. | |
| Minutes must be from 0 to 480. | |
| Give all three minutes values, or none. | |
| Minutes must run from conservative to upside without going down. | |
| Realisation must be a share from 0 to 1. | A share, not a percentage: 0.5, not 50 |
| Give all three realisation values, or none. | |
| Realisation must run from conservative to upside without going down. | |
| The note can be at most 500 characters. |
The report calls everything it computes modelled: these figures decide how persuasive that model is, so choose ones you can explain.
- Licence price. Use what your agreement says you pay for one licence a month, after any discount. The page itself warns that list prices may not reflect your agreement.
- Hourly cost. Salary plus on-costs for an hour of a typical person's time. Use the figure your finance team already uses for other business cases, rather than one chosen for this report.
- Minutes and realisation. The product cannot observe either. Treat the three values as a range from cautious to optimistic, and base them on something you can point to: a pilot, a survey or an agreed business case. Realisation exists because time given back is not automatically value, since some of it is absorbed as slack.
- Record the source in the Note. It is shown on the report and in its workbook, so a reader can see where the figures came from.
- Do not reuse the illustrative example. The What-if example fills the dialog so you can see the page with money on it. Its figures are not Microsoft prices, your organisation's figures or measured savings.
- Quote the version. Because a later change reaches every period, note the version (on Method and trust and in the workbook) beside any figure you present, and export the workbook when you do.
- Money stays modelled. Even with careful figures the report applies them to observed active days. It cannot show that Copilot caused a saving: see Copilot investment → Limitations.
- One set of figures for the whole tenant. There is no separate hourly cost per department or country, and no separate minutes per role. A reader can try different figures for themselves with What-if.
- One currency, with no conversion. Every price and the hourly cost are in the one currency.
- One licence price for every Copilot licence.
- Figures are current, not historical. They apply when a report is built and are not stamped on the periods it covers.
- The history keeps the last 50 changes and is shown only on this page. The report does not say who saved the figures.
-
Saving needs the
Storageaccount. The Contoso demo database has no saved assumptions: see Copilot investment → Try it with the Contoso demo.
Return to Web Portal · Copilot investment · Portal Administration · Portal Permissions
- Copilot analytics overview
- Copilot Adoption user guide
- Copilot Adoption setup (admins)
- Work Trend Index
- Copilot investment
- Copilot spend
- Agent costs
- Prompt categories
- Copilot credit history (preview)
- Agent 365 package catalog
- The Copilot data in depth
- Prerequisites
- App registrations setup
- Install with the installer
- Verify the deployment
- Security & permissions model
- Private endpoints (optional)
- Certificate authentication (optional)
- Manual installation
- Activity & usage analytics (Power BI)
- SharePoint page tracking