| title | sp_delete_firewall_rule | ||||
|---|---|---|---|---|---|
| titleSuffix | Azure SQL Database | ||||
| description | Removes server-level firewall settings from your Azure SQL Database logical server. | ||||
| author | VanMSFT | ||||
| ms.author | vanto | ||||
| ms.reviewer | randolphwest | ||||
| ms.date | 06/23/2025 | ||||
| ms.service | azure-sql-database | ||||
| ms.topic | reference | ||||
| f1_keywords |
|
||||
| helpviewer_keywords |
|
||||
| dev_langs |
|
||||
| monikerRange | =azuresqldb-current || =azure-sqldw-latest |
[!INCLUDE asdb-asa]
Removes server-level firewall settings from your [!INCLUDE ssSDS] server. This stored procedure is only available in the master database to the server-level principal login.
sp_delete_firewall_rule [ @name = ] N'name'
[ ; ]
The name of the server-level firewall setting that will be removed. @name is nvarchar(128) with no default.
In [!INCLUDE ssSDS], the credential data required to authenticate a connection and server-level firewall rules are temporarily cached in each database. This cache is periodically refreshed. To force a refresh of the authentication cache and make sure that a database has the latest version of the logins table, execute DBCC FLUSHAUTHCACHE.
Because sp_delete_firewall_rule is an extended stored procedure, the data type of the value passed in for the parameter much match exactly. Implicit conversions from other types don't take place.
Only the server-level principal login created by the provisioning process can delete server level firewall rules. The user must be connected to the master database to execute sp_delete_firewall_rule.
The following example removes the server-level firewall setting named Example setting 1. Execute the statement in the virtual master database.
EXECUTE sp_delete_firewall_rule N'Example setting 1';