Re: Due to organizational policies, you can't down...

karthi · ‎03-21-2022

Dear Team,

I have a simple flow which triggers when new SharePoint list item is added.

I had saved the Logo in site document library and images are saved in the same document library.

Flow is behaving some weird, sometimes it runs successful and some time it gives error "Due to organizational policies, you can't download these resources from this device"

Im the owner of the sharepoint site and i can able to view and download the images from the document library.

If there is some restriction due to policies, flow shouldnt run successful. I tried with duplicating the same flow and the same behavior is found.

can you please support on how to fix this issue. Thanks in advance for your support.

leo85 · ‎03-21-2022

Hi @karthi ,

the error message says that there is an organizational policy which restricts access. Apparently this is a conditional access policy. Conditional access provides access to file, sites, etc. based on certain conditions (e.g., location, device, etc.). This access has nothing to do with you permissions on the SharePoint site (site owner).

The conditional access will handle the request differently if you access the image via your browser and via flow.

I'm not sure if flows are always the same (in regards to conditional access) or different runs may have different parameters.

Check in your tenant (company) what conditional access policies are active and if they may affect your flow. Maybe you will also find relevant info in the trigger output.

Regards,

Leo

Dhanesha1 · ‎07-27-2022

Hi Karthi, Hope all is well on your side.

I am experiencing the same issue. Weird thing is that I never got it previously.

Did you find a fix for that?

Thanks.

Regards,

Dhanesha.

garavata · ‎08-30-2022

Same here. We are also seeing the issue running a flow that says we have a policy in place. The flow was working until around August 10th 2022

ScottVPeters · ‎08-31-2022

Hello @karthi @garavata did you find a resolution? I am experiencing this issue randomly after months of successful usage! Thank you for your time!

garavata · ‎08-31-2022

So far I have not been able to fix this for the user. My last recommendation to the person was to remove his connections and re-establish them. He had just cleared out all of his cached passwords from Credential Manager and re-signed into Office 365. Still waiting to hear if that helps. Keeping my fingers crossed! Will post here if it does.

rpallapothu · ‎08-31-2022

We are facing same issue... Did re-establishing connection worked for the user ?

garavata · ‎09-01-2022

I have not heard back yet, but I did send the person a follow up to see if it did. I hope so. Once I know for sure, I will post an update.

ScottVPeters · ‎09-01-2022

As an update, I troubleshooted with an IT colleague within my company's MS365 support team and even when testing a simple flow he created referencing his SharePoint, I still received the error as above though he did not. He thinks it's an isolated issue related to my MS account and is looking further into it..might need to have MS support look into it as well.

leo85 · ‎09-02-2022

Hi @ScottVPeters , @garavata, @karthi

did you check your tenant's conditional access policies? Conditional access can target specific groups or individual users to prevent them from using specific resources. So flows may work for one, but not for another user.

If the error message contains conditional access as in the OP, this should be the first place to look.

Regards

Leo

------------------------------------------------------

If my answer solved your issue, please mark it as a solution.

If what I wrote helped you, please give it a thumbs up.

garavata · ‎09-02-2022

Thank you, yes, I did ask our Global Tenant Administrator and he said that our current conditional access policy setup should not be preventing our users from running their existing flows. He is the one who suggested re-establishing the connections. Appreciate the thought!

garavata · ‎09-06-2022

Hi there! Following up to let you know that re-establishing the connection for the PowerAutomate flow worked. The user was able to successfully run the flow without any errors.

ScottVPeters · ‎09-06-2022

Update: Switching the SharePoint site sensitivity from "C2" to "C1" (not sure if this is similar across the board) allowed my flow and action to run successfully..this is still a headache as I prefer higher site sensitivity. I was told that this might be related to the document's MIP setting however I'm still looking into this to see if I can set this document sensitivity within PowerAutomate (as I'm creating the document in Flow).

Additionally, I believe the error is that the flow does not "trust" my device (apparently I have some account related issues still under review by IT) and does not allow me to call on items in a "C2" level SharePoint (I was told my organization has additional steps to take to allow "C2" SharePoints to interact with untrusted devices). Still a massive headache for something that was successfully running for months before!

ScottVPeters · ‎09-06-2022

Ahh lucky..I attempted to re-establish my connection on this action, as well as recreate the action alltogether..it still failed but I found that having another user connect to the action let it run successfully!

garavata · ‎09-06-2022

Did you try clearning out your Windows Cached Credentials? I had the user do that first and then re-establish the connections.

ScottVPeters · ‎09-06-2022

Thank you for your suggestion..I went through and removed some authentications but I didn't see anything specifically for MS O365..tried a reboot after that but still no success on the flow.

Dhanesha1 · ‎09-07-2022

Hi @ScottVPeters .

Had same issue. What worked for me was:

Re-establish connection for Populate word action
Select a new/past template from documents
Then re select the template that you wished to work on.

ScottVPeters · ‎09-07-2022

Thank you for your suggestion & support, unfortunately I am not using word action, but rather trying to pull in file content of a PDF.

Dhanesha1 · ‎09-07-2022

Okayy sure. Got this also on file content, i did re establish connection and it worked.

ScottVPeters · ‎09-07-2022

SOLUTION: simply reconnecting my connection to this (Get file content using path) action did not previously work. After @garavata's suggestion, I opened my local credential manager and removed some cached MS credentials (then restarted computer), then reconnected my connection on this action and it now ran successfully..will continue to test in other flows. Thank you all for your patience and support!