Over recent months, agents have transitioned from a feature to a purchasable item, a shift that warrants attention from anyone involved in software billing. This progression may be overlooked, as each development was announced separately. Microsoft Agent 365 became generally available on 1 May 2026, introducing its own pricing and licensing. Prerequisites were established, and agent activity began to be metered by consumption.
On 10 August, Microsoft launched multi-tenant agent management in public preview, enabling partners to view, install, or block agents across customer tenants. Together, these developments denote the transformation of agents into commercial objects. Agents now have pricing, identity, inventory, and control mechanisms. However, they often lack a designated owner, a budget, or a clear cost allocation. This article addresses that gap, focusing not on technology, but on the underlying commercial question: as customers deploy more agents that incur costs, who is accountable, and how should billing be managed?
The key decision is not the price itself, but rather to whom the cost is assigned. Agent 365 is licensed per user, not per agent. Agents themselves do not hold licenses. Microsoft's own licensing guidance is explicit that the entitlement is tied to the human associated with the agent, described as the user, owner, sponsor, or manager. It sells standalone for $15 per user per month and is included in Microsoft 365 E7 for $99 per user per month. This is a purposeful design choice. Microsoft assigns agent ownership to a specific licensed individual, establishing sponsorship as the accountability model. Every agent is linked to a person. Agent activity is billed separately, based on consumption and measured in credits. Charges are tied to usage rather than headcount. Our previous article on the Copilot Cowork billing wall explains this mechanism in the CSP channel. As a result, a single agent may generate multiple types of charges that appear in different sections of the bill.
| What gets charged | How it behaves commercially |
|---|---|
| Governance license | Agent 365, per user, predictable, attaches to the sponsoring human. Behaves like a seat. |
| The work itself | Consumption-based, varies month to month with activity. Behaves like Azure. |
| Building the agent | Separate tooling, separate commercial terms, often bought by a different part of the business. |
A single agent can involve three distinct billing behaviors and potentially three different budget owners. This complexity defines the core issue. Where do agents come from inside a customer? This detail is particularly relevant for those familiar with shadow IT. Microsoft's agent registry includes agents built by Microsoft, ecosystem partners, the organization itself, and individual creators. The registry also identifies shadow agents and allows for quarantining unauthorized ones. The inclusion of a quarantine function indicates that unauthorized agents are an anticipated issue. The last two categories present commercial challenges. Agents published by the organization or shared by individual creators can be introduced without formal procurement. For example, a finance operations employee may develop a useful agent, or a marketing team member may share one with colleagues. These agents gain permissions, perform actions, and incur costs as they are used. This pattern is familiar, but with new implications. Previously, shadow IT referred to unapproved subscriptions with limited impact. In contrast, shadow agents operate within the business and incur variable expenses, resulting in broader impacts and more complex billing.
Customers are unlikely to address this issue independently, just as they did not resolve self-service purchasing challenges on their own. When new capabilities outpace controls, organizations often either overlook the risks or restrict adoption, obstructing progress. We earlier discussed this pattern in relation to underused self-service portals, and the situation here is similar. In contrast, providers possess two major advantages: a cross-tenant perspective and control over invoicing. Microsoft's multi-tenant agent management is designed for partners with delegated admin privileges, allowing actions within each customer tenant. These tools are intended for partners overseeing the entire estate. This situation requires advisory involvement rather than a technical solution. Four key questions arise: Which agents exist across the customer's tenants? Who sponsors each agent? Which budget is responsible? What occurs if the sponsor changes roles or leaves? The fourth question often leads to challenging discussions. Licensing tied to an individual is simple until that person departs, and an agent continues to operate under their name.
Microsoft has effectively established the technical control plane, including identity, registry, audit, quarantine, and policy features. This foundation is robust and complete. The commercial control plane is less mature, and transparency is important. Accurately attributing consumption spending remains challenging, even for us. Our documentation notes that Microsoft's billing reconciliation file shows only the Azure Plan container, not individual subscriptions. As a result, matching consumption to the correct source depends on usage data, and we sometimes leave charges unattributed to avoid misallocation. This is the current standard for consumption attribution, and agent activity will further complicate the issue. This points to where this has to go. Everything else in a customer estate that costs money eventually acquires the same commercial furniture: an owner, a budget it belongs to, a threshold above which someone approves it, and a line on a chargeback report. Agents have identities. Budgets are the obvious next thing they need, and providers who can already answer "Who authorized this and which department pays for it?" for the rest of the estate will find it easy to extend that question to it.
Ask the inventory question before the customer does: Most customers are unaware of how many agents are active in their tenants or who created them. Initiating this discussion marks you as a trusted advisor, and the cross-tenant view now enables you to provide answers.
Consider sponsorship a commercial responsibility rather than a licensing detail. If entitlement is linked to an individual, sponsorship effectively represents ownership of the budget. Record it as you would any other cost owner.
Decide the attribution model before the volume arrives. Whether an agent spend lands on a department, a project, or a central AI, establish the attribution model before agent usage increases.
The customer's finance team should determine whether agent expenses are assigned to a department, project, or central AI budget while volumes remain manageable. late-arriving spending belongs in the same rules rather than as a separate exception.
We do not manage agents directly, nor is this a product for agent management. Our focus is on the underlying commercial layer: determining who can authorize spending, which part of the customer organization bears the cost, and how the invoice is structured. Both are relevant today. Cost centers let billing be split across a customer's departments, branches, or subsidiaries, with each billing line divided according to the allocation at the time, and a cost center report available at the organization level, so a finance team can see spend by the entity that actually owns it. The Organization Internal Approval Process lets the customer set their own spend thresholds and approval groups, so purchases above a level they choose pause for their own people before anything is provisioned or billed. It is important to be clear about existing capabilities. Cost centers currently apply only to license-based subscriptions. Expanding cost centers to Azure subscriptions and enabling tag-based splits are planned for 2026. As noted, consumption attribution remains a significant challenge. If you are considering agent-related spending across your customer base, now is the time to discuss this with your Cloudmore contact, while it is still a planning matter rather than an invoicing issue. Agents received identities in May and inventory capabilities in August. The next step is budget assignment. The key question for the channel is not adoption, which is already occurring, but rather who can provide cost transparency and identify the responsible party for payment.
Licensing details and dates sourced from Microsoft Learn, the Microsoft Agent 365 licensing FAQ, and Partner Center announcements, current as of 11 August 2026. Prices are listed and indicative. Verify current terms in Partner Center before advising customers. Cloudmore platform behavior reflects the Knowledge Base at the time of writing; roadmap items are identified as such.