My company is looking into the Adobe PDF service connector for Microsoft Power Automate. They are concerned that Adobe will be sent information/data when the connector is used. Can someone please explain, in the most basic terms possible, how this connector interacts with Power Automate and Adobe; so that it can be explained to our decision makers? They are requesting this information as well as any architecture documentation on the connector.
For both PA and non-PA solutions, the flow works like so - imagine a scenario of converting Word to PDF.
A call is made to the API saying, I need to upload a Word doc.
API says, cool, send it here.
You send it there. That file is stored by us, but we do not have any access to it. It will automatically be deleted in 24 hours. No one has access but you.
You kick off a Word->PDF job.
When the job is done, the PDF is stored like your WOrd document - we have it, but we don't have access to it, only you. You can download it, we can't. In 24 hours, it's deleted.
Now, here's where things get a bit different. Our REST API has an option to delete assets. So if you were using the REST API, you could "clean up" when done and not wait for the 24 hours. You can't do that with the PA connector unfortunately.
You *can* do REST calls in PA, but the PA connector abstrtacts so much that I don't think you would have access to the ID of the uploaded Word doc or PDF doc to call delete. In PA if you wanted to do the "immediate cleanup", you would need to skip the connector and do it all via REST. I've done this and it's possible, just not via the connector.
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
AdChoices