Azure Firewall unable to update existing rules.

This seems to be a temporary issue in the Azure portal UI when saving rule updates. The console error you shared (Cannot read properties of undefined reading 'ruleCollectionGroup') usually appears when the portal session cache gets out of sync with the policy data.

Try clearing your browser cache or open the Azure portal in a private window. If the issue continues, you can edit or save the rule directly using Azure PowerShell or CLI, that usually works even when the portal fails.

Tried clearing browser cache or open the Azure portal in a private window but it didn't work. Any other options than Azure PowerShell or CLI?

Hi Mr K

Welcome to Microsoft Q&A forum.

You can try some of the below steps:

Use Azure CLI or PowerShell

update the rule using CLI:

Example: Update an existing Firewall Policy rule collection

az network firewall policy rule-collection-group update \
--policy-name <FirewallPolicyName> \
--resource-group <ResourceGroupName> \
--name <RuleCollectionGroupName> \
--rule-collection <RuleCollectionName> \
--action Allow \
--priority 100

For PowerShell:

Update-AzFirewallPolicyRuleCollectionGroup `
-Name "<RuleCollectionGroupName>" `
-PolicyName "<FirewallPolicyName>" `
-ResourceGroupName "<ResourceGroupName>"

Switch to Classic Editor

• If you’re using the new preview UI, switch back to the classic editor for Firewall Policy rules. This often bypasses the bug.

You can use Azure Resource Manager templates or REST API to modify the rule until the.

Hope, you find this comment helpful, if yes, please “up-vote” for the information provided , this can be beneficial to community members.

Kindly let us know if you have any additional questions.

Thanks

I would like to do this through Azure portal as the Firewall is on a production environment. I don't have a test Firewall setup to test/validate Azure Resource Manager templates/REST API/CLI/PowerShell . Is there anyway Microsoft can fix this?

Hi Mr K,

Yes , you can validate through azure portal as yo don't have test set up otherwise try to set up a test firewall & try those above steps from CLI/powershell/REST API.

Thanks