Skip to content

Commit cc50914

Browse files
committed
tweak and remove comments
1 parent 6d360d8 commit cc50914

File tree

1 file changed

+2
-80
lines changed

1 file changed

+2
-80
lines changed

articles/firewall/firewall-azure-policy.md

Lines changed: 2 additions & 80 deletions
Original file line numberDiff line numberDiff line change
@@ -8,86 +8,16 @@ ms.topic: how-to
88
ms.date: 09/05/2024
99
---
1010

11-
<!--
12-
Remove all the comments in this template before you sign-off or merge to the main branch.
13-
14-
This template provides the basic structure of a How-to article pattern. See the
15-
[instructions - How-to](../level4/article-how-to-guide.md) in the pattern library.
16-
17-
You can provide feedback about this template at: https://aka.ms/patterns-feedback
18-
19-
How-to is a procedure-based article pattern that show the user how to complete a task in their own environment. A task is a work activity that has a definite beginning and ending, is observable, consist of two or more definite steps, and leads to a product, service, or decision.
20-
21-
-->
22-
23-
<!-- 1. H1 -----------------------------------------------------------------------------
24-
25-
Required: Use a "<verb> * <noun>" format for your H1. Pick an H1 that clearly conveys the task the user will complete.
26-
27-
For example: "Migrate data from regular tables to ledger tables" or "Create a new Azure SQL Database".
28-
29-
* Include only a single H1 in the article.
30-
* Don't start with a gerund.
31-
* Don't include "Tutorial" in the H1.
32-
33-
-->
34-
3511
# Use Azure Policy to help secure your Azure Firewall deployments
3612

37-
<!-- 2. Introductory paragraph ----------------------------------------------------------
38-
39-
Required: Lead with a light intro that describes, in customer-friendly language, what the customer will do. Answer the fundamental “why would I want to do this?” question. Keep it short.
40-
41-
Readers should have a clear idea of what they will do in this article after reading the introduction.
42-
43-
* Introduction immediately follows the H1 text.
44-
* Introduction section should be between 1-3 paragraphs.
45-
* Don't use a bulleted list of article H2 sections.
46-
47-
Example: In this article, you will migrate your user databases from IBM Db2 to SQL Server by using SQL Server Migration Assistant (SSMA) for Db2.
48-
49-
-->
50-
5113
Azure Policy is a service in Azure that allows you to create, assign, and manage policies. These policies enforce different rules and effects over your resources, so those resources stay compliant with your corporate standards and service level agreements. Azure Policy does this by evaluating your resources for noncompliance with assigned policies. For example, you can have a policy to allow only a certain size of virtual machines in your environment or to enforce a specific tag on resources.
5214

5315
Azure Policy can be used to govern Azure Firewall configurations by applying policies that define what configurations are allowed or disallowed. This helps ensure that the firewall settings are consistent with organizational compliance requirements and security best practices.
5416

55-
<!---Avoid notes, tips, and important boxes. Readers tend to skip over them. Better to put that info directly into the article text.
56-
57-
-->
58-
59-
<!-- 3. Prerequisites --------------------------------------------------------------------
60-
61-
Required: Make Prerequisites the first H2 after the H1.
62-
63-
* Provide a bulleted list of items that the user needs.
64-
* Omit any preliminary text to the list.
65-
* If there aren't any prerequisites, list "None" in plain text, not as a bulleted item.
66-
67-
-->
68-
6917
## Prerequisites
7018

7119
If you don't have an Azure subscription, create a [free account](https://azure.microsoft.com/free/?WT.mc_id=A261C142F) before you begin.
7220

73-
<!-- 4. Task H2s ------------------------------------------------------------------------------
74-
75-
Required: Multiple procedures should be organized in H2 level sections. A section contains a major grouping of steps that help users complete a task. Each section is represented as an H2 in the article.
76-
77-
For portal-based procedures, minimize bullets and numbering.
78-
79-
* Each H2 should be a major step in the task.
80-
* Phrase each H2 title as "<verb> * <noun>" to describe what they'll do in the step.
81-
* Don't start with a gerund.
82-
* Don't number the H2s.
83-
* Begin each H2 with a brief explanation for context.
84-
* Provide a ordered list of procedural steps.
85-
* Provide a code block, diagram, or screenshot if appropriate
86-
* An image, code block, or other graphical element comes after numbered step it illustrates.
87-
* If necessary, optional groups of steps can be added into a section.
88-
* If necessary, alternative groups of steps can be added into a section.
89-
90-
-->
9121
## Policies available for Azure Firewall
9222

9323
The following policies are available for Azure Firewall:
@@ -121,7 +51,7 @@ The following policies are available for Azure Firewall:
12151
This policy recommends migrating from Firewall Classic Rules to Firewall Policy.
12252
- **VNET with specific tag must have Azure Firewall Deployed**
12353

124-
This policy finds all VNETs with a specified tag and checks if there's an Azure Firewall deployed, and flags it as noncompliant if no Azure Firewall exists.
54+
This policy finds all virtual networks with a specified tag and checks if there's an Azure Firewall deployed, and flags it as noncompliant if no Azure Firewall exists.
12555

12656
The following steps show how you can create an Azure Policy that enforces all Firewall Policies to have the Threat Intelligence feature enabled (either **Alert Only**, or **Alert and deny**). The Azure Policy scope is set to the resource group that you create.
12757

@@ -178,15 +108,7 @@ Now you attempt to create a Firewall Policy with Threat Intelligence disabled.
178108

179109
You should see an error that says your resource was disallowed by policy, confirming that your Azure Policy doesn't allow firewall policies that have Threat Intelligence disabled.
180110

181-
:::image type="content" source="media/firewall-azure-policy/azure-policy.png" lightbox="media/firewall-azure-policy/azure-policy.png" alt-text="Screenshot shown policy create denial.":::
182-
183-
<!-- 5. Next step/Related content------------------------------------------------------------------------
184-
185-
Optional: You have two options for manually curated links in this pattern: Next step and Related content. You don't have to use either, but don't use both.
186-
- For Next step, provide one link to the next step in a sequence. Use the blue box format
187-
- For Related content provide 1-3 links. Include some context so the customer can determine why they would click the link. Add a context sentence for the following links.
188-
189-
-->
111+
:::image type="content" source="media/firewall-azure-policy/azure-policy.png" lightbox="media/firewall-azure-policy/azure-policy.png" alt-text="Screenshot showing policy create denial.":::
190112

191113
## Related content
192114

0 commit comments

Comments
 (0)