Skip to content

Update "Set up Virtual Network support for Power Platform" to clarify behavior/steps for Power Platform regions with single Azure regions. #2785

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
davidxw wants to merge 2 commits into
base: main
Choose a base branch
from
+2 −1
Open

Update "Set up Virtual Network support for Power Platform" to clarify behavior/steps for Power Platform regions with single Azure regions. #2785

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
d1c1da1
Update vnet-support-setup-configure.md to clarify behavior for Power …
davidxw May 28, 2025
5e808da
Merge pull request #1 from davidxw/davidxw-patch-1
davidxw May 28, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion power-platform/admin/vnet-support-setup-configure.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -59,6 +59,7 @@ The following diagram depicts the functions of the roles in the setup process fo

> [!IMPORTANT]
> - If there are two or more supported regions for the geo, such as the United States with **eastus** and **westus**, two virtual networks in ***different*** regions are required to create the enterprise policy for [business continuity and disaster recovery] or failover scenarios.
> - If there is only one supported region for the geo, such as Sweden with **swedencentral**, only one virtual network is required to create the enterprise policy.
> - Be sure that the subnet you create has been appropriately sized according to [Estimating subnet size for Power Platform environments](./vnet-support-overview.md#estimating-subnet-size-for-power-platform-environments).

You can [reuse existing virtual networks](./vnet-support-overview.md#can-i-use-an-existing-virtual-network-for-power-platform) if desired. Subnets on the other hand, [can't be reused in multiple enterprise policies](./vnet-support-overview.md#can-i-reuse-the-same-delegated-subnet-in-multiple-enterprise-policies).
Expand All @@ -78,7 +79,7 @@ The following diagram depicts the functions of the roles in the setup process fo

### Create the enterprise policy

1. Run the [CreateSubnetInjectionEnterprisePolicy.ps1 script](https://github.com/microsoft/PowerApps-Samples/tree/master/powershell/enterprisePolicies#2-create-subnet-injection-enterprise-policy), using the virtual networks and subnets you delegated. Remember two virtual networks in different regions are required for geos that support two or more regions.
1. Run the [CreateSubnetInjectionEnterprisePolicy.ps1 script](https://github.com/microsoft/PowerApps-Samples/tree/master/powershell/enterprisePolicies#2-create-subnet-injection-enterprise-policy), using the virtual networks and subnets you delegated. Remember two virtual networks in different regions are required for geos that support two or more regions. If your geo only supports one Azure region then follow the documentation provided with the script to cater for this scenario.

> [!IMPORTANT]
> If you wish to delete the virtual network or subnet, or are getting errors like `InUseSubnetCannotBeDeleted` and `SubnetMissingRequiredDelegation`, you **must delete the enterprise policy** if it exists. You can delete the enterprise policy with the following command.
Expand Down