Microsoft Financial Results: Q1 FY26


Satya Nadella now refers to Microsoft “building a planet-scale cloud and AI factory” which, with the recent agreement with Open AI, including $250 billion of Azure services (these don’t impact the Q1 results), and Copilot, shows they’re not changing direction any time soon.

Is Microsoft Copilot successful?

Lots of talk in the earnings call about Copilot growth and success with 90% of the Fortune 500 using M365 Copilot and various organisations purchasing 15,000+ seats in Q1 and PWC purchasing 155,000 seats. One should always be carefully sceptical of numbers like this from software publishers – what exactly is “using” and how many people within an org are “using” the software for example?

Copilot functionality is being added into almost every facet of Microsoft’s product portfolio, making it ubiquitous whether users really want it or not!

What are Microsoft’s Financial Results for Q1 FY26?

Revenue = $77.7 billion, an 18% increase

Net Income = $27.7 billion, a 12% increase

Microsoft Cloud = $49.1 billion, a 26% increase

What are Microsoft spending?

  • Capital Expenditure (CAPEX) was up 74% in Q1 FY26 “to support customer demand for…cloud and AI offerings.” Approximately half of that spend was on “short-lived assets” such as GPUs and CPUs for Azure and AI growth.
  • Long-lived assets spend was up 71%, driven by lease commencements for “large datacenter sites”.

You can see here the huge amount of money that Microsoft are spending on building datacentres, primarily to handle AI growth.

Productivity & Business Processes

  • Revenue = $33 billion, a 17% increase
  • Microsoft 365 Commercial Revenue = 17% increase
  • Dynamics 365 revenue = 18% increase

Operating Expenses increased 6% driven by investments in “compute capacity and AI talent”.

The M365 growth was driven by E5 and Copilot. 

Intelligent Cloud

  • Revenue = $30.9 billion, a 28% increase
  • Azure = 40% increase

Operating Expenses increased 4% driven by investments in “compute capacity and AI talent”. 

Earnings Call highlights

  • Microsoft plan to increase their total AI capacity by 80% through FY26 and double their datacentre footprint by 2028. They plan to launch the “world’s most powerful AI datacentre” in 2026 which will hit 2 gigawatts itself.
  • Fabric revenue increased 60% and now has 28,000 paying customers.
  • Cosmos DB revenue increased 50%.
  • Microsoft Sentinel has 40,000 customers.

Microsoft Power BI Premium retired


Microsoft have announced the end of Power BI Premium Capacity SKUs in favour of the newer and shinier Microsoft Fabric. Note that the “Power BI Premium per-user” SKU is unaffected.

Key dates

  • New customers will not be able to purchase Power BI Premium after July 1st, 2024.
  • Existing non-EA customers can renew until Jan 1st, 2025. If your renewal date is after that, you will need to transition to Fabric at renewal. Additional Power BI Premium capacity can be purchased until the end of the agreement.
  • EA customers can continue with Power BI Premium until the end of their contract. If that is post Jan 1st, 2025 they will need to switch to Fabric at renewal. Additional Power BI Premium capacity can be purchased until the end of the agreement.
  • Sovereign Cloud customers are unaffected as they don’t currently have access to Fabric.

Benefits and differences

Fabric is the evolution of Power BI Premium and the next step in Microsoft’s organisation wide data analytics strategy. Thus, as well as the Power BI Premium functionality, Fabric contains additional services and features such as OneLake and various Azure services. Additional benefits include:

  • Fabric can be used to contribute towards your MACC (Microsoft Azure Consumption Commitment) agreement.
  • There is a Pay As You go (PAYG) option for Fabric.
  • Fabric SKUs start at a lower point that Power BI Premium. However, note that Copilot for Power BI (which I assume will become Copilot for Fabric) doesn’t work for the lower end SKUs.

Of course, there is always something that is removed or made more complicated with any product retirement and this is no different.

Each Power BI Premium capacity P-SKU includes the ability to run Power BI Report Server on-premises…but Microsoft Fabric does not, and is not compatible with it. To continue accessing Power BI Report Server, you will need to have SQL Server Enterprise w/SA instead.

Microsoft announcement

FAQ page

Microsoft Fabric licensing & pricing


Photo by cottonbro studio on Pexels.com

Microsoft Build 2023 saw the announcement of Microsoft Fabric – “an end-to-end, unified analytics platform that brings together all the data and analytics tools that organizations need” by combining various products including Power BI, Azure Synapse Analytics, and Azure Data Factory.

Additionally, “Fabric comes with a SaaS, multi-cloud data lake called OneLake that is built-in and automatically available to every Fabric tenant. All Fabric workloads are automatically wired into OneLake, just like all Microsoft 365 applications are wired into OneDrive.

To get more info about what Fabric is, check out the MS post here. To learn more about the licensing and pricing, read on 😊

Microsoft Fabric licensing

Microsoft Fabric takes its licensing model, and some of its terminology, from Power BI Premium which means parts of this may be familiar to you.

Each organisation must have 1 x “organisational” license and at least 1 x “individual” license and each subscription is broken down into tenants, capacities, and workspaces.

Organisational licenses

These provide the infrastructure for Microsoft Fabric – effectively this is what gets things provisioned in Azure so you have something to access/work with. There are 2 types which follow the Power BI Premium pattern:

Capacity – This provisions a set of resources in Azure with different SKUS providing different amounts of capacity, cores, RAM etc.

Premium Per User – Gives per-user access to Power BI elements on Microsoft Fabric, with shared capacity only.

Capacity SKUs

SKUCapacity UnitsPAYG (Hourly)PAYG (Monthly)Power BI SKUsPower BI v-cores
F2*2$0.36$262.80N/A0.25
F4*4$0.72$525.60N/A0.5
F8*8$1.44$1,051.20EM1/A11
F16*16$2.88$2,102.40EM2/A22
F32*32$5.76$4,204.80EM3/A34
F6464$11.52$8,409.60P1/A48
F128128$23.04$16,819.20P2/A516
F256256$46.08$33,638.40P3/A632
F512512$92.16$67,276.80P4/A764
F10241024$184.32$134,553.60P5/A8128
F20482048$368.64$269,107.20N/A256
Pricing of Fabric capacity SKUs at US west 2

*SKUs smaller than F64 require all users, including those consuming content, to be licensed with a Power BI Pro license.

  • The Azure “F” SKUs are billed PAYG per second
  • The P SKUs are billed monthly/annually with a monthly commitment and support Fabric being enabled on top of the Power BI subscription.
  • The EM SKUs do not support Fabric.

Individual licenses

Free – This allows users with access to Fabric capacity to create and share Fabric content

Pro – Required to create, share, and in some cases consume, Power BI content

This appears to show a differentiation between “Fabric content” and “Power BI content” – even if the Power BI content is being created within Fabric 🤔

Pricing and costs

As well as the SKU pricing above, there will also be additional costs for OneLake storage. Again based on costs in US West, the price is:

$0.023 per GB per month

That equals $23 per TB per month ($276 annually). 500TB of data in Fabric OneLake will be $138,000 per year and I feel like that’s probably a low amount of data for many organisations.

There are also potential bandwidth costs as data is accessed and moved between regions:

Managing these resources and costs can be done through a combination of the Fabric portal and Azure Cost Management:

Furthermore, Azure Reservations (Reserved Instances) are planned for later in 2023 which will make the Fabric capacity pricing comparable to the Power BI capacity pricing.

Microsoft resources

https://learn.microsoft.com/en-us/fabric/enterprise/licenses

https://blog.fabric.microsoft.com/en-us/blog/announcing-microsoft-fabric-capacities-are-available-for-purchase