Microsoft’s 28 October results do not justify an immediate Copilot or Azure expansion. If you are budgeting for 2027, evaluate the selected workflow first, then obtain written pricing, regional commitments and exit terms.
Microsoft published the results on 28 October 2026 for the quarter ended 30 September. The detailed quarterly release announced no price change. For buyers, the rapidly growing contract backlog and Azure’s 48% revenue growth provide useful context for the next contract negotiation.
What do Microsoft’s quarterly figures tell buyers?
According to Microsoft’s quarterly release, revenue reached $92.3 billion, up 19% year over year. Microsoft Cloud revenue rose 30% to $63.9 billion. Azure revenue grew 48%, while Microsoft 365 commercial cloud increased 17% as reported and 18% in constant currency.
The gap matters in procurement: Azure revenue is growing much faster than Microsoft 365 commercial cloud revenue. It does not set the future price of any individual product. It does give buyers a reason to address price-review rules, minimum commitments and capacity terms explicitly in a multi-year Azure AI agreement.
Commercial remaining performance obligation, or RPO, increased 73% to $677 billion. Dividing 677 by 92.3 puts that figure at about 7.3 times total quarterly revenue. The release does not state the recognition schedule for RPO, so the ratio is not a revenue forecast.
The $76.8 billion Agents and Infra revenue figure comes from a different reporting view than the $63.9 billion Microsoft Cloud metric. Agents and Infra is a reporting segment reflecting Microsoft’s fiscal 2027 segment changes, with earlier figures recast. The amounts cannot be added, and neither should be treated as a component of the other.
Which action fits your procurement position?
| Buying situation | Action | Basis for the decision |
|---|---|---|
| Your Microsoft 365 or Azure agreement is approaching renewal | Request written pricing, price-review rules, minimum commitments and exit terms. | Enter the negotiation with comparable offers covering the full contract period. |
| You plan to give Copilot licences to more employees | Evaluate one bounded workflow first. | Compare cost per successful task, elapsed time and correction effort with the current process. |
| You are preparing a multi-year Azure AI commitment | Request a price-review date, SLA, regional terms, named support ownership and an exit path. | Microsoft lists service capacity constraints among its risk factors. |
| The workflow connects several Microsoft services | Build a dependency inventory and test what can move to another provider. | Deep integration can make a later provider change more difficult. |
| You have little Microsoft exposure or no selected workflow | Wait for a commercial offer and compare it with other platforms. | A $677 billion contract backlog does not show which provider fits your task. |
For a multi-year commitment, the guide to Maia 300 and Azure AI contract terms covers price reviews and exit provisions in more detail. Before widening Copilot access, define where Microsoft 365 and Teams are sufficient. The AI ROI calculator can organise cost, time-saving and correction assumptions.
How should you measure the value of expansion?
Run the Copilot or Azure AI pilot on the same tasks as the current process. Track successful completion, elapsed time, human correction, total running cost and permission failures. Use those results to decide how many licences or how much capacity to buy.
For a Hungarian-language workflow, the evaluation set should contain Hungarian emails, documents, searches and approval comments. Include company terminology and inflected search terms so that the pilot reflects the language used in production.
The evaluation should reflect the workflow:
- For knowledge retrieval in Teams or SharePoint, check the source document, citation and compliance with existing access rules. The guide to Microsoft 365 agent permissions provides a more detailed question set for limiting access.
- For a Dynamics-linked automation, test write permissions, approval controls and reversal of an incorrect action.
- For an Azure AI workflow, record the service, model identifier, region, SLA and fallback behaviour.
Use the same fields for every task in the pilot evaluation: successful or unsuccessful completion, elapsed time, human correction, running cost and cause of failure. This prevents a faster system with higher correction effort from receiving an artificial advantage.
If your AI system will span several Microsoft services, review the available integration, evaluation and operating options. Enterprise AI solutions
What should the Microsoft agreement contain in writing?
Build the 2027 budget from the commercial offer and contract schedules. Separate licences or cloud usage, integration, identity and access controls, monitoring, user support and the potential cost of a later migration.
The negotiation package should answer at least five questions:
- Which unit price, discount and minimum commitment apply throughout the term?
- When can pricing be reviewed, and under which conditions?
- Which region will provide the service, and what does the SLA cover?
- Who owns support when a problem spans Microsoft 365, Dynamics and Azure?
- In which formats can data, logs, evaluation cases and integration settings be exported at the end of the agreement?
Test portability during the pilot. Keep prompts, evaluation cases and business rules separate from provider-specific settings. Record which functions require a Microsoft service and which components can be replaced independently.
When should the review begin?
Start now if renewal is approaching, you are expanding Azure capacity or more employees will receive Copilot licences. Before negotiations, assemble the current cost, pilot results, required service level and estimated effort involved in changing provider.
You can wait if there is no selected workflow, near-term renewal or commercial offer. Local evaluation, actual pricing and contract terms determine the return for your project.
Close the procurement decision with five checks
- Inventory which workflows depend on each Microsoft service.
- Record current cost, elapsed time, error rate and human correction.
- Obtain written pricing, minimum commitments, SLA, region, support ownership and exit terms.
- Test whether prompts, evaluation cases, logs and integration settings can be moved.
- Expand licences or capacity after the pilot meets predefined business and quality thresholds.