Skip to content

Commit 611d252

Browse files
committed
Fixed Unknown section and fixed typo
1 parent 7a1af89 commit 611d252

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/governance/policy/concepts/compliance-states.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -53,7 +53,7 @@ An applicable resource has a compliance state of exempt for a policy assignment
5353
5454
### Unknown (preview)
5555

56-
This compliance state only occurs for policy assignments with `manual` effect, when the policy definition has a default compliance state of unknown and there is no active [attestation](./attestation-structure.md) for the applicable resource stating otherwise.
56+
Unknown is the default compliance state for definitions with `manual` effect, unless the default has been explicitly set to compliant or non-compliant. This state indicates that an [attestation](./attestation-structure.md) of compliance is warranted. This compliance state only occurs for policy assignments with `manual` effect.
5757

5858
### Not registered
5959

@@ -73,7 +73,7 @@ This compliance state indicates that the evaluation cycle hasn't started for the
7373

7474
Now that you have an understanding of what compliance states exist and what each one means, let's look at an example using compliant and non-compliant states.
7575

76-
Suppose you have a resource group - ContsoRG, with some storage accounts
76+
Suppose you have a resource group - ContosoRG, with some storage accounts
7777
(highlighted in red) that are exposed to public networks.
7878

7979
:::image type="complex" source="../media/getting-compliance-data/resource-group01.png" alt-text="Diagram of storage accounts exposed to public networks in the Contoso R G resource group." border="false":::

0 commit comments

Comments
 (0)