A field technician I shadowed on a project once put it perfectly: “The app works great in the parking lot and dies in the basement — and all my work is in the basement.” If you build canvas apps for people who work in basements, warehouses, rural routes, or anywhere else connectivity goes to die, the offline story in Power Apps has quietly become very good — and 2026 release wave 1 fills in the piece that was missing. Here is the current state of it, and how to set it up.
Offline-First, in One Paragraph
Built-in Dataverse offline for canvas apps flips the traditional model. Instead of the app calling the server for every read and write and failing when the network does, the app works against a local copy of the data on the device — iOS, Android, or Windows — and Power Apps synchronizes local and server-side changes in the background whenever a network is available. Your formulas do not change: the same Power Fx you already write reads and writes the local store transparently. The pleasant side effect is speed — reading from the device is faster than any mobile network even on a good day, so well-built offline-first apps feel snappier online too.
Step 1 — Enable It
The app must live in a solution — that is a hard requirement. From there, open the app in Power Apps Studio, go to Settings > General, and switch on Can be used offline. On first launch the app downloads the data it needs to the device, and from then on it runs against the local store.
Step 2 — Choose Your Offline Profile
For simple apps, Power Apps auto-generates an offline profile — it works out which tables and columns the app touches and caches them. For anything substantial, build a custom profile and think in terms of the technician’s day: which records does this user actually need in the next eight hours? “My work orders, my customers, open items only” makes for a fast first sync; “all rows in all tables” makes for a support ticket. Wave 1 2026 adds advanced offline profiles with FetchXML, which finally gives makers fine-grained, query-based control over exactly what lands on the device.
For files and images, you choose between on-view download (fetch when the user opens the content) and on-sync (fetch everything during synchronization). On-sync makes the content available in the basement; on-view keeps the sync small. Pick per column, based on whether the content is nice-to-have or the actual job.
Step 3 — The New Part: Real-Time Access When You Are Online
The historical trade-off of offline-first was staleness: everything went through the local cache, even when the device had perfect connectivity and the user needed the live number — current stock, latest price, the case another team updated five minutes ago. The headline mobile improvement in 2026 release wave 1 is real-time Dataverse access in online mode: offline-first canvas apps can now read live server data when connected, while keeping the cached store for when they are not. That combination — local speed by default, live truth on demand — is the design that field service vendors have been hand-rolling for years, now built in.
Wave 1 also brings push notifications for custom-branded and white-labeled apps, which closes another gap for organizations shipping branded field apps to large workforces.
⚠️ Important: offline works with Dataverse only. Connector-based sources like SharePoint are not supported in the offline story. If your app’s critical data lives in SharePoint lists, the honest fix is not a workaround — it is migrating that data into Dataverse tables. Every project I have seen attempt the workaround route ended up doing the migration anyway, a year later and grumpier.
Testing Like You Mean It
Airplane mode in the office is a start, but it is not the real world. Test the ugly middle states: one bar of signal, network dropping mid-save, two users editing the same record on different sides of a dead zone. Watch what sync does in each case and make sure your users can tell, from the app itself, whether their changes have made it to the server. Most “offline bugs” I get called about are actually user-trust bugs — the data synced fine, but nothing told the technician it had.
Closing Thoughts
Connectivity is a spectrum, and your users live on all of it — sometimes in the same hour. Offline-first with real-time online access means you no longer choose between an app that survives the basement and an app that shows the live truth in the office. Enable it deliberately, profile the data around the working day, test the messy middle, and the parking-lot-versus-basement conversation disappears from your support queue.
