Hi Erich Late,
Thank you for reaching out to Microsoft QA!
it sounds like you're facing a frustrating situation with your SQL Server connection getting blocked despite your office's public IP being in the allow list. The error code you're seeing (NativeError=40615) indicates that the connection attempt is being rejected because your IP address is not allowed. Let's go through some potential reasons and solutions.
Public Network Access Check:
Confirm Public network access is "Selected networks" (not Disabled) in SQL Server > Networking. Disabled forces private endpoints only.
Rule Propagation Wait Time:
Firewall updates take up to 5 mins. Wait full window after changes.
Catch the Real Client IP:
Portal's client IP often wrong due to proxies from office PC, check whatismyipaddress.com for actual IPv4. Add as /32 rule.
Layered Firewall Rules Check server + database level:
SELECT * FROM sys.database_firewall_rules;
Remove conflicts, recreate at server level.
Auth Cache Flush Elastic pool? Run DBCC FLUSHAUTHCACHE; from another DB on server.
Next: Test mobile hotspot, grab blocked IP from logs, share Networking screenshot + whatismyip. What's your Public Network Access set to now?
If you've already confirmed these settings and the issue persists, could you provide more details on the following?
- Is your SQL Server using a Private Endpoint or Public Endpoint for connection?
- Are there any other network configurations like VPNs or proxies used in your office that might affect connectivity?
- Could you check if there are any network constraints (e.g., inbound or outbound rules) set in your office's firewall or router?
Let me know how it goes! Hope this helps!