An Azure relational database service.
The issue occurred because of a late payment which I didnt realize.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
I am attempting to add a firewall rule to my SQL database. I get the message : "An error occurred while fetching firewall rule details. Please try loading the firewall rule again" as I access the page. How can I resolve?
An Azure relational database service.
Answer recommended by moderator
The issue occurred because of a late payment which I didnt realize.
Hi Mark Wedderburn,
It looks like you're facing an issue with adding a firewall rule to your SQL database, getting an error while trying to fetch rule details. This problem might be caused by a couple of reasons. Here are some steps you can try to resolve the issue:
Check Permissions: Ensure you have the required permissions assigned to your account to manage firewall rules. You might need to be a subscription owner or have contributor-level access.
Enable TCP Port 1433: Make sure that TCP port 1433 is open on your local network as it is required for connecting to Azure SQL Database. You can check this by running:
telnet <your-server-name>.database.windows.net 1433
If it fails, the port might be blocked.
Review Your IP Configuration: Go to the Azure portal, access your SQL server, and check the Configure tab to verify your Current Client IP Address. Ensure this IP address is added to the firewall rules under Allowed IP Addresses.
Dynamic IP Address Considerations: If you’re using a dynamic IP address, it might change regularly, which could lead to access issues. In this case, consider adding a range or switching to a static IP.
Clear Cache: If you've made changes to your firewall rules and they aren't recognized immediately, you can clear the local cache by running:
DBCC FLUSHAUTHCACHE;
This command helps to refresh the authentication cache for your database.
Check Documentation: You can refer to these helpful documents for detailed steps and troubleshooting tips:
If these steps don't solve your issue, I suggest providing a bit more detail about your setup. Here are a few follow-up questions that could help narrow down the problem:
Hope this helps you get back on track! Let me know if there's anything else you need!
Maybe that is related to temporary issues on the Azure region where the server is located. Examine Resource Health to find possible health information related the server/database. In this case
Make sure you still have permissions to manage firewall rules. See permissions required here.
As a workaround, try to create the rule using Transact-SQL while connected to the master database or using Azure CLI.
EXECUTE sp_set_firewall_rule
@name = N'AllowSpecificIP',
@start_ip_address = '192.168.1.1',
@end_ip_address = '192.168.1.10';