Forum Discussion
Cloud data source refresh is not allowed in gateway setting
Any chance you got a response back from MS on this or figured out what the issue was?
I have a feeling my environment has been opted into the Gateway for Sharepoint mentioned above and I can't for the life of me get it to authenticate after the latest Gateway update.
Yes, we talked to Microsoft about it. And we solved it together!
I don't know the architecture on MS, but the solution is a bit strange (for me):
As soon as data from the gateway (internal SQL DB) and data from the SharePoint / cloud connection are combined within the report, the gateway needs a firewall activation to the cloud connection, in our case to our SharePoint. After that, it works without any problems.Why it has also worked before without this firewall activation (only if you don't mix the data in the report) remains a mystery to me about the MS architecture.
And: The fact that the red cross can still be seen in the screenshots gateway section is normal, according to MS.
Case closed 😀
Greetings,
Lars
The support has sent these infos to us:
#######################################
- The gateway server is unable to access the Sharepoint site, which is a requirement for this functionality. Is is enough to open the connection from the gateway server to the Sharepoint URL via TCP 443.
- Please find the following documentation about communication settings that are required for the gateway to work correctly.
Adjust communication settings for the on-premises data gateway | Microsoft Learn
Specifically see this section outlining endpoints that are essential for the gateway to function correctly (including refrence to login.microsoft.com):
- You can carry out a network ports test on the gateway server (described above) to check what it does / does not have access to.
#######################################
After that it works. Hope it helps!
Greetings,
Lars
Yes, we talked to Microsoft about it. And we solved it together!
I don't know the architecture on MS, but the solution is a bit strange (for me):
As soon as data from the gateway (internal SQL DB) and data from the SharePoint / cloud connection are combined within the report, the gateway needs a firewall activation to the cloud connection, in our case to our SharePoint. After that, it works without any problems.
Why it has also worked before without this firewall activation (only if you don't mix the data in the report) remains a mystery to me about the MS architecture.
And: The fact that the red cross can still be seen in the screenshots gateway section is normal, according to MS.
Case closed 😀
Greetings,
Lars
Hey lars-kettermann, the issue you face is a bit obscure, and it concerns how the mash-up engine works when you publish a semantic model into the service.
If you combine sources in a query, and one requires a Gateway, then all connections in that query must go through the same Gateway. The explanation can be found in the "data exfiltration" data flow documentation:
"If a dataflow needs to access a network isolated data store (and is therefore bound to a gateway), all data access is then required to flow through the gateway."
https://learn.microsoft.com/en-us/power-query/dataflows/data-exfiltration-best-practices
Although the document is about dataflows, this is how the mashup engine behaves for any power query program, no matter if this comes from a PBI semantic model.
I hope this helps!