Azure SQL Server firewall not allowing operation to connect even though option is set to yes in firewall settings

Marco Pagan 6 Reputation points
2021-03-26T14:51:17.44+00:00

I am trying to import my local SQL server database into Azure & I have all the requirements (storage, bacpac file, etc). When I try to import the db, I am getting the error below.

The Azure SQL Server firewall did not allow the operation to connect. To resolve this, please select the "Allow All Azure" checkbox in the Sql Server's configuration blade.

I have already checked yes on the Allow Azure services and resources to access this server option in the firewall settings. Is there something behind the scenes preventing it from allowing access? I am running my SQL server on a Docker container. My Client IP is in my firewall settings along with an IP that is from 0.0.0.0 to 255.255.255.255 and the database still will not import.

Imported bacpac file
81936-local-db.png

Import Operation Azure
81860-import-azure.png

Import Error
81837-import-error.png

Firewall Settings
81918-firewall-settings.png

Azure Database Migration service
Azure SQL Database
Azure Firewall
Azure Firewall
An Azure network security service that is used to protect Azure Virtual Network resources.
566 questions
Azure Migrate
Azure Migrate
A central hub of Azure cloud migration services and tools to discover, assess, and migrate workloads to the cloud.
717 questions
0 comments No comments
{count} vote

1 answer

Sort by: Most helpful
  1. Navtej Singh Saini 4,216 Reputation points Microsoft Employee
    2021-03-30T01:29:11.357+00:00

    @Marco Pagan

    We see that you were able to resolve the issue here on Stack Overflowcand as mentioned below:

    It might have been the cache on Azure's side. I got in contact with an Azure rep recently and they stated that the cache may have not updated yet. Clearing your cache could be the source of the problem as well.

    Creating a new rule that spans from 0.0.0.0 to 255.255.255.255 in your firewall settings.

    Regards
    Navtej S

    0 comments No comments