For those who may get stuck with this.
As i am hosting my sql server on Azure it was difficult to see what IP Range the inbound connection is coming from.
I enabled login logging on the sql server instance for both failed and successful login attempts.
I then opened a test * in my inbound firewall from any data source to my sql server. In the sql server log i was then able to see what the ip address that was trying to login from Qlik Cloud.
Clear from the documentation that they are missing a range of IP Addresses coming from Qlik Cloud. I added 126.96.36.199/28 to my whitelist and the connection worked. hope this saves somebody the amount of hours i put it into it....
looks like new ip ranges are being added to cloud with no addition to documentation in link above.
when using the beta of the SQL Server connection these must be white listed within the firewall where the database resides.
mto great if you could have somebody look at the online documentation.
the ranges i have added that work are: