Skip to content

Commit a4dd60b

Browse files
Update how-to-use-azure-policy.md
Fixed links to policy docs
1 parent 1c8503d commit a4dd60b

File tree

1 file changed

+7
-7
lines changed

1 file changed

+7
-7
lines changed

articles/load-testing/how-to-use-azure-policy.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ ms.topic: how-to
1212

1313
# Secure your Azure Load Testing resources with Azure Policy
1414

15-
[Azure Policy](../../governance/policy/index.yml) is a governance tool that gives users the ability to audit and manage their Azure environment at scale. Azure Policy helps you place guardrails on Azure resources to ensure they are compliant with assigned policy rules. It allows users to perform audit, real-time enforcement, and remediation of their Azure environment. The results of audits that are performed by policy are available to users in a compliance dashboard. In the compliance dashboard, you can see a drill down of the resources and components that are compliant and noncompliant. For more information, see the [Overview of the Azure Policy service](../../governance/policy/overview.md).
15+
[Azure Policy](../governance/policy/) is a governance tool that gives users the ability to audit and manage their Azure environment at scale. Azure Policy helps you place guardrails on Azure resources to ensure they are compliant with assigned policy rules. It allows users to perform audit, real-time enforcement, and remediation of their Azure environment. The results of audits that are performed by policy are available to users in a compliance dashboard. In the compliance dashboard, you can see a drill down of the resources and components that are compliant and noncompliant. For more information, see the [Overview of the Azure Policy service](../governance/policy/overview.md).
1616

1717
Example Usage Scenarios:
1818

@@ -24,15 +24,15 @@ Example Usage Scenarios:
2424

2525
When enforcing a policy, you can determine its effect over the resulting evaluation. Each policy definition allows you to choose one of multiple effects. Therefore, policy enforcement may behave differently depending on the type of operation you are evaluating. In general, the effects for policies that integrate with Azure Load Testing include:
2626

27-
- [**Audit**](../../governance/policy/concepts/effects.md#audit): when the effect of a policy is set to `Audit`, the policy doesn't cause any breaking changes to your environment. It only alerts you to Azure Load Testing resources that don't comply with the policy definitions within a specified scope, by marking these components as noncompliant in the policy compliance dashboard. Audit is default if no policy effect is selected.
27+
- [**Audit**](../governance/policy/concepts/effects.md#audit): when the effect of a policy is set to `Audit`, the policy doesn't cause any breaking changes to your environment. It only alerts you to Azure Load Testing resources that don't comply with the policy definitions within a specified scope, by marking these components as noncompliant in the policy compliance dashboard. Audit is default if no policy effect is selected.
2828

29-
- [**Deny**](../../governance/policy/concepts/effects.md#deny): when the effect of a policy is set to `Deny`, the policy blocks the creation of a new resource or new test runs that don't comply with the policy definition. Existing noncompliant test runs are not affected. The 'audit' capabilities continue to operate.
29+
- [**Deny**](../governance/policy/concepts/effects.md#deny): when the effect of a policy is set to `Deny`, the policy blocks the creation of a new resource or new test runs that don't comply with the policy definition. Existing noncompliant test runs are not affected. The 'audit' capabilities continue to operate.
3030

31-
- [**Disabled**](../../governance/policy/concepts/effects.md#disabled): when the effect of a policy is set to `Disabled`, the policy gets evaluated but enforcement doesn't take effect, thus being compliant for the condition with `Disabled` effect. This effect is useful to disable the policy for a specific condition as opposed to all conditions.
31+
- [**Disabled**](../governance/policy/concepts/effects.md#disabled): when the effect of a policy is set to `Disabled`, the policy gets evaluated but enforcement doesn't take effect, thus being compliant for the condition with `Disabled` effect. This effect is useful to disable the policy for a specific condition as opposed to all conditions.
3232

3333
## Available Built-In Policy Definitions
3434

35-
Predetermined policies, referred to as 'built-ins', facilitate governance over your load testing resources so you don't have to write custom policies in JSON format to enforce commonly used rules associated with best security practices. Even though built-ins are predetermined, certain policies require you to define parameters. For example, by defining the effect of the policy, you can audit the load testing resource before enforcing a deny operation to prevent outages. See [built-in policies for Azure Load Testing](../../governance/policy/samples/built-in-policies#azure-load-testing) to view the current built-in policies available for Azure Load Testing.
35+
Predetermined policies, referred to as 'built-ins', facilitate governance over your load testing resources so you don't have to write custom policies in JSON format to enforce commonly used rules associated with best security practices. Even though built-ins are predetermined, certain policies require you to define parameters. For example, by defining the effect of the policy, you can audit the load testing resource before enforcing a deny operation to prevent outages. See [built-in policies for Azure Load Testing](../governance/policy/samples/built-in-policies#azure-load-testing) to view the current built-in policies available for Azure Load Testing.
3636

3737
## Enabling and managing a load testing policy through the Azure portal
3838

@@ -85,5 +85,5 @@ If the compliance results show up as "Not Started" it may be due to the followin
8585

8686
## Next Steps
8787

88-
- Learn more about the [Azure Policy service](../../governance/policy/overview.md)
89-
- See Key Vault samples: [Azure Load Testing built-in policy definitions](../../governance/policy/samples/built-in-policies.md#azure-load-testing)
88+
- Learn more about the [Azure Policy service](../governance/policy/overview.md)
89+
- See Key Vault samples: [Azure Load Testing built-in policy definitions](../governance/policy/samples/built-in-policies.md#azure-load-testing)

0 commit comments

Comments
 (0)