Adding an Azure SQL Database as an MS SQL Monitor

Adding an Azure SQL Database as an MS SQL Monitor

Troubleshooting guide for Azure SQL Database monitoring in ManageEngine Applications Manager.

Azure SQL Database has connection and firewall requirements that differ from an on-premises SQL Server. Check the server name, firewall rules and database name when adding the monitor.

1. Cannot open server '<name>' requested by the login. The login failed.

What it means: Azure could not match the request to a server or would not allow the client to reach it. Although the message appears to indicate a login failure, the credentials may be correct.

  1. Use the fully qualified server name. In the monitor's Host Name field, enter <your-server>.database.windows.net. A short server name will not resolve to the Azure SQL server.
  2. Add the Applications Manager host to the Azure SQL firewall. In the Azure portal, open the SQL server, navigate to Networking → Firewall rules, and add the public IP address of the machine running Applications Manager. Save the rule and allow time for it to take effect.
  3. Specify the database name. Enter the database to be monitored in the monitor's database field.
  4. Check the login format. If the plain user name is rejected, try user@your-server, as some drivers require this format.

2. The client with IP address '<address>' is not allowed to access the server.

What it means: The client host's IP address is not included in the Azure SQL server firewall rules.

What to do: Add the IP address shown in the error message to the SQL server's firewall rules. Azure reports the public IP address it sees, which may differ from the address displayed on the Applications Manager machine. Use the address from the error message.

If the Applications Manager host uses a changing public IP address, ask your Azure administrator about a firewall rule covering the required range or connecting through a private endpoint.

Suggested KB slug: adding-an-azure-sql-database-as-an-mssql-monitor