Skip to content

Commit c8e4c8c

Browse files
committed
add ASA managed resource group policy and lock guidelines
1 parent b8c8698 commit c8e4c8c

File tree

1 file changed

+5
-0
lines changed

1 file changed

+5
-0
lines changed

articles/spring-apps/basic-standard/how-to-deploy-in-azure-virtual-network.md

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -260,6 +260,11 @@ Those network resources are connected to your virtual network created in the pre
260260
> [!IMPORTANT]
261261
> The resource groups are fully managed by the Azure Spring Apps service. Do not manually delete or modify any resource inside.
262262
263+
> If your organization uses Azure Policy assignments that enforce rules on resource groups, you may need to create policy exclusions for the Azure Spring Apps managed resource groups (`ap-svc-rt_*` and `ap-app_*`). These groups are controlled by the Azure Spring Apps service, and policy restrictions might prevent the service from working properly.
264+
> Also, check if any resource locks are applied to these groups. Locks can stop the service from creating or updating resources.
265+
> You can review the Activity Log for these resource groups to find failed operations or access denied events. These issues may be caused by policy settings or resource locks.
266+
> Before deployment, contact your Azure administrator to make sure the correct policy exclusions are in place and that no resource locks are blocking normal operations.
267+
263268
## Using smaller subnet ranges
264269

265270
This table shows the maximum number of app instances Azure Spring Apps supports using smaller subnet ranges.

0 commit comments

Comments
 (0)