Skip to content

Commit 312167a

Browse files
authored
Merge pull request #103103 from vhorne/fwm-policy
start firewall manager policy overview
2 parents 9c30140 + 139196c commit 312167a

File tree

3 files changed

+64
-0
lines changed

3 files changed

+64
-0
lines changed
162 KB
Loading
Lines changed: 62 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,62 @@
1+
---
2+
title: Azure Firewall Manager Preview policy overview
3+
description: Learn about Azure Firewall Manager policies
4+
author: vhorne
5+
ms.service: firewall-manager
6+
services: firewall-manager
7+
ms.topic: overview
8+
ms.date: 02/18/2020
9+
ms.author: victorh
10+
---
11+
12+
# Azure Firewall Manager Preview policy overview
13+
14+
[!INCLUDE [Preview](../../includes/firewall-manager-preview-notice.md)]
15+
16+
Firewall policy is an Azure resource that contains NAT, network, and application rule collections as well as Threat Intelligence settings. It's a global resource that can be used across multiple Azure Firewall instances in Secured Virtual Hubs and Hub Virtual Networks. Policies work across regions and subscriptions.
17+
18+
![Azure Firewall Manager policy](media/policy-overview/policy-overview.png)
19+
20+
## Policy creation and association
21+
22+
A policy can be created and managed in multiple ways, including the Azure portal, REST API, templates, Azure PowerShell, and CLI.
23+
24+
You can also migrate existing rules from Azure Firewall using the portal or Azure PowerShell to create policies. For more information, see [How to migrate Azure Firewall configurations to Azure Firewall policy (preview)](migrate-to-policy.md).
25+
26+
Policies can be associated with one or more virtual hubs or VNets. The firewall can be in any subscription associated with your account and in any region.
27+
28+
## Hierarchical policies
29+
30+
New policies can be created from scratch or inherited from existing policies. Inheritance allows DevOps to create local firewall policies on top of organization mandated base policy.
31+
32+
Policies created with non-empty parent policies inherit all rule collections from the parent policy.
33+
Network rule collections inherited from a parent policy are always prioritized above network rule collections defined as part of a new policy. The same logic also applies to application rule collections. However, network rule collections are always processed before application rule collections regardless of inheritance.
34+
35+
Threat Intelligence mode is also inherited from the parent policy. You can set your threat Intelligence mode to a different value to override this behavior, but you can't turn it off. It's only possible to override with a stricter value. For example, if your parent policy is set to **Alert only**, you can configure this local policy to **Alert and deny**.
36+
37+
NAT rule collections aren't inherited because they're specific to a given firewall.
38+
39+
With inheritance, any changes to the parent policy are automatically applied down to associated firewall child policies.
40+
41+
## Traditional rules and policies
42+
43+
Azure Firewall supports both traditional rules and policies. The following table compares policies and rules:
44+
45+
46+
| |Policy |Rules |
47+
|---------|---------|---------|
48+
|Contains |NAT, Network, Application rules, and Threat Intelligence settings|NAT, Network, and Application rules |
49+
|Protects |Virtual hubs and Virtual Networks|Virtual Networks only|
50+
|Portal experience |Central management using Firewall Manager|Standalone firewall experience|
51+
|Multiple firewall support |Firewall Policy is a separate resource that can be used across firewalls|Manually export and import rules, or using third-party management solutions |
52+
|Pricing |Billed based on firewall association. See [Pricing](#pricing).|Free|
53+
|Supported deployment mechanisms |Portal, REST API, templates, Azure PowerShell, and CLI|Portal, REST API, templates, PowerShell, and CLI. |
54+
|Release Status |Public Preview|General Availability|
55+
56+
## Pricing
57+
58+
Policies are billed based on firewall associations. A policy with zero or one firewall association is free of charge. A policy with multiple firewall associations is billed at a fixed rate. For more information, see [Azure Firewall Manager Pricing](https://azure.microsoft.com/pricing/details/firewall-manager/).
59+
60+
## Next steps
61+
62+
To learn how to deploy an Azure Firewall, see [Tutorial: Secure your cloud network with Azure Firewall Manager Preview using the Azure portal](secure-cloud-network.md).

articles/firewall-manager/toc.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -11,6 +11,8 @@
1111
href: secure-cloud-network.md
1212
- name: Concepts
1313
items:
14+
- name: Policy overview
15+
href: policy-overview.md
1416
- name: What is a secured virtual hub?
1517
href: secured-virtual-hub.md
1618
- name: General deployment process

0 commit comments

Comments
 (0)