“How much will this cost us?” It is always the first question from finance when I show SharePoint agents. On 6 March 2025, Microsoft published its guidance on consumption-based pricing for agents built in SharePoint, so I finally have a clear answer.
1️⃣ Two ways people use SharePoint agents
- Users with a Microsoft 365 Copilot licence can use SharePoint agents as part of that licence.
- Users without a Copilot licence can also use SharePoint agents, and that usage is billed on a pay-as-you-go basis to an Azure subscription your organisation links.
This is what makes SharePoint agents interesting for mixed organisations: you do not need to license everyone to let everyone benefit.
2️⃣ You pay for usage, not for seats
With consumption-based pricing, the organisation pays for the interactions people actually have with agents. No usage, no cost. That makes it ideal for a pilot, and much easier to explain to finance than another per-user licence.
3️⃣ Control is in your hands
Pay-as-you-go does not mean “unlimited spending”. Admins decide whether to enable it, link it to an Azure subscription and can use Azure cost management to keep an eye on budgets.
How I explain it to customers
- Licensed Copilot users: already covered.
- Everyone else: pay only when they use an agent.
- Finance: set a budget and alerts in Azure, review monthly.
- IT: start with a few high-value sites, measure usage, then expand.
My take
This pricing model removes one of the biggest blockers I see: the fear of paying for licences nobody uses. My advice is simple: pick one knowledge-heavy SharePoint site, such as HR policies or IT support, build an agent on it, turn on pay-as-you-go for a pilot group and measure for 30 days.
Has your organisation already set up pay-as-you-go for SharePoint agents? What was the hardest part? 💬
Leave a Reply