Can Power Apps Run on a Desktop? Browser, Windows App and Offline Limits

Yes. A Power Apps user can run canvas and model-driven apps on a desktop in a supported web browser. Windows users can also install Power Apps for Windows from Microsoft Store.

The important correction is on macOS: Power Apps runs in a supported browser, but Microsoft does not document a Power Apps for Mac desktop client. The old version of this article said the client was available for Windows and Mac. That was wrong.

Desktop use also does not make an app automatically faster, offline-capable or accessible. Those outcomes depend on the app, data source, network, device and design.

The short answer

What you need	Best starting route	Important limit
Run an app on Windows or macOS	Open its web link in a supported browser	Browser apps require a connection; they do not run offline
A native player on Windows	Install Power Apps for Windows	Windows only; installation and WebView2 may need administrator help
A Mac desktop experience	Use Safari, Edge, Chrome or Firefox within Microsoft's current support matrix	There is no Microsoft-documented Power Apps for Mac client
Open the app from Teams	Add the shared canvas app as a Teams personal app or tab	Teams policy, app sharing and data permissions still apply
Open the app from SharePoint	Add the Power Apps web part to a modern SharePoint Online page	Embedding does not grant access to the app or its data
Work without a network	Design the app for offline use and run it in a native Power Apps player	Microsoft says canvas apps in web browsers cannot run offline

If you only need to use an app at a desk, start with the browser. It is the simplest route to distribute and support.

Choose the Windows client when you have a real reason: native-player/offline requirements, a managed-device design, or a tested user experience that works better there.

Run a Power App in a desktop browser

Microsoft supports canvas and model-driven apps in current versions of major desktop browsers. Its current Power Apps system requirements list:

• the latest three major releases of Microsoft Edge and Google Chrome;
• the latest three major releases of Mozilla Firefox for running apps;
• Safari 13 or later for running apps;
• Windows 10 or later and macOS 10.13 or later as supported desktop operating systems for browser use.

Those are platform requirements, not a promise that an old app will behave well on every display. Microsoft explicitly tells organisations to test the devices intended for production.

Give users the app link

The maker or owner should:

1. Save and publish the app.
2. Share it with the intended users or Microsoft Entra security group.
3. Give the same people the required access to its data sources, flows and other dependent resources.
4. Copy the app's Web link from its details page.
5. Send that link through the governed route your organisation uses, or make the app discoverable from the Microsoft 365 apps page.

The user opens the link, signs in and runs the app. Microsoft's browser instructions also note that the user may be asked to authorise a data connection or a device capability such as the camera or location.

That distinction matters. An app link proves where the app is; it does not prove the person can read or write the underlying SharePoint list, Dataverse table, SQL database or flow.

Use Power Apps for Windows

Microsoft provides a Windows client for canvas and model-driven apps.

To install it:

1. Open Microsoft Store on the Windows device.
2. Find Power Apps and install it.
3. Open the client and sign in with the work account that has access to the app.
4. Select the required app from the list.
5. Test the business task, not just the home screen.

Microsoft's installation page says Power Apps for Windows can require a current WebView2 Runtime. Installing or repairing WebView2 can require administrator rights, so this may need packaging by endpoint management rather than a note telling every employee to visit the Store.

The Windows client is not a magic performance switch. Microsoft's system guidance says results vary with processing power, memory, network connectivity, app complexity and other workloads on the device. Measure the actual save, search and navigation paths on representative hardware.

Can Power Apps run on a Mac?

Yes—in a supported web browser.

Open the app's web link in a supported Safari, Edge, Chrome or Firefox release and sign in. Makers can also use the browser-based Power Apps Studio on supported macOS/browser combinations.

Do not tell Mac users to download a Power Apps for Mac client. Microsoft's current client documentation is specifically Power Apps for Windows. If a future Mac client appears, it should be confirmed from Microsoft's current product documentation before the advice changes.

Can a desktop Power App work offline?

Not in the browser.

Microsoft's offline canvas-app guidance is explicit: offline capability is available in the native Power Apps players on iOS, Android and Windows, while canvas apps running in a web browser cannot run offline.

Offline is also something the maker designs; it is not obtained by installing the Windows player.

For a Dataverse-based canvas app, Power Apps has an offline-first capability with data profiles and synchronisation. For other connectors, Microsoft documents LoadData and SaveData as a basic local-storage mechanism with limits. Neither route should be switched on minutes before a field rollout.

An offline acceptance test should cover:

• the first data download;
• opening the app with no connection;
• creating and editing records offline;
• reconnecting and synchronising;
• conflict behaviour when another person changed the same record;
• error visibility and recovery;
• lost, replaced or shared devices.

If offline work is central to the job, make it a design requirement at the start. Retrofitting it after the app already assumes constant SharePoint, SQL or Dataverse access is a different project.

Add a Power App to Microsoft Teams

A canvas app can appear in Teams as a personal app or as a tab.

Microsoft's Teams embedding guidance says custom-app policies and the organisation's Shared Power Apps setting can affect whether the app can be added. The app must belong to the same tenant as the Teams account for that route.

For a channel tab:

1. Publish and share the canvas app.
2. Share its data and dependent resources.
3. In Teams, open the intended team and channel.
4. Add a tab and select the Power Apps option available in your tenant.
5. Select the app and save the tab.
6. Test with a normal team member, not only the maker.

Microsoft's tab guidance says the maker must share their own app before adding it. It also documents platform limitations for some sensors and media.

The tab is a convenient doorway. It does not make every member a Power Apps user, grant SharePoint permissions or turn concurrent app use into live co-authoring of the same record.

Add a Power App to a SharePoint page

SharePoint Online has a Power Apps web part for canvas apps.

The basic route is:

1. Edit the modern SharePoint page.
2. Add the Power Apps web part.
3. Enter or select the published canvas app's web link or app ID, as the web part requests.
4. Republish the SharePoint page.
5. Test with a reader who has the page, app and data permissions expected for the role.

Microsoft confirms that users can run a canvas app from a SharePoint page. The web part only hosts the player. It does not inherit the SharePoint page's audience as the app's security model.

If the goal is to replace the New/Edit/View experience of one SharePoint list, a customised SharePoint form is a different feature. Use the web part for a standalone canvas app embedded in a page; use list-form integration for the list's own form lifecycle.

Design an app that works at a desk

An app can be technically available on a desktop and still be miserable to use.

Make the layout responsive

Desktop screens range from a small laptop split beside Outlook to an ultrawide display at 150% scaling. Use responsive containers and test the widths people actually use.

If your screens are currently built from fixed X/Y coordinates, our guide to consistent interfaces across Power Apps screens gives you the maintainable pattern. The aim is not to stretch every control to fill a monitor; it is to keep reading width, navigation and actions predictable.

Support keyboard users

Test the complete task without a mouse. Tab order should be logical, focus visible, buttons named clearly and Enter/Escape behaviour deliberate.

Use Power Apps Accessibility Checker, but do not treat a clean checker result as a complete accessibility test. Microsoft's canvas-app accessibility guidance also calls for keyboard and screen-reader testing.

Avoid device assumptions

A barcode scanner, GPS location, camera, pen input and file picker can differ across browser, Teams and native player. Where a capability matters, use a supported signal or control and test that host.

Give users a manual fallback for an essential task. A warehouse app that cannot continue when one scanner API is unavailable is not robust merely because its home screen loads on Windows.

Permissions checklist when an app opens but does not work

If the app opens and then reports missing data, failed connections or disabled actions, check these separately:

1. App access: Is the person a user of the published app?
2. Environment access: Can the person reach the environment and any required Dataverse app/table roles?
3. Data access: Does the person have the right SharePoint, Dataverse, SQL or other source permissions?
4. Connections: Is the app using an end-user connection, an explicitly shared connection or a flow-owned connection as designed?
5. Flows: Has every app-triggered flow been shared/configured for run-only users correctly?
6. Gateway: If an on-premises gateway is involved, is the data source and user/connection mapping valid?
7. Policy: Does a Teams app policy, Power Platform data policy or Conditional Access rule block the route?
8. Licence: Does the user have the licence required by the app's actual connectors and features?

Do not troubleshoot all eight by repeatedly republishing the app. Establish which boundary failed first.

Desktop acceptance test

Before rolling out, use at least one standard user account and run this checklist:

• open the direct browser link on a managed Windows device;
• open it on macOS if Mac users are in scope;
• open it through Teams or SharePoint if those routes will be advertised;
• create, find, edit and save a real test record;
• upload/download a file if the app supports files;
• test at normal and increased browser zoom;
• use the task with keyboard only;
• remove one data permission and confirm the error is understandable;
• test the supported native Windows player if offline or device features matter;
• record browser/client versions, connection identity and the date tested.

For errors that only appear at runtime, open Live monitor and trace the failing session. “It works for the maker” is not production evidence.

Frequently asked questions

Can Power Apps run on Windows 11?

Yes. Use a supported desktop browser or install Power Apps for Windows. Test the app and its connectors on your managed Windows build before a wide rollout.

Is there a Power Apps desktop app for Mac?

Microsoft documents a Power Apps for Windows client, not a Power Apps for Mac client. Mac users can run canvas and model-driven apps in supported desktop browsers.

Can I put a Power App shortcut on the desktop?

Yes. The simplest supported route is to bookmark or distribute the app's web link and let the browser/operating system create a shortcut. The user still needs app, data and licence access.

Will a Power App work offline in Chrome or Edge?

No. Microsoft says canvas apps in web browsers cannot run offline. Offline scenarios use a deliberately configured app in a native Power Apps player on iOS, Android or Windows.

Does adding a Power App to Teams or SharePoint give users permission?

No. Embedding supplies a launch surface. The app and its data sources, flows, gateways and connections still need the appropriate access.

Make the desktop route boring

For most desk-based users, the good design is unremarkable: a published web link, a supported browser, responsive screens, correctly shared data and a test account that proves the whole task.

Use Power Apps for Windows when the native player solves a specific requirement. Use Teams or SharePoint when they are where the work already starts. Keep offline, permissions and device capabilities visible as separate design decisions.

If you are building the app rather than merely opening it, join the Power Apps Builders Space. Bring the screen, data source and device you need to support; the useful answer depends on all three.

How this article was checked

This rewrite was checked on 14 August 2026 against current Microsoft documentation for Power Apps system requirements, Power Apps for Windows, browser launch, offline canvas apps, Teams embedding and the SharePoint web part.