System requirements, limits, and configuration values for Power Apps
This article contains information on supported device platforms, web browser requirements, limits, and configuration values for Power Apps.
Platform | Version |
---|---|
iOS | The latest version of iOS is always the recommended version to run Power Apps mobile. The previous version is the minimum required. |
Android | The latest version of Android is always the recommended version to run Power Apps mobile. The previous three versions are the minimum required to run Power Apps mobile. |
Windows | Windows 10 version 17763.0 or later to run Power Apps for Windows. |
Note
New major versions of iOS and Android are released each year. When a new version is released, if you're using the oldest previously supported version, you'll have 60 days to update your device to at least the new minimum supported version to continue to run Power Apps mobile.
Browser | Supported versions | App type |
---|---|---|
Google Chrome | Latest three major releases | Model-driven apps, canvas apps, app and component designers1. |
Microsoft Edge | Latest three major releases | Model-driven apps, canvas apps, app and component designers1. |
Mozilla Firefox | Latest three major releases | Model-driven apps and canvas apps. |
Apple Safari | 13 and later | Model-driven apps and canvas apps. |
1App and component designers include Power Apps studio, model-driven app designer, and model-driven custom page designer.
Operating system | Supported versions | App type |
---|---|---|
Windows | Windows 10 or later | Model-driven apps, canvas apps, app and component designers1. |
macOS | 10.13 or later | Model-driven apps, canvas apps, app and component designers1. |
iOS | iOS 13 or later | Model-driven apps2 and canvas apps. |
Android | 10 or later | Model-driven apps2 and canvas apps. |
1App and component designers include Power Apps studio, model-driven app designer, and model-driven custom page designer.
2Using the web browser on a phone to run a model-driven app isn't supported; use the Power Apps mobile app.
For classic web application system requirements, go to Web application requirements.
Note
Canvas apps running on Windows platform must use the legacy Microsoft Dataverse connector. A warning is displayed for apps that still use the legacy connector, but using it for Windows platform is supported.
These limits apply to each single outgoing request:
Name | Limit |
---|---|
Timeout | 180 Seconds |
Retry attempts | 4 |
Note
The retry value may vary. For certain error conditions, it's not necessary to retry.
Requests from Power Apps use IP addresses that depend on the region of the environment that the app is in. We don't publish fully qualified domain names available for Power Apps scenarios.
Calls made from an API connected through an app (for example, the SQL API or the SharePoint API) come from these IP addresses.
This list identifies all services to which Power Apps communicates and their usages. Your network must not block these services.
Domain(s) | Protocols | Uses |
---|---|---|
api.bap.microsoft.com *.api.bap.microsoft.com |
https | Environment permissions management |
management.azure.com | https | Power Apps Management Service |
msmanaged-na.azure-apim.net | https | Runtime of Connectors/Apis |
login.microsoft.com login.windows.net login.microsoftonline.com secure.aadcdn.microsoftonline-p.com *.odc.officeapps.live.com |
https | Microsoft Authentication Library |
graph.microsoft.com graph.windows.net |
https | Azure Graph - For getting user info (for example, profile photo) |
*.azure-apim.net | https | API Hubs - Different subdomains for each locale |
*.azure-apihub.net | https | API Hubs - Different subdomains for each locale |
*.powerapps.com | https | create.powerapps.com, content.powerapps.com, apps.powerapps.com, make.powerapps.com, *gateway.prod.island.powerapps.com, and *gateway.prod.cm.powerapps.com |
*.azureedge.net | https | create.powerapps.com, content.powerapps.com, and make.powerapps.com (Optional) We highly recommend that you use the wildcard listed under Domain(s). You can download the complete list if you want to allow specific domain names instead of using *.azureedge.net. However, this list is subject to change. |
*.ces.microsoftcloud.com | https | Access to net promoter score (NPS) and surveys. |
*.blob.core.windows.net | https | Blob storage (Optional) We highly recommend that you use the wildcard listed under Domain(s). You can download the complete list if you want to allow specific domain names instead of using *.blob.core.windows.net. However, this list is subject to change. |
*.flow.microsoft.com *.powerautomate.com |
https | create.powerapps.com, content.powerapps.com, and make.powerapps.com |
http://*.crm#.dynamics.com and https://*.crm#.dynamics.com | https | Required for environments access. Includes integration and static Content Delivery Network (CDN) content endpoints. Replace # in http://*.crm#.dynamics.com and https://*.crm#.dynamics.com with your region's number:
|
eu-mobile.events.data.microsoft.com/Collector/3.0 | https | European region telemetry endpoint for model-driven apps |
browser.pipe.aria.microsoft.com | https | Rest of the World telemetry endpoint for model-driven apps |
localhost | http | Power Apps Mobile |
127.0.0.1 | http You might need to explicitly list the port (5040 and up) for localhost/127.0.0.1. |
Power Apps Mobile |
ecs.office.com | https | Retrieve feature flags for Power Apps |
augloop.office.com *.augloop.office.com |
WSS | Power Apps Studio Copilot |
config.edge.skype.com | https | Retrieve feature flags for Power Apps (backup) |
api.powerplatform.com *.powerplatform.com *.api.powerplatformusercontent.com |
https | Required for Power Platform API connectivity used internally by Microsoft products, and Power Platform programmability and extensibility. |
*.sharepointonline.com | https | Retrieve assets for presenting the header that appears at the top of app playing experiences |
ris.api.iris.microsoft.com eudb.ris.api.iris.microsoft.com |
https | Record user action in response to Power Apps in-app campaigns |
arc.msn.com arc-emea.msn.com |
https | Record user viewing of Power Apps in-app campaigns |
*.hubblecontent.osi.office.net hubble.officeapps.live.com res.cdn.office.net |
https | Provides stock images to use in your app |
dc.services.visualstudio.com | https | Application Insights endpoint used for custom telemetry in canvas app |
js.monitor.azure.com | https | This is used by the office header for reporting telemetry |
1 Replaces domain name gov.content.powerapps.us
used before July 2022.
2 Replaces domain name high.content.powerapps.us
used before July 2022.
3 Replaces domain name content.appsplatform.us
used before July 2022.
Important
- If you're using a VPN, it must be configured to exclude localhost from tunneling for Power Apps Mobile.
- If you are a US Government customer or a customer in China, there are additional service URLs that must be unblocked. More information:
US Government: Power Apps US Government service URLs, Power Automate US Government service URLs
China: Power Platform and Dynamics 365 apps - operated by 21Vianet in China.
This section lists endpoints that we no longer support. Instead, use the new endpoints listed below. We recommend updating any bookmarks you might have that use the deprecated endpoint to the new endpoint.
Deprecated endpoint | New endpoint |
---|---|
web.powerapps.com/apps/{yourAppGuid} | apps.powerapps.com/play/{yourAppGuid} |
web.powerapps.com/apps/{yourAppGuid}/open | apps.powerapps.com/play/{yourAppGuid} |
Power Apps doesn't support the nested embedding of canvas apps in native desktop, mobile, or other non-browser clients.
The following table shows some of the examples where embedding a canvas app is and isn't supported:
Power Apps embedding scenario | Supported clients | Unsupported clients |
---|---|---|
A canvas app embedded in a SharePoint page. | Web, for example, Sharepoint.com |
|
A canvas app embedded in a SharePoint page that is added as a tab in a Microsoft Teams channel. | Web, for example.
|
|
A canvas app used as a custom form in the SharePoint page. | Web, for example, Sharepoint.com |
|
A canvas app used as a custom form in the SharePoint page that is added to a Teams team. | Web, for example.
|
|
A Power BI report that is added to Teams, or a SharePoint site. | Web, for example, Teams.microsoft.com |
|
A canvas app is embedded in a third party client. | Third party websites in a browser | Third party native applications |
A canvas app in Unified Service Desk | None | Unified Service Desk Desktop app |
Power Apps doesn't support embedding a model-driven app or page within an IFrame in another application.
Power Apps doesn't support running with a proxy enabled. This can cause unpredictable behavior. If you encounter issues, disable the proxy and then try again.
- Some proxies (such as Zscaler, Blue Coat) modify Power Apps requests by removing headers (CORS or authentication headers). Power Apps relies on these headers to load the app.
- Some proxies (such as Microsoft Defender for Cloud Apps, McAfee) might intercept and change the URL of an app or embedded app. For example, if there's a Dynamics 365 app that is running under domain org.crm.dynamics.com or a canvas app that is running under domain apps.powerapps.com, the platform doesn't support a proxy that changes these domains to a custom domain such as mycustomdomain.com. This can cause unpredictable behavior when the platform tries to retrieve tokens that are necessary to run the app.
For canvas app data type limits, you can find information about size limits on text, hyperlinks, images, and media in Data types in Power Apps.
For Microsoft Dataverse data type size limits, you can find information on column types, such as text and image columns, in Types of columns.
Information is now available in the Power Apps per app plan section in the Power Platform admin guide.
System requirements, limits, and configuration values for Power Pages