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
The feeling is mutual. Hard to help if nothing is really visible.
Whenever you attempt to combine data from different sources you wake up the firewall dragon. What are the privacy levels for these two sources?
(Yours is "just" an append. in case of merges you actually need to create an actual gateway connection for your SharePoint source (!!!) and that is an irreversible step - the sharepoint source will continue to need that gateway connection for all eternity even if you remove your SQL data source)
Show your gateway config.
"What are the privacy levels for these two sources" > Normally organisation, but i have already testet all possible combinations.
"Yours is just an append. in case of merges you ...": What do you mean by merges? Joining instead of appending? From my point of view it can't get worse 😉
What i don't get is, that everything works perfect with exactly the same configurations, but only if i append / mix those source inside the report after importing suddenly "The credentials provided for the SharePoint source are invalid". For me this is completely unlogical ☹️
I'm giving up for now and will send MS a ticket. Thank you for your help and patience!
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.
No, this is not the case. Of course, we had ticked these boxes right at the beginning and that is not a solution in this case.