Microsoft Donnacona: A finished building still needs accepted power
FJI qualification held or pending: the full four-document gate, including project-specific government evidence, has not yet been accepted. Qualification evidence and decisions →
Project status: Building completed November 2025; electrical works targeted for second half 2026. Capacity scope: IT MW and usable electrical load undisclosed. How we verify evidence.
← Back to project indexCompare this project → · Track its catalysts → · Evidence guide →
- Location
- Donnacona / Portneuf, Quebec — representative locality pin
- Readiness
- Under construction
- Status
- Building completed November 2025; electrical works targeted for second half 2026
- Confirmed companies
- Microsoft
- Next milestone
- Substation completion and energized facilities followed by productive cloud service
- Reviewed
- October 6, 2026
Expanded analysis · Original disclosures linked below · CAD and USD preserved as labeled · Company statements attributed; interpretations labeled.
The one-minute investment takeaway
Our analysis: A finished building still needs accepted power. Donnacona illustrates why the atlas distinguishes physical completion from useful cloud capacity. Its dated electrical schedule gives investors a concrete delivery test without inventing a campus operating date.
Readiness basis: Classification of evidence in the reviewed profile; strongest documented phase, not full-campus completion. Building completed November 2025; electrical works targeted for second half 2026 Readiness source →
What the sources establish
- Building stage. Microsoft’s April 2026 update says the data center building was completed in November 2025, with work continuing inside. Primary source →
- Electrical schedule. Substation construction and a sound wall were expected in the second half of 2026. This is an electrical-works target, not confirmation that computing is operational. Primary source →
Who receives the money?
Our analysis of disclosed roles. Revenue routes are business-model interpretations, not estimates of booked project revenue.
| Company / exposure | Economic role | What investors need to establish |
|---|---|---|
| Microsoft | Owner or operator of the disclosed infrastructure | Accepted useful capacity and net contribution after resource and renewal costs. |
| Named service and construction participants | Contract-specific delivery and recurring service roles | Actual contract, tariff or purchase terms; participation is not booked profit. |
| Equipment suppliers not established here | Potential procurement and renewal spending | Named awarded orders before attributing public-company project revenue. |
How financially meaningful is it?
Our analysis: The economics depend on the sequence of usable power, cooling acceptance, server installation and customer workload deployment. Spending on an apparently completed structure can remain unproductive while the substation is unfinished. Conversely, staged energization could permit some productive deployment before an entire development program is complete; that possibility needs evidence rather than assumption. Microsoft earns through cloud and product contribution, not independent landlord rent. A local project should therefore be assessed against useful computing output and renewal spending, with corporate Azure growth providing context rather than a site revenue allocation. Substation costs, commissioning obligations and the division of utility versus customer assets matter to both timing and invested capital.
Computing contribution equals customer or product benefit minus power, network, facility operation, financing and equipment renewal. Model long-lived buildings separately from shorter-lived computing assets.
Hypothetical illustration: 10 MW steady IT load at 1.2 PUE uses 105,120 MWh annually. A USD 10/MWh tariff increase adds USD 1.0512 million annual cost. Neither load, PUE nor tariff is disclosed here; this is a sensitivity example, not a site forecast.
Milestones that would change the assessment
| Milestone | Evidence to watch |
|---|---|
| Scope and capital | Reconcile campus and portfolio figures, accepted versus potential capacity, and property versus equipment funding. |
| Electrical and cooling acceptance | Substation completion and energized facilities followed by productive cloud service. Equipment delivery, construction completion and commissioning are separate steps. |
| Commercial productivity | Useful workloads or billable customer capacity, with operating costs and renewal obligations included. |
| Counterparty attribution | Named binding service and procurement terms before estimating participant earnings. |
What could break the investment case?
Our analysis: Electrical works, internal fit-out and workload deployment can have different completion dates. Sound mitigation and construction conditions may affect the sequence. No accepted operating load is disclosed.
What would change our view?
Our analysis: Dated acceptance, disciplined incremental capital and useful output at competitive resource cost would strengthen our assessment. Idle equipment, repeated delivery slippage or capital and renewal spending ahead of economic benefits would weaken it. We change the stage only on project-specific evidence, and would improve public-company financial attribution only with contract scope and cash-flow detail. A larger headline by itself would not justify a stronger return conclusion.
What remains unknown
Current accepted IT and facility MW, workload mix, utilization, site-attributable income, contract prices, tariffs, hardware renewal schedule and phase-specific capital allocation remain unestablished in the reviewed sources unless explicitly disclosed above. Targets remain expectations until confirmed. The map pin represents the locality rather than a verified individual building. Supplier, fund and corporate exposures must be modeled separately.
Project research for information, not a buy recommendation. Financial illustrations use assumptions, not disclosed site results or management guidance.
Company investor information & quarterly statements
Microsoft
Named developer/operator of this data center in operator construction/operation disclosure
Official investor & shareholder information · Quarterly financial statements: FY2026 Q4, quarter ended June 30, 2026
Corporate disclosures provide company-wide context. They do not establish this project’s revenue, spending, profit, ownership share or operating capacity. Disclosure verification records →