You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/firewall/draft-deploy.md
+83-20Lines changed: 83 additions & 20 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
---
2
2
title: Azure Firewall features
3
-
description: Learn about Azure Firewall feature draft and deploy
3
+
description: Learn about Azure Firewall feature draft and deployment
4
4
services: firewall
5
5
author: vekannan
6
6
ms.service: azure-firewall
@@ -9,14 +9,14 @@ ms.date: 04/22/2025
9
9
ms.author: duau
10
10
---
11
11
12
-
# Azure Firewall Draft and Deploy (Preview)
12
+
# Azure Firewall Draft + Deployment (Preview)
13
13
14
14
Organizations are required to make frequent changes to their Firewall Policy for several reasons: onboarding a new application or workload, patching security issue, or for maintenance and optimizing their policy by merging rules or deleting unused rules. These updates can be performed by multiple people, while each update can take up to a few minutes to be deployed.
15
15
With Azure Firewall Policy Save & Commit, you can now update your policy in a 2-phased approach:
16
16
17
-
*Save: Make as many changes as needed, by one or more people, which will be saved in a temporary policy draft (which is cloned from your current applied policy). These changes are extremely fast to make.
17
+
*Draft: Make as many changes as needed, by one or more people, which will be saved in a temporary policy draft (which is cloned from your current applied policy). These changes are extremely fast to make.
18
18
19
-
*Commit: Apply the changes altogether by deploying the draft version and make it your current applied policy.
19
+
*Deployment: Apply the changes altogether by deploying the draft version and make it your current applied policy.
20
20
21
21
In this article, you learn how to:
22
22
@@ -29,31 +29,94 @@ In this article, you learn how to:
29
29
30
30
If you don't have an Azure subscription, create a [free account](https://azure.microsoft.com/free/?WT.mc_id=A261C142F) before you begin.
31
31
32
-
### Use Draft + Commit
32
+
If you want to use this feature via CLI, then make sure azure-firewall extenstion version is above [1.2.3](https://github.com/Azure/azure-cli-extensions/releases/tag/azure-firewall-1.2.3)
33
33
34
-
Azure Firewall's draft and deploy feature allows you to safely test changes in a demo or test environment before applying them to production.
34
+
## Use Draft + Deployment
35
+
36
+
Azure Firewall's draft + deployment feature allows you to make bulk updates to your firewall policy, before applying them to production.
35
37
36
38
1. In the Azure portal, navigate to your existing firewall policies or create a new one.
37
-
1. On the Azure Firewall Policy blade, click **Draft & Deployment**, then select **Create a new draft.** This will create a new draft associated with this policy, which is a 1-1 copy of your current applied policy.
39
+
1. On the Azure Firewall Policy blade, under **Management** section click **Draft & Deployment**, then select **Create a new draft.** This creates a draft that is an exact copy of your current applied policy.
38
40
39
-
:::image type="content" source="media/draft-deploy/Picture1.png" alt-text="screenshot of Draft and Deploy":::
41
+
:::image type="content" source="media/draft-deploy/pic1.png" alt-text="screenshot of Draft and Deploy":::
40
42
41
-
1. On the draft page, make changes or additions to your rules or other settings. These pages are identical to the ones in the deployed draft, but changes you make in a draft will be deployed only when you specifically deploy the draft.
42
-
1. Next, return to the **deploy** screen, and select **deploy draft**. Once the draft is deployed, the updated version, including all changes you made in draft, will override the current deployed policy and become the latest version. The draft body itself will be deleted after that. And you will then be able to create a new draft on top of the new deployment again.
43
-
1. You can repeat the process as many times as you would like to make further changes to the firewall policy.
43
+
:::image type="content" source="media/draft-deploy/pic2.png" alt-text="screenshot of create a draft":::
44
+
45
+
1. On the draft page, make changes or additions to your rules or settings. These pages are identical to the ones in the deployed draft. These changes will only take effect when you deploy the draft.
46
+
:::image type="content" source="media/draft-deploy/pic3.png" alt-text="screenshot of drafting changes":::
47
+
48
+
1. To verify the changes, return to the **deploy** screen and see the rules or setting changes. To deploy, select **deploy draft**. Once deployed, the draft replaces the current policy and becomes the latest version. The draft itself is deleted after the deployment.
49
+
50
+
:::image type="content" source="media/draft-deploy/pic4.png" alt-text="screenshot of check changes and deploy":::
51
+
52
+
1. Repeat the process as needed to make further updates to the firewall policy.
53
+
54
+
> [!NOTE]
55
+
> When using this feature via PowerShell or API, you must first download the current policy and manually create a draft based on it. In contrast, when using the Azure portal or CLI, creating a draft automatically generates it from the existing policy.
0 commit comments