Please correct me if wrong, if my surmise that Microsoft Power Automate Cloud Flow is for internal employees?
I am an external employee working in Backoffice but assigned a weekly task of saving Attachment every Friday late night which unfortunately is only achievable Monday late morning due to no WFH resources and health reason.
Otherwise, I need expert opinion before giving up Automation and continue current practice which incurs two days delay due to weekend. Automation is not forthcoming due to Network Drive Folder. where a File is saved. SharePoint would be better, but this is not my scope and I have to request change for such a trivial task. For Power Automate Cloud Flow, Network Drive is a complex solution and requires dedicated environment and on-prem data gateway which I need to request.
The task I need to do is updating a Network Drive Folder by saving attachment ASAP when an Outlook 365 Email Arrive Friday night to overcome my unavailability to login Saturday and Sunday. APPENDIX Why you should avoid folders in SharePoint — Gravity Union
YouTube demo of Save Email to File System requires Data Gateway in Local Computer?
defining custom path to Enterprise Network Drive Folder where email attachment is to go.
There is alternative as contributed by DamoBird365; do I still need to create File System?
https://pnp.github.io/blog/post/save-an-email-attachment-to-a-custom-path-with-power-automate/>
thanks, it turns out to be a complex solution as per my IT
Thanks, for Windows 10 Enterprise Client, my further questions:
(1) application for DLP Policy change requires Environment Name and URL; how to find out?
(2) since additional Install of on-premises data gateway to download
(A) is local computer running and login required?
(B) how to get Windows Server 2012 R2 for Windows Client?
YouTube demo of Save Email to File System requires Data Gateway in Local Computer?
Thanks Rimmon,
I made correction by selecting "New on-premises data gateway" as per your advise "It seems that you haven't selected the gateway and set up a connection yet, using the file system connector asks us to set up the gateway" .
I am now getting following error
Failed to create connection for connection id
e503-4dIc-agbc-II 732Ba7eOB2'. Connection creation/edit of 'shared_filesystem' has been blocked by
Data Loss Prevention (DIP) policy 'DLP Personal Productivity'.
Unless I can view my DLP policy, I am waiting for my IT staff to advise. I still have trouble understanding extra access-granting from IT for saving to Network Drive Folder which I can manually save attachment to.
In case I am not authorized to have DLP setting for File System, how can I develop a Flow for someone else who is authorized? In other words, I develop this Flow to be used by my Supervisor who I believe have more Access Rights to File System; my Supervisor do not have the skill to create this Flow even though this is a Template.
Hi @SunnySchindler ,
Since your error is a DLP error, I suggest that you check the DLP settings of your environment. If the configuration is correct, check another issue I found in your screenshot:
It seems that you haven't selected the gateway and set up a connection yet, using the file system connector asks us to set up the gateway.
Here's a video tutorial I found for you on how to set up a gateway along with the official documentation.
Install an on-premises data gateway | Microsoft Learn
Once the connection is created, we can select the folder where the email attachment is stored.
Hope this helps.
Rimmon
Thanks, I also need help for Windows 10 Enterprise Steps Recorder App to disclose information for Internal Staff (Technical Support). Example is to record data entry information for File System Field User-Name; as-is, this is not visible (Screenshot attached).
Otherwise, I have to post-process Steps Recorder Output to show my internal Tech Support that my data entry information is correct.
Thanks, I need help to understand why additional security measure is needed for Network Drive. There is no prohibition to save to OneDrive.
Hi @SunnySchindler ,
The issue shows that the connector for this action is prohibited by a DLP policy, I suggest you go to the Power Platform Admin Center to check the configuration of your environment's DLP policy or get in touch with your administrator to modify the DLP configuration for your environment.
Best regards,
Rimmon