Forum Discussion
Unable to connect to domainSQL Server with Windows Auth via data gateway on non-domain server in DMZ
The technician from a support call with Microsoft eventually stated it was required to install the gateway on a domain-connected server to enable Windows Authentication modes. I'm not sure if the Microsoft technician was just opting for an 'easy' answer or it's a genuine requirement that is not documented anywhere that I saw. So we decided it was an 'undocumented requirement' of the Gateway for that architecture and security configuration.
Hi pauste1,
When you create a SQL Server data source under data gateway use Windows authentication, make sure the domain account you entered is the same as the account you used in ODBC data source.
By the way, please update the data gateway to the latest version. If issue persists, please run the Fiddler with HTTPS encrypt enabled then repeat the steps to create SQL data source in data gateway. Share .saz file with us.
Best Regards,
Qiuyun Yu
Hi v-qiuyu-msft
Yes, the domain account was the same, and the ODBC server name and database were the same.
I updated the data gateway to the latest version and there was no change in behaviour.
I ran Fiddler with HTTPS decrypt enabled and there was no traffic captured. A colleague also ran Fiddler with HTTPS decrypt enabled and he captured no traffic either while testing the data sources from the PowerBI.com Gateway service. A technician from Microsoft was on a Skype screen-sharing session with us and offered no other suggestions regarding Fiddler to capture web traffic, and finished the call stating we should just install the data gateway on a server in the domain.
So our understanding at the moment from the technician at Microsoft, and the documentation online, is that it is an undocumented requirement that the server hosting the Data Gateway must be connected to the domain in order to use Windows Authentication in the data source.
Has anyone else experienced this limitation?
Hello Pauste1, did you found any solution on the above Problem? I have the same problem with these services!!!
The technician from a support call with Microsoft eventually stated it was required to install the gateway on a domain-connected server to enable Windows Authentication modes. I'm not sure if the Microsoft technician was just opting for an 'easy' answer or it's a genuine requirement that is not documented anywhere that I saw. So we decided it was an 'undocumented requirement' of the Gateway for that architecture and security configuration.
