Skip to content

Commit 360af5b

Browse files
Updated docs to boost score
1 parent ee6db98 commit 360af5b

File tree

2 files changed

+17
-18
lines changed

2 files changed

+17
-18
lines changed

articles/managed-applications/concepts-custom-providers-built-in-policy.md

Lines changed: 9 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: Deploy associations for a custom provider using policy
2+
title: Deploy associations for Azure Custom Provider using policy
33
description: Learn about deploying associations for a custom provider using Azure Policy service.
44
author: msHich
55
ms.service: managed-applications
@@ -14,23 +14,22 @@ Azure policies can be used to deploy associations to associate resources to a cu
1414

1515
## Built-in policy to deploy associations
1616

17-
Deploy associations for a custom provider is a built-in policy that can be used to deploy association to associate a resource to a custom provider. The policy accepts three paramaters:
17+
Deploy associations for a custom provider is a built-in policy that can be used to deploy association to associate a resource to a custom provider. The policy accepts three parameters:
1818

19-
- Custom provider Id - This is the resource Id of the custom provider to which the resources need to be associated.
20-
- Resource types to associate - These are the list of resource types to be associated to the custom provider. You can associate multiple resource types to a custom provider using the same policy.
21-
- Association name prefix - This is the prefix to be added to the name of the association resource being created. The default value is "DeployedByPolicy".
19+
- Custom provider Id - This ID is the resource ID of the custom provider to which the resources need to be associated.
20+
- Resource types to associate - These resource types are the list of resource types to be associated to the custom provider. You can associate multiple resource types to a custom provider using the same policy.
21+
- Association name prefix - This string is the prefix to be added to the name of the association resource being created. The default value is "DeployedByPolicy".
2222

23-
The policy uses DeployIfNotExists evaluation which runs after a Resource Provider has handled a create or update resource request of the selected resource type(s) and has returned a success status code. After that, the association resource gets deployed using a template deployment.
23+
The policy uses DeployIfNotExists evaluation. It runs after a Resource Provider has handled a create or update resource request and the evaluation has returned a success status code. After that, the association resource gets deployed using a template deployment.
2424
For more information on associations, see [Azure Custom Providers resource onboarding](./concepts-custom-providers-resourceonboarding.md)
2525

26-
## How to use deploy associations built-in policy
26+
## How to use the deploy associations built-in policy
2727

2828
### Prerequisites
29-
If the custom provider needs permissions to the subscription to perform an action, the policy deployment of association resource wouldn't work without granting the permissions.
29+
If the custom provider needs permissions to the scope of the policy to perform an action, the policy deployment of association resource wouldn't work without granting the permissions.
3030

3131
### Policy assignment
32-
To use the built-in policy, create a policy assignment and assign the Deploy associations for a custom provider policy. Once the policy has been assigned successfully,
33-
the policy will identify non-compliant resources and deploy association for resources that are non-compliant.
32+
To use the built-in policy, create a policy assignment and assign the Deploy associations for a custom provider policy. The policy will then identify non-compliant resources and deploy association for those resources.
3433

3534
![Assign built-in policy](media/builtin-policy/assign-builtin-policy-customprovider.png)
3635

articles/managed-applications/concepts-managed-applications-built-in-policy.md

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: Deploy associations for a managed application using policy
2+
title: Deploy associations for Azure Managed Application using policy
33
description: Learn about deploying associations for a managed application using Azure Policy service.
44
author: msHich
55
ms.service: managed-applications
@@ -14,23 +14,23 @@ Azure policies can be used to deploy associations to associate resources to a ma
1414

1515
## Built-in policy to deploy associations
1616

17-
Deploy associations for a managed application is a built-in policy that can be used to deploy association to associate a resource to a managed application. The policy accepts three paramaters:
17+
Deploy associations for a managed application is a built-in policy that can be used to deploy association to associate a resource to a managed application. The policy accepts three parameters:
1818

19-
- Managed application Id - This is the resource Id of the managed application to which the resources need to be associated.
20-
- Resource types to associate - These are the list of resource types to be associated to the managed application. You can associate multiple resource types to a managed application using the same policy.
21-
- Association name prefix - This is the prefix to be added to the name of the association resource being created. The default value is "DeployedByPolicy".
19+
- Managed application Id - This ID is the resource ID of the managed application to which the resources need to be associated.
20+
- Resource types to associate - These resource types are the list of resource types to be associated to the managed application. You can associate multiple resource types to a managed application using the same policy.
21+
- Association name prefix - This string is the prefix to be added to the name of the association resource being created. The default value is "DeployedByPolicy".
2222

23-
The policy uses DeployIfNotExists evaluation which runs after a Resource Provider has handled a create or update resource request of the selected resource type(s) and has returned a success status code. After that, the association resource gets deployed using a template deployment.
23+
The policy uses DeployIfNotExists evaluation. It runs after a Resource Provider has handled a create or update resource request of the selected resource type(s) and the evaluation has returned a success status code. After that, the association resource gets deployed using a template deployment.
2424
For more information on associations, see [Azure Custom Providers resource onboarding](./concepts-custom-providers-resourceonboarding.md)
2525

26-
## How to use deploy associations built-in policy
26+
## How to use the deploy associations built-in policy
2727

2828
### Prerequisites
2929
If the managed application needs permissions to the subscription to perform an action, the policy deployment of association resource wouldn't work without granting the permissions.
3030

3131
### Policy assignment
3232
To use the built-in policy, create a policy assignment and assign the Deploy associations for a managed application policy. Once the policy has been assigned successfully,
33-
the policy will identify non-compliant resources and deploy association for resources that are non-compliant.
33+
the policy will identify non-compliant resources and deploy association for those resources.
3434

3535
![Assign built-in policy](media/builtin-policy/assign-builtin-policy-managedapp.png)
3636

0 commit comments

Comments
 (0)