Effective October 12, 2022, Power Apps portals is Power Pages. More information: Microsoft Power Pages is now generally available (blog)
We will soon migrate and merge the Power Apps portals documentation with Power Pages documentation.
This topic provides resources where you can learn about the new features that have been recently released and features that will be releasing over the next few months.
Portals release plans
For information about the roadmap and new features releasing over the next few months, see:
- 2022 release wave 1 plan
- 2021 release wave 2 plan
- 2021 release wave 1 plan
- 2020 release wave 2 plan
- 2020 release wave 1 plan
Portals version updates
The following articles provide details about the portals version updates:
- Power Apps portals version 9.3.7.x and later
- Power Apps portals version 9.3.6.x
- Power Apps portals version 9.3.4.x
- Power Apps portals version 9.3.3.x
- Power Apps portals versions before 9.3.3.x
Starter portal package updates
The following articles provide details about the starter portal package updates:
- Starter portal package version 9.3.2209.x
- Starter portal package version 9.3.2204.x
- Starter portal package version 9.3.2109.x
- Starter portal package version 9.2.2108.x
- Starter portal package version 9.2.2103.x
- Starter portal package version 9.2.2006.10
- Starter portal package version 9.2.2005.0
- Starter portal package version 9.2.2003.2
- Starter portal package version 220.127.116.11
By enabling the portal capabilities for Dynamics 365, Dynamics 365 data, such as customer name, product name, case number, or any custom entity data, can be exposed through an external-facing Dynamics 365 portal. Any data exposed through the portal is stored in memory in Microsoft Azure Web Apps for caching and also as files on the local hard drive to enable portal search functionality.
A tenant administrator enables Dynamics 365 portals by configuring it through the Power Platform admin center, which also installs a package (with solutions and data) in the selected Dynamics 365 instance. A tenant administrator or a Dynamics 365 user set up as a Portal Administrator can then specify the data that will be exposed through the portal. To subsequently disable the portal capabilities, a tenant administrator can cancel the Portal Add-on subscription with Office 365.
Important Azure components and services that are involved with the portal capabilities are:
- Azure Web Apps: Azure Web Apps are used to host the portal in Azure.
- Azure Traffic Manager: Azure Traffic Manager is used to ensure the high availability of the service by routing the user to the Web Apps that are up and running.
- Azure Service Bus: Azure Service Bus (Topics/Subscriptions) is used for cache invalidation of the portals. Azure Service Bus temporarily stores the messages, which are triggered when any portal-related record is changed in Dynamics 365, and are passed along to Web Apps to do the cache invalidation.
- Azure Key Vault: All services store configuration data in Azure Key Vault.
- Azure Storage: Data related to the organization, tenant, and portal is stored in Azure Storage.
- Azure Active Directory: All the web services use Azure Active Directory to authenticate.
For more information about additional Azure service offerings, see the Microsoft Azure Trust Center.
Submit and view feedback for