The MySQL user was granted access for a specific host that does not match the client's IP or hostname. The ADF integration runtime or dbt runner uses a different IP than what was granted. Cloud services with dynamic IPs (Azure, AWS) rotate IPs outside the allowed range

Step 1: Check existing grants: `SELECT user, host FROM mysql.user WHERE user='your_user';`. Step 2: Create a wildcard grant: `GRANT SELECT ON your_db.* TO 'your_user'@'%' IDENTIFIED BY 'password'; FLUSH PRIVILEGES;`. Step 3: Or restrict to a specific subnet: `GRANT SELECT ON your_db.* TO 'your_user'@'10.0.0.%' IDENTIFIED BY 'password'; FLUSH PRIVILEGES;`

High severityconnection

Power BI Refresh Error:
1130

What does this error mean?

The connecting host has no matching GRANT entry in mysql.user — the server rejects the connection before authentication.

Common causes

1The MySQL user was granted access for a specific host that does not match the client's IP or hostname
2The ADF integration runtime or dbt runner uses a different IP than what was granted
3Cloud services with dynamic IPs (Azure, AWS) rotate IPs outside the allowed range

How to fix it

1Step 1: Check existing grants: `SELECT user, host FROM mysql.user WHERE user='your_user';`
2Step 2: Create a wildcard grant: `GRANT SELECT ON your_db.* TO 'your_user'@'%' IDENTIFIED BY 'password'; FLUSH PRIVILEGES;`
3Step 3: Or restrict to a specific subnet: `GRANT SELECT ON your_db.* TO 'your_user'@'10.0.0.%' IDENTIFIED BY 'password'; FLUSH PRIVILEGES;`

Frequently asked questions

How is MySQL error 1130 different from 1045?

Error 1130 fires before authentication — MySQL rejects the connection because no GRANT matches the host. Error 1045 fires after host matching succeeds but the password is wrong.

Is using '%' as the host in a GRANT secure?

It allows connections from any IP, so combine it with strong passwords, SSL/TLS, and firewall rules to restrict network-level access.

Can MetricSign help identify which ADF pipelines are affected by host restriction changes?

Yes — MetricSign groups all pipeline failures caused by the same MySQL error into a single incident, showing the full blast radius instantly.

Official documentation: https://dev.mysql.com/doc/mysql-errors/8.0/en/server-error-reference.html