Azure SQL Firewall Setup — App Dashboard

Why you're here: the Azure SQL server garnet-sql blocks every client IP by default. When a new machine (like the shared IIS host running cwaMESG) tries to connect for the first time, you'll see:

Cannot open server 'garnet-sql' requested by the login. Client with IP address '72.15.144.215' is not allowed to access the server.

Add that IP to the server's firewall allow-list and it starts working within a few minutes.

Faster than the portal: use the Azure DBs card's Firewall Rules tab right here in the dashboard — it lists and adds rules for you.

Go to portal.azure.com and sign in with the account that owns the Garnet subscription.

Search for the SQL server (not the database)

Use the top search bar and type garnet-sql. Pick the result whose type is SQL server — a database has a similar-looking name but a different icon, so double-check the type column.

garnet-sql

🗄️ garnet-sql SQL server ← pick this one

🧱 garnet-sql/cwaMesg SQL database

Open "Networking" in the left menu

Under Security in the server's left-hand menu, click Networking (older portal versions call this "Firewalls and virtual networks").

🔒 Security

Networking ← click this

Identity

Microsoft Defender for Cloud

Add a firewall rule for the hosting server's IP

Under Firewall rules, click + Add a firewall rule, then fill in:

Rule namefity-hosting

Start IP72.15.144.215

End IP72.15.144.215

+ Add a firewall rule

Use the same value for Start IP and End IP unless the host is known to use a range of outbound IPs.

Save

Click Save at the top of the Networking page. Changes take effect in about 1–5 minutes — no restart of the SQL server needed.

💾 Save

Confirm it worked

Reload cwaMESG (or hit / on it again). If the firewall rule was the only problem, the 500.30 startup error goes away and the sign-in page loads normally.