Skip to content

Commit 0523898

Browse files
authored
Update articles/spring-apps/basic-standard/how-to-deploy-in-azure-virtual-network.md
1 parent c8e4c8c commit 0523898

File tree

1 file changed

+6
-3
lines changed

1 file changed

+6
-3
lines changed

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

Lines changed: 6 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -259,10 +259,13 @@ Those network resources are connected to your virtual network created in the pre
259259

260260
> [!IMPORTANT]
261261
> The resource groups are fully managed by the Azure Spring Apps service. Do not manually delete or modify any resource inside.
262-
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.
262+
>
263+
> If your organization uses Azure Policy assignments that enforce rules on resource groups, you might need to create policy exclusions for the Azure Spring Apps managed resource groups - `ap-svc-rt_*` and `ap-app_*`. The Azure Spring Apps service controls these groups, and policy restrictions might prevent the service from working properly.
264+
>
264265
> 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+
>
267+
> You can review the Activity Log for these resource groups to find failed operations or access denied events. These issues might be caused by policy settings or resource locks.
268+
>
266269
> 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.
267270
268271
## Using smaller subnet ranges

0 commit comments

Comments
 (0)