Proposed Pull Request Change

📄 Document Links

View on GitHub View on Microsoft Learn

--- title: IP Groups in Azure Firewall description: IP groups allow you to group and manage IP addresses for Azure Firewall rules. author: duau ms.author: duau ms.service: azure-firewall ms.topic: concept-article ms.date: 03/28/2026 ms.custom: - devx-track-azurepowershell - sfi-image-nochange # Customer intent: "As a network administrator, I want to create and manage IP Groups for Azure Firewall, so that I can efficiently organize and apply IP address rules across multiple firewalls and enhance network security." --- # IP Groups in Azure Firewall IP Groups make it easy to group and manage IP addresses for Azure Firewall rules. Use IP Groups in the following ways: - As a source address in DNAT rules - As a source or destination address in network rules - As a source address in application rules An IP Group can include a single IP address, multiple IP addresses, one or more IP address ranges, or a combination of addresses and ranges. You can use IP Groups in Azure Firewall DNAT, network, and application rules for multiple firewalls across regions and subscriptions in Azure. Group names must be unique. You can configure an IP Group in the Azure portal, Azure CLI, or REST API. A sample template is provided to help you get started. ## Sample format The following IPv4 address format examples are valid to use in IP Groups: - Single address: 10.0.0.0 - CIDR notation: 10.1.0.0/32 - Address range: 10.2.0.0-10.2.0.31 ## Create an IP Group Create an IP Group by using the Azure portal, Azure CLI, or REST API. For more information, see [Create an IP Group](create-ip-group.md). ## Browse IP Groups 1. In the Azure portal search bar, type `IP Groups` and select it. You can see the list of IP Groups, or you can select **Add** to create a new IP Group. 1. Select an IP Group to open the overview page. You can edit, add, or delete IP addresses or IP Groups. ## Manage an IP Group You can see all the IP addresses in the IP Group and the rules or resources that are associated with it. To delete an IP Group, you must first dissociate the IP Group from the resource that uses it. 1. To view or edit the IP addresses, select **IP Addresses** under **Settings** in the left pane. 1. To add single or multiple IP addresses, select **Add IP Addresses**. This action opens the **Drag or Browse** page for an upload, or you can enter the address manually. 1. Select the ellipses (**…**) to the right to edit or delete IP addresses. To edit or delete multiple IP addresses, select the check boxes and select **Edit** or **Delete** at the top. 1. Finally, you can export the file in the CSV file format. > [!NOTE] > If you delete all the IP addresses in an IP Group but the IP Group is still in use in a rule, that rule is skipped. ## Use an IP Group Select **IP Group** as a **Source type** or **Destination type** for the IP addresses when you create Azure Firewall DNAT, application, or network rules. ## Parallel IP Group updates You can update multiple IP Groups in parallel at the same time. This feature is particularly useful for environments that require faster changes at scale, especially when you make those changes by using a dev ops approach (templates, ARM, CLI, and Azure PowerShell). By using this feature, you can: - **Update 20 IP Groups at a time:** Perform simultaneous updates for up to 20 IP Groups in one operation, referenced by firewall policy or classic firewall. - **Update Azure Firewall and IP Groups together:** Update IP Groups simultaneously with the firewall or with firewall policies. - **Improved efficiency:** Parallel IP Group updates now run twice as fast. - **Receive new and improved error messages:** |Error message |Description |Recommended action| |---------|---------|---------| |**In failed state (skipping update)** |Azure Firewall or Firewall Policy is in a failed state. Updates can't proceed until the resource is healthy. |Review previous operations and correct any misconfigurations to ensure the resource is healthy.| | **Backend server could not update Firewall at this time** | The backend server was unable to successfully process the request.| Create a support request.| | **Error occurred during FW update** | The error is related to the underlying backend servers.| Retry the operation or create a support request if the issue persists.| | **Internal server error** | An unexpected backend error occurred. | Retry the operation or create a support request.| Also, note the following status updates: - **One or more IP Group failure:** If one IP Group update (out of 20 parallel updates) fails, the provisioning state changes to "Failed" while the remaining IP Groups continue to update and succeed. - **Status update:** If an IP Group update fails, and if the firewall remains healthy, its state still shows as "Succeeded." To verify, check the status on the IP Group resource itself. ## Region availability IP Groups are available in all public cloud regions. ## IP address limits For IP Group limits, see [Azure subscription and service limits, quotas, and constraints](../azure-resource-manager/management/azure-subscription-service-limits.md#azure-firewall-limits). ## Related Azure PowerShell cmdlets Use the following Azure PowerShell cmdlets to create and manage IP Groups: - [New-AzIpGroup](/powershell/module/az.network/new-azipgroup) - [Remove-AzIPGroup](/powershell/module/az.network/remove-azipgroup) - [Get-AzIpGroup](/powershell/module/az.network/get-azipgroup) - [Set-AzIpGroup](/powershell/module/az.network/set-azipgroup) - [New-AzFirewallNetworkRule](/powershell/module/az.network/new-azfirewallnetworkrule) - [New-AzFirewallApplicationRule](/powershell/module/az.network/new-azfirewallapplicationrule) - [New-AzFirewallNatRule](/powershell/module/az.network/new-azfirewallnatrule) ## Next steps - Learn how to [deploy and configure an Azure Firewall](tutorial-firewall-deploy-portal.md).