Skip to content

Commit 8059653

Browse files
Update mfa-enforcement.md
1 parent efc659c commit 8059653

File tree

1 file changed

+10
-11
lines changed

1 file changed

+10
-11
lines changed

articles/governance/policy/tutorials/mfa-enforcement.md

Lines changed: 10 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: "Tutorial: Apply MFA Self-Enforcement through Azure Policy"
2+
title: "Tutorial: Self-enforce MFA through Azure Policy"
33
description: Learn how to gather audit events or enforce MFA enforcement on your environment
44
ms.date: 07/17/2025
55
ms.topic: how-to
@@ -32,12 +32,13 @@ Select Policy under Azure services. If you don't see it, type 'Policy' in the se
3232
> To enable safe rollout of policy enforcement, we recommend using [Azure Policy’s resource selectors](/azure/governance/policy/concepts/assignment-structure#resource-selectors) to gradually rollout policy enforcement across your resources.
3333
1. Click 'Expand' on the 'Resource Selectors' section of the Basics tab.
3434
2. Click 'Add a resource selector'
35-
36-
:::image type="content" source="../media/multifactor-enforcement/policy-resource-selectors.png" alt-text="Screenshot of Azure Policy Assignment Creation View." border="false" lightbox="../media/multifactor-enforcement/policy-resource-selectors.png":::
37-
1. Add a name for your selector
38-
2. Toggle resourceLocation to enable it.
39-
3. Pick a few low-risk regions that you’d like to enforce on. The policy assignment will evaluate Azure resources in those regions.
40-
4. You can update this assignment later to add more regions by adding more resourceLocation selectors or updating the existing resourceLocation selector to add more regions.
35+
36+
:::image type="content" source="../media/multifactor-enforcement/policy-resource-selectors.png" alt-text="Screenshot of Azure Policy Assignment Creation View." border="false" lightbox="../media/multifactor-enforcement/policy-resource-selectors.png":::
37+
38+
3. Add a name for your selector
39+
4. Toggle resourceLocation to enable it.
40+
5. Pick a few low-risk regions that you’d like to enforce on. The policy assignment will evaluate Azure resources in those regions.
41+
6. You can update this assignment later to add more regions by adding more resourceLocation selectors or updating the existing resourceLocation selector to add more regions.
4142

4243
:::image type="content" source="../media/multifactor-enforcement/resource-selector-creation.png" alt-text="Screenshot of Azure Policy Selector Creation View." border="false" lightbox="../media/multifactor-enforcement/resource-selector-creation.png":::
4344

@@ -87,8 +88,6 @@ You can enable enforcement by updating the 'Effect' of the policy assignment.
8788
6. Click 'Review + save', then 'Create'.
8889
7. Once you have confirmed no unexpected impact, you may update the existing override to add other regions.
8990

90-
## User Experience during Preview
91-
9291
## Audit Mode
9392
Discover audit events in your activity log when this policy assignment is applied in audit mode. Each event represents a resource create, update or delete that was performed by a user who did not authenticate with MFA.
9493

@@ -122,5 +121,5 @@ When you attempt to perform a create, update, or delete operation without an MFA
122121
:::image type="content" source="../media/multifactor-enforcement/powershell-sample.png" alt-text="Screenshot of Azure PowerShell View When User Gets Blocked By Policy." border="false" lightbox="../media/multifactor-enforcement/powershell-sample.png":::
123122

124123
## Limitations in the Preview Timeframe
125-
1. In some cases, you may not be prompted to complete MFA after receiving an error. In such cases, reauthenticate with MFA before retrying the operation (for example, through Azure portal).
126-
2. In some cases, the error message may not indicate that the operation is blocked due to the policy assignment in-place. Take note of the error message samples to familiarize your organization on what error messages they may receive.
124+
- In some cases, you may not be prompted to complete MFA after receiving an error. In such cases, reauthenticate with MFA before retrying the operation (for example, through Azure portal).
125+
- In some cases, the error message may not indicate that the operation is blocked due to the policy assignment in-place. Take note of the error message samples to familiarize your organization on what error messages they may receive.

0 commit comments

Comments
 (0)