Your administrator denied access to account e05c3683-3099-44b4-aae4-665929e2e4fa from your current IP. Contact your administrator for more information.

Hello @Databricks

The message: “Your administrator denied access to account … from your current IP.”

strongly indicates that an Azure Databricks account-level IP access restriction is preventing your current public IP address from accessing the Account Console.

Azure Databricks supports separate IP access controls for the Account Console and individual workspaces. When an account-level IP access list is enabled, the Account Console and account-level APIs can only be accessed from permitted IPv4 addresses/ranges.

If you're an account administrator and can access the Account Console from another approved network, check:

Account Console → Security → Policies → Account console IP access list

Look for either an ALLOW rule that does not contain your current public IP address, or a BLOCK rule that contains your IP/range. Block rules take precedence over allow rules.

If your organization intentionally restricts Account Console access, the preferred fix would be to add your trusted corporate/VPN public IPv4 address or CIDR range to the appropriate ALLOW rule rather than disabling the security control entirely.

For example, if your public IPv4 address is:

203.0.113.25

it could be permitted specifically as:

203.0.113.25/32

After the administrator updates the rule, allow a few minutes for the change to take effect. Microsoft notes that changes to these IP access lists can take several minutes to propagate.

If you're not an Azure Databricks account administrator, you'll need to contact whoever administers the Databricks account shown in the error and ask them to verify the account-level IP access policy. Simply having permissions to an Azure Databricks workspace doesn't necessarily give you permission to change Account Console policies.

Also check whether you're connecting through a VPN, corporate proxy, secure web gateway, or another NAT service. Databricks evaluates the public source IP it sees, which may be different from the IP assigned directly to your computer. Testing from the organization's approved VPN/network can therefore be useful.

One other distinction is important: don't troubleshoot only the workspace IP access list. Microsoft documents Account Console IP access lists and workspace IP access lists as separate controls. Since your error occurs specifically while opening the Account Console, I would investigate the account-level policy first.

If you can access the account through the Databricks CLI with appropriate account-admin credentials, Microsoft also provides the account ip-access-lists commands for viewing and managing these rules.

If the issue remains after your current public IPv4 address is confirmed in an enabled ALLOW rule, please share whether you're accessing Databricks through a corporate VPN/proxy and whether other account administrators can open the Account Console from their networks. That would help narrow down whether another account-level network policy is involved.

Please "Accept the Answer" if this information helped you. This will help us and others in the community as well.