Merge pull request #115175 from DCtheGeek/dmc-policy-samplesparameters

Add Parameters pattern #3 - Effect

Author: ktoliver

articles/governance/policy/samples/pattern-parameters.md

@@ -1,7 +1,7 @@
 ---
 title: "Pattern: Parameters in a policy definition"
 description: This Azure Policy pattern provides an example of how to use parameters in a policy definition.
-ms.date: 01/31/2020
+ms.date: 05/20/2020
 ms.topic: sample
 ---
 # Azure Policy pattern: parameters
@@ -52,6 +52,26 @@ Here, it's used against the **serviceProvider.bandwidthInMbps** alias as one of
 
 :::code language="json" source="~/policy-templates/patterns/pattern-parameters-2.json" range="21-24" highlight="3":::
 
+## Sample 3: Parameterized effect
+
+A common way to make policy definitions reusable is to parameterize the effect itself. This example
+uses a single parameter, **effect**. Parameterizing the effect makes it possible to assign the same
+definition to different scopes with different effects.
+
+:::code language="json" source="~/policy-templates/patterns/pattern-parameters-3.json":::
+
+### Sample 3: Explanation
+
+:::code language="json" source="~/policy-templates/patterns/pattern-parameters-3.json" range="11-25":::
+
+In this portion of the policy definition, the **effect** parameter is defined as _string_. The
+policy definition sets the default value for an assignment to _audit_ and limits the other options
+to _disabled_ and _deny_.
+
+The parameter is then used in the **policyRule.then** block for the _effect_.
+
+:::code language="json" source="~/policy-templates/patterns/pattern-parameters-3.json" range="38-40" highlight="2":::
+
 ## Next steps
 
 - Review other [patterns and built-in definitions](./index.md).