Do you get further if you click the On Host checkbox in the V/I job? Prior to this, set up your ODBC System DSN directly on the Sage server if not already done.

No luck with the On Host checkbox, I get the same error message.  The ODBC connections are already on the sage server.

Is there any way to see a more verbose log to see what the underlying connection issue might be?

Maybe set up a local SQL Express, with linked server to Azure, and a SQL View as a bridge?

Ryan - You can see a bit more verbose logging by going into the DSN, clicking Debug tab then checking Enable Debug. Change the Log File path and and filename while you're at it.

Also I just remembered one the Sage developers I work with (another MD / DP) told me about this. He said Azure itself is rejecting the connection so he had to make an adjustment to a VI program to handle it. I'll give you his contact info if interested but I would try Kevin's idea it sounds very promising.

Ryan - You can see a bit more verbose logging by going into the DSN, clicking Debug tab then checking Enable Debug. Change the Log File path and and filename while you're at it.

Also I just remembered one the Sage developers I work with (another MD / DP) told me about this. He said Azure itself is rejecting the connection so he had to make an adjustment to a VI program to handle it. I'll give you his contact info if interested but I would try Kevin's idea it sounds very promising.

It seems like the linked server approach with a view will work.