We have 2 separate SharePoint Servers (one demo and one production). I have installed an on-premises data gateway in a PC that can access both servers fine. I can use the exact same domain user to connect to both sites. I'm not an administrator, but I have authoring rights in the sites of both servers.
When I try to log in to create the trigger step for the demo / test server, everything works fine:
However, If I try to create the same step connecting to the production server, Flow can't find the URL:
Could there be something disabled in the production server that is enabled in the demo server that is blocking this?
Other notes to consider:
I have worked with our SharePoint Administrator and we have done the following tests:
- Created a new Gateway using his Administrator account login credentials. This gateway was visible to me in the make.powerapps.com site under the correct environment and region. This gateway was also visible to my administrator within his Flow portal (unitedkingdom.flow.microsoft.com).
- My SharePoint Administrator created a similar flow as above within unitedkingdom.flow.microsoft.com and he created a connection using his administrator account and his new gateway.
- The similar problem happened: 1. Demo site connects successfully and can show all the lists/objects in the Folder Id filed and recognises the URL of the demo site. 2. For the Production site it can't find the URL at all.
- Note: My SharePoint Administrator has full access rights to both production and demo servers. He also has full access to the Central Administrator portal of both SharePoint servers.
We have ruled out any connectivity issues between the PC where the Gateway resides, and the Flow Servers - The connection tests from the Gateway App are successful, and make.powerapps.com can see the Gateway and shows the status as Online. If we try to open a web browser and browse to both SharePoint subsites they are accessible with the administrator accounts as well in the
Gateway PC so we really don't know what's going on.
As an additional test I (as a .NET developer), tried a quick console application using SharePoint CSMO (https://docs.microsoft.com/en-us/sharepoint/dev/sp-add-ins/sharepoint-net-server-csom-jsom-and-rest-...).
When I tested it, the demo server successfully retrieved the lists from the subsite, however when testing the Production server, it just showed:
System.Net.WebException: 'The remote server returned an error: (401) Unauthorized.'
Furthermore, the reference documentation advises that the API tries to access the website in this form:
so this is what happened when I tried to access the demo site api (from a web browser):
and this is what happened when I tried to access the similar subsite api in the production server (from a web browser):
I'm not sure if this has anything to do with Microsoft Flow (Power Apps), but I suppose if Flow uses a similar technique to access the site then this might be part of the problem? (Note that Flow is not saying anything about access denied, it just says that it can't find the URL as seen above in the first screenshots).
I've also noticed a clear difference between our test server and our production server. Our test server uses standard Windows Authentication to log in, however our Production Server uses ADFS, however, we can log in to both servers using the same user@domain and password - Not sure if this is a problem for Microsoft Flow? - It still doesn't explain why Flow is saying that the URL doesn't exist, it should be showing a different error?
We were never able to fix it 😞 - I mean, possibly something needs to be done by the Power Apps developers to fix this issue in the code / network authentication modes etc, if no one has been able to contribute a solution to the problem in over a year 😑
I just had this problem and did 2 things, but I'm not sure which one fixed it.
Learn how to create your own user groups today!
Check out the new Power Platform Community Connections gallery!
Join us, in-person, December 7–9 in Las Vegas, for the largest gathering of the Microsoft community in the world.