Inference Public

AWS Quick guideChoosing your route

Microsoft 365 Copilot or AWS Quick? How public bodies should make the choice

How UK public bodies should choose between Microsoft 365 Copilot and AWS Quick on evidence: assumptions to test, strengths of each, and a fair comparison.

Two colleagues weighing up two options at a table

Most public bodies already run Microsoft 365, so Microsoft 365 Copilot is often the assumed next step. Several things make that assumption feel settled:

For many organisations Copilot will be the right choice. It should still be a choice, made on evidence. Selecting an assistant automatically skips the questions that decide whether it will be safe and good value:

AWS Quick, AWS's AI workspace, has been available in the London region since March 2026 and is a credible option for some public bodies. This article covers four things:

It describes both products as their vendors document them on 20 November 2026. Inference Public works on AWS, and we say so. Our aim is that the decision is made on evidence.

Why Microsoft is the default

Microsoft's position in UK public services is built into how they buy technology, as well as how they use it:

None of this makes Copilot the wrong choice. The CMA's findings cover AWS as well as Microsoft, and the right answer will depend on each organisation's work rather than on the market.

It does mean that adding an AI assistant because the licence is already on the agreement is different from choosing it on its merits. Where the Green Book and relevant business-case requirements apply, an AI investment should be appraised against credible alternatives, including the existing arrangement. The depth of appraisal should be proportionate to the decision, the expenditure and the risks.

Four assumptions worth testing

"We already have Microsoft 365, so we are ready for Copilot"

Copilot answers using data the user already has permission to access, so the accuracy of your SharePoint and OneDrive permissions decides what it can expose.

Microsoft is direct about the risk. Its deployment blueprint for Copilot starts with remediating oversharing, then setting guardrails and meeting regulations. The blueprint uses SharePoint Advanced Management, now included with Copilot licences, and controls such as Restricted Content Discovery to keep sensitive sites out of Copilot's reach.

Owning Microsoft 365 therefore does not mean being ready for Copilot. The same is true of Quick, which also enforces the permissions it finds. The readiness work on permissions, content ownership and withdrawal of superseded guidance is the same whichever product you choose, and it should come before the product decision.

"Copilot is cheaper because we already pay Microsoft"

Microsoft 365 Copilot

AWS Quick publishes per-user prices in US dollars (shown here at 20 November 2026), plus a $250 monthly infrastructure fee for each organisation account and charges for usage above each plan's allowances:

Quick planPrice per user per monthIncluded agent time
Essentials$31 hour (3 hours until 31 January 2027)
Professional$208 hours
Enterprise$4018 hours

Essentials supports chat, research and Quick Flows. Advanced multi-step automation in Quick Automate, and authoring Quick Sight dashboards, require Enterprise.

Neither product is simply cheaper. Cost depends on three things:

Model it per user group, at contract prices rather than list prices, before assuming either product is the economical choice.

"Our knowledge is all in Microsoft 365"

Often it is not. Guidance may live in Confluence, case data in line-of-business systems, and performance data in an analytics platform.

Both products can reach beyond Microsoft 365. Copilot can reference third-party tools and services through Microsoft Graph connectors or agents, and returns connector data only where the user has permission. Connectors use different models: some synchronise content into Microsoft 365, and others query the source at the time of the question. Each model has its own indexing, permission and administration behaviour. Quick builds knowledge bases over SharePoint, OneDrive, Confluence, S3 and other sources, and Quick Sight works with data held in AWS.

Spreading knowledge across several systems does not, by itself, favour either product. The question is which one covers your actual sources, with the permission behaviour, reporting and integrations you need, at an acceptable cost.

"The trials prove the value"

The UK trials are valuable, but they all tested Copilot, because Copilot is what most public bodies already had. Their results vary by population and method:

The trials say nothing about how Quick would have performed on the same tasks, and nothing about your organisation. The only way to know is to measure.

Where each product is likely to be stronger

Microsoft 365 Copilot

AWS Quick

Quick's potential advantage is a separate AI workspace that combines research, knowledge, applications, workflow automation and AWS analytical capabilities. This depends on regional availability, permissions and licensing. In practice:

An existing AWS landing zone helps, but it does not make Quick simple. Quick brings its own identity, knowledge base, encryption and operational decisions, several of which cannot be changed later.

The actual decision

The choice comes down to which product covers your required information and tasks with fewer unsupported assumptions, a lower total operating cost and stronger measured outcomes.

Questions that should decide it

QuestionWhy it matters
What tasks, for which staff?In-application drafting suits Copilot. Cross-source research, reporting over AWS data and AWS workflows may suit Quick
Which sources must it reach, and with what permission behaviour?Coverage, indexing and permission checks differ by connector in both products
How accurate are permissions today?Both products expose what users can already see. Remediation comes first either way
Where must data be stored and processed?The products differ, and Microsoft's UK processing is a dated expectation that needs confirming
What will it cost per user group, at contract prices?Licence tiers, included allowances, usage charges and connector costs change the comparison
How will records, FOI and retention work?Both create prompts, outputs and logs that are recorded information
What skills and platforms do you already run?A second platform has a real operating cost
How do the products perform on your own work?Measured results are the only evidence that settles quality

How to run a fair comparison

A bounded comparison settles the question faster than a long debate. Run it in three parts, and include your current way of working as a third comparator.

1. Shared knowledge tasks Use the same approved sources, users and questions for both products, with at least 20 real questions and agreed answers. Fix permissions and content first, so neither product is judged on the state of your SharePoint. Measure:

2. Product-specific work Test what each product is designed for, within your organisation's agreed requirements:

Score these separately from the shared tasks. Never mark a product down for lacking a feature outside your agreed requirements.

3. Operational and commercial evaluation Compare:

Measure output quality, correction effort and completed work as well as claimed time savings. Record the decision and the evidence, including why each alternative was not chosen.

None of this effort is wasted. The permission remediation, the question set and the evaluation method carry over to whichever product you choose.

Using Quick alongside Microsoft 365

For most public bodies the realistic question is whether AWS Quick adds value alongside Microsoft 365, rather than whether to leave Microsoft. Quick reads SharePoint and OneDrive and offers Microsoft 365 extensions, so staff can keep working in Microsoft 365 while Quick serves the specific jobs it is chosen for.

Some organisations will run both: Copilot for in-application work, and Quick for research or reporting over AWS-hosted data. That can be sensible, but it doubles some governance work:

Decide deliberately which tool is used for what, and tell staff.

What does not change

Whichever product you choose, the quality and safety of answers depend on the content behind them and the controls around them:

Our article on treating RAG as a data product explains why. The AWS Quick FAQ covers Quick's identity, encryption and data location decisions. Build RAG, use Bedrock Managed Knowledge Base, or adopt AWS Quick? covers the wider architectural choice, including purpose-built services for the public.

The free AWS Quick readiness checklist covers the groundwork, and most of it applies to Copilot as well. If you want help running a fair comparison as part of a Discovery, see AWS Quick Readiness, Implementation & Assurance.


Further reading

Strategic Partnership Arrangement 2024 (Government Commercial Agency)

CMA, actions on business software and cloud services

CMA, SMS investigation into Microsoft's business software ecosystem, roadmap (16 October 2026)

Government Cloud First policy

HM Treasury, The Green Book

Microsoft, oversharing deployment blueprint

Microsoft, SharePoint Advanced Management for Copilot

Microsoft 365 Copilot UK enterprise pricing

Microsoft 365 Copilot privacy, data and connectors

Microsoft, in-country data processing for Copilot (April 2026 update)

AWS Quick pricing

GDS, Microsoft 365 Copilot cross-government findings

Microsoft, five-year agreement with UK government

Microsoft, Copilot Credits

AWS Quick regions and data processing

AWS Quick in London

HMRC, phase 3 Copilot evaluation

All insights

Start a conversation

Let’s talk about what you need to build.

Bring the service, the constraint or the engineering question. We’ll work through a sensible starting point.

Discuss a project