An architectural practice is weighing two uses for AI. It could give staff Copilot to cut the time spent searching old projects. Or it could build an app that answers clients’ questions about building specifications. The first budget begins with a headcount. The second starts with the volume and length of inquiries. Microsoft can earn revenue from both.
Paying for employee productivity or for an application’s capacity
A paid business Microsoft 365 Copilot seat can help an employee draft in Word, review a meeting and analyse figures in Excel. The buyer weighs the cost per seat against time saved. Some capabilities incur additional usage charges, so a flat seat fee is only part of the calculation.
An application built on Azure has a different cost driver. Client traffic, the size of specifications sent to a model and the length of the answers influence the bill. Customers can pay for usage or contract for provisioned throughput. Committed capacity can cost money while idle. A purchaser needs to weigh the importance of predictable response times at peak load against the price of quiet hours.
Microsoft on billing for provisioned throughput
Where does an employee’s question about a PDF go?
Suppose a staff member asks about a building specification already in SharePoint. The path is question → permitted content retrieved via Microsoft Graph → model generates an answer → result shown in the app. Copilot respects the user’s permissions. If material was shared too broadly, the assistant can make it easier for authorized employees to find documents they rarely encountered before.
For the commercial service Microsoft documents, uploading a file directly into Copilot Chat stores it in the user’s OneDrive. Interaction records containing prompts and responses are kept in a hidden area of the user’s Exchange Online mailbox. Referring to an existing SharePoint document is a different operation. Downloading a finished report creates a local deliverable as well. Consumer Copilot and custom apps running on Azure have their own storage arrangements.
Microsoft on permissions, storage locations and audit records
Reading the quarter without double counting
On October 28, 2026, Microsoft reported $92.3 billion in revenue and $45.9 billion in operating income for July–September, its first quarter of fiscal 2027. Azure revenue was $33.165 billion, up 48% year over year. Microsoft 365 cloud revenue was $27.778 billion. The former includes conventional cloud workloads. The latter includes existing productivity software. Microsoft Cloud revenue of $63.9 billion aggregates several services. Adding it to Azure revenue would double count.
Management also attributed growth in commercial cloud revenue per Microsoft 365 user in part to premium offerings, including Copilot. The quarter does not disclose standalone Copilot revenue or gross margin. For Google Search, we asked what advertisers gain. For Microsoft, ask how many existing customers upgrade seats and how much additional computing demand their own applications create.
本稿は2026年11月6日時点の法令に基づく一般的な解説です。実行の前に必ず個別にご相談ください。
We take care in preparing this information. If you notice an error, please let us know through our contact page.