observed resultHigh confidenceCurrent
The strongest current portability story is that a previously unprepared Microsoft tenant became a working Dataheart sandbox, not that a vendor-neutral runtime has been proven.
Infrastructure, identity, SQL, Fabric and reports could be deployed and read back. The same central person still carried both history and execution, while parts of the M365 and report chain remained manual or blocked.
Valid from2026-08-24
Last reviewed2026-08-24
Review again2026-09-23
Dataheart stanceconstrained
Evidence for
Resource manifest, preflight and managed-runtime verification show deployed and verified sandbox resources.
Dataheart repository, deployment receipts and implementation artifacts · Kugghuset AB ↗Evidence against
M365 publication returned 403, Graph publication requires delegated permission and a complete restore chain is absent.
Dataheart repository, deployment receipts and implementation artifacts · Kugghuset AB ↗Publish a Teams app to the Microsoft Teams app catalog · Microsoft ↗How this claim can fall
Supersede the claim when another installation provides stronger evidence through an independent team, clean environment, complete restore, external delivery and continued development.
A published claim remains useful only while it remains possible to prove it wrong.