Forum Discussion
SQL Azure Import Data Refresh
I finally figured it out: the connection FQDN included the word "secure".
This won't allow server-side refresh: <database name>.database.secure.windows.net.
This will allow servers-side refresh: <database name>.database.windows.net
Both FQDNs seem to work otherwise. The 'secure' setting was used to enable auditing, but I don't think it is required anymore.
Problem solved. Thanks everyone.
-Jeff
Update: I have confirmed Power BI requires a personal gateway in our main azure subscription with a brand new SQL database and test database. In a separate test subscription with exactly the same Azure SQL setup, a personal gateway is not required.
There is something specific about our subscription that is causing this problem. I'm at the end of my ideas to troubleshoot, and so we are opening a Microsoft ticket.
I finally figured it out: the connection FQDN included the word "secure".
This won't allow server-side refresh: <database name>.database.secure.windows.net.
This will allow servers-side refresh: <database name>.database.windows.net
Both FQDNs seem to work otherwise. The 'secure' setting was used to enable auditing, but I don't think it is required anymore.
Problem solved. Thanks everyone.
-Jeff