Hi, @LXX Welcome to the Microsoft Q&A forum, and thanks for reaching out.
Sorry for the inconvenience caused, This is a known issue that we are in process of fixing it.
As for now, here are the workarounds that are a little bit easier to use.
- Add a new firewall rule with a new name. And remove old ones when the overall amount of rules reaches close to 128
- Use PowerShell/CLI to update firewall rules Set-AzSqlServerFirewallRule (Az.Sql) | Microsoft Learn
- Use T-SQL to update firewall rules on master DB IP firewall rules - Azure SQL Database and Azure Synapse Analytics | Microsoft Learn
Please let me know if the information is helpful
Regards
Geetha