Skip to content

Commit 84ea793

Browse files
committed
links
1 parent db2cb76 commit 84ea793

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/ai-studio/how-to/azure-policy.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -70,7 +70,7 @@ To configure this policy, set the effect parameter to __Audit__, __Deny__, or __
7070

7171
### Compute instances should be recreated to get software updates
7272

73-
Controls whether compute instances should be audited to make sure they're running the latest available software updates. This policy is useful to ensure that compute instances are running the latest software updates to maintain security and performance. For more information, see [Vulnerability management](vulnerability-management.md#compute-instance).
73+
Controls whether compute instances should be audited to make sure they're running the latest available software updates. This policy is useful to ensure that compute instances are running the latest software updates to maintain security and performance. For more information, see [Vulnerability management](../concepts/vulnerability-management.md#compute-instance).
7474

7575
To configure this policy, set the effect parameter to __Audit__ or __Disabled__. If set to __Audit__, a warning event is created in the activity log when a compute isn't running the latest software updates.
7676

@@ -90,7 +90,7 @@ If the policy is set to __Deny__, then you can't create a compute unless SSH is
9090

9191
### Hubs should be encrypted with customer-managed key
9292

93-
Controls whether a hub and its projects should be encrypted with a customer-managed key, or with a Microsoft-managed key to encrypt metrics and metadata. For more information on using customer-managed key, see the [Customer-managed keys](encryption-keys-portal.md) article.
93+
Controls whether a hub and its projects should be encrypted with a customer-managed key, or with a Microsoft-managed key to encrypt metrics and metadata. For more information on using customer-managed key, see the [Customer-managed keys](../concepts/encryption-keys-portal.md) article.
9494

9595
To configure this policy, set the effect parameter to __Audit__ or __Deny__. If set to __Audit__, you can create a hub without a customer-managed key and a warning event is created in the activity log.
9696

0 commit comments

Comments
 (0)