Skip to content

Commit 94dc309

Browse files
authored
Merge pull request #77377 from DCtheGeek/dmc-policy-languagepass
Minor corrections to language
2 parents 2a2c169 + cb6b1f3 commit 94dc309

File tree

1 file changed

+18
-17
lines changed

1 file changed

+18
-17
lines changed

articles/governance/policy/overview.md

Lines changed: 18 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -10,8 +10,8 @@ manager: carmonm
1010
---
1111
# Overview of the Azure Policy service
1212

13-
Governance validates that your organization can achieve its goals through an effective and
14-
efficient use of IT. It meets this need by creating clarity between business goals and IT projects.
13+
Governance validates that your organization can achieve its goals through effective and efficient
14+
use of IT. It meets this need by creating clarity between business goals and IT projects.
1515

1616
Does your company experience a significant number of IT issues that never seem to get resolved?
1717
Good IT governance involves planning your initiatives and setting priorities on a strategic level
@@ -33,11 +33,12 @@ over more details on how to create and implement policies with Azure Policy.
3333
3434
## How is it different from RBAC?
3535

36-
There are a few key differences between Policy and role-based access control (RBAC). RBAC focuses
37-
on user actions at different scopes. You might be added to the contributor role for a resource
38-
group, allowing you to make changes to that resource group. Policy focuses on resource properties
39-
during deployment and for already existing resources. Policy controls properties such as the types
40-
or locations of resources. Unlike RBAC, Policy is a default allow and explicit deny system.
36+
There are a few key differences between Azure Policy and role-based access control (RBAC). RBAC
37+
focuses on user actions at different scopes. You might be added to the contributor role for a
38+
resource group, allowing you to make changes to that resource group. Azure Policy focuses on
39+
resource properties during deployment and for already existing resources. Azure Policy controls
40+
properties such as the types or locations of resources. Unlike RBAC, Azure Policy is a default allow
41+
and explicit deny system.
4142

4243
### RBAC Permissions in Azure Policy
4344

@@ -47,9 +48,9 @@ Azure Policy has several permissions, known as operations, in two Resource Provi
4748
- [Microsoft.PolicyInsights](../../role-based-access-control/resource-provider-operations.md#microsoftpolicyinsights)
4849

4950
Many Built-in roles grant permission to Azure Policy resources. The **Resource Policy Contributor
50-
(Preview)** role includes most Policy operations. **Owner** has full rights. Both **Contributor**
51-
and **Reader** can use all read Policy operations, but **Contributor** can also trigger
52-
remediation.
51+
(Preview)** role includes most Azure Policy operations. **Owner** has full rights. Both
52+
**Contributor** and **Reader** can use all read Azure Policy operations, but **Contributor** can
53+
also trigger remediation.
5354

5455
If none of the Built-in roles have the permissions required, create a [custom role](../../role-based-access-control/custom-roles.md).
5556

@@ -93,7 +94,7 @@ networking resources. You could exclude a resource group in that subscription th
9394
networking infrastructure. You then grant access to this networking resource group to users that
9495
you trust with creating networking resources.
9596

96-
In another example, you might want to assign a resource type whitelist policy at the management
97+
In another example, you might want to assign a resource type allow list policy at the management
9798
group level. And then assign a more permissive policy (allowing more resource types) on a child
9899
management group or even directly on subscriptions. However, this example wouldn't work because
99100
policy is an explicit deny system. Instead, you need to exclude the child management group or
@@ -167,7 +168,7 @@ options:
167168
When creating value options in an initiative definition, you're unable to input a different value
168169
during the initiative assignment because it's not part of the list.
169170

170-
## Maximum count of Policy objects
171+
## Maximum count of Azure Policy objects
171172

172173
[!INCLUDE [policy-limits](../../../includes/azure-policy-limits.md)]
173174

@@ -208,8 +209,8 @@ visit [Govern your Azure environment through Azure Policy](https://channel9.msdn
208209
Now that you have an overview of Azure Policy and some of the key concepts, here are the suggested
209210
next steps:
210211

211-
- [Assign a policy definition using the portal](assign-policy-portal.md)
212-
- [Assign a policy definition using the Azure CLI](assign-policy-azurecli.md)
213-
- [Assign a policy definition using PowerShell](assign-policy-powershell.md)
214-
- Review what a management group is with [Organize your resources with Azure management groups](..//management-groups/overview.md)
215-
- View [Govern your Azure environment through Azure Policy](https://channel9.msdn.com/events/Build/2018/THR2030) on Channel 9
212+
- [Assign a policy definition using the portal](assign-policy-portal.md).
213+
- [Assign a policy definition using the Azure CLI](assign-policy-azurecli.md).
214+
- [Assign a policy definition using PowerShell](assign-policy-powershell.md).
215+
- Review what a management group is with [Organize your resources with Azure management groups](..//management-groups/overview.md).
216+
- View [Govern your Azure environment through Azure Policy](https://channel9.msdn.com/events/Build/2018/THR2030) on Channel 9.

0 commit comments

Comments
 (0)