Microsoft is now rolling out a similar capability known as Copilot Checkout.

If a user asks Copilot for recommendations — whether that’s software, subscriptions, equipment or services — Copilot can surface relevant products.

Where the seller supports Copilot Checkout, the employee can:

  • Click Buy
  • Confirm delivery details
  • Approve payment
  • Complete the purchase inside Copilot

No browser tabs.
No separate checkout pages.
No familiar “are you sure?” moment.

From Microsoft’s perspective, this is incredibly powerful.

Their data shows people are more likely to complete purchases when Copilot is involved — and to do so faster. That’s why this feature won’t be limited to one platform. Expect to see it across Copilot, Bing, Edge, MSN and other Microsoft services.

Convenient for users — complicated for businesses

For individual consumers, this experience feels seamless and efficient.

For businesses, however, it introduces a very different set of considerations.

The first question is straightforward:

Do you actually want your team buying this way?

In many organisations, purchasing is intentionally controlled. There are processes in place, such as:

  • Approval workflows
  • Budget limits
  • Preferred supplier lists
  • Clear accountability for spending

Copilot Checkout has the potential to bypass some of these controls quietly, especially if it’s adopted casually or without proper guidance.

What about data and payment details?

To function properly, in‑chat checkout needs access to:

  • Payment methods
  • Shipping information
  • Account data

Copilot Checkout integrates with platforms such as PayPal, Stripe and Shopify — all reputable providers. But the real question isn’t whether these systems are secure.

It’s whether your internal policies account for this new method of buying.

Consider the following:

  • If an employee is logged into Copilot with a work account, whose payment details are used?
  • What information is Copilot allowed to access, store or reuse?
  • Are these purchases visible to finance or IT teams?
  • Is there an audit trail — or do transactions disappear into the background?

Behavioural risk is easy to miss

There’s also a behavioural element to think about.

When purchasing becomes frictionless, people naturally buy more. Microsoft openly states that interactions involving Copilot are far more likely to end in a sale.

That’s great for vendors.

But without oversight, it can quietly inflate costs inside your business — especially when purchases feel small, fast, and “helpful”.

This isn’t about banning AI — it’s about deciding

None of this means Copilot Checkout is a bad feature.

It simply means it should be deliberately considered, rather than discovered accidentally after something goes wrong.

If you do want your team to use AI‑based checkout tools, some sensible controls include:

  • Clear rules on who is allowed to buy
  • Defined limits on what can be purchased
  • Approved accounts and payment methods
  • Central visibility of purchases made via AI tools
  • Staff guidance reinforcing that convenience doesn’t remove responsibility

If you don’t want it used, that decision needs to be just as clear.

Because if it’s not documented, explained and enforced, most people will assume it’s allowed.

A familiar pattern with AI tools

This is a recurring theme with modern AI features.

They don’t arrive with a warning saying, “Time to update your policies.”
They simply… appear.

The real question isn’t whether your staff can use them.

It’s whether you’ve decided if they should.

If you’d like help assessing how tools like Microsoft Copilot fit into your purchasing, security and governance processes, contact GZD. We can help you put the right controls in place for your business.ess.

Give us a call  ‣  031 818 9060