← Benedict PDF
FREQUENTLY ASKED QUESTIONS

Benedict PDF: pricing, licensing, deployment, and support.

Answers about how Benedict PDF is licensed, deployed, and supported — and which version to choose.

Benedict PDF is a free, open-source Azure Function for Microsoft Power Platform. It watermarks, password-protects, and restricts permissions on PDF documents — called from Power Automate or Power Apps, running entirely inside your own Azure subscription.

Yes. Benedict PDF is free and open source under the MIT License with Commons Clause, with no required subscriptions or per-user licenses. If it saves you time, a voluntary contribution via Stripe helps fund further development, but it's entirely optional.

v1 uses a shared function key, ships with a working sample Power App, and deploys in minutes — a good fit for learning, personal use, or small-scale deployments. v2 adds Entra ID authentication with per-user access control, granular permission restrictions independent of the open password, and enforced size/rate limits, at the cost of a more involved setup. See the comparison on the Benedict PDF page for the full breakdown.

If you want the fastest path to something working, or don't need identity-based access control, start with v1. Move to v2 when you need real control over who can call the function, or need to restrict what recipients can do with a document beyond just requiring a password to open it.

v1's shared function key works the same for everyone, so a sample app can be imported and run immediately. v2's Entra ID authentication requires registering an application in your own tenant and building a custom connector referencing your tenant's own client ID and secret — a packaged sample's connector would reference our tenant, not yours, and simply wouldn't work once imported. v2 ships a step-by-step Implementation Guide instead, covering deployment, Entra ID setup, and building your own connector.

Yes, on both versions.

An Azure subscription to host the Function App, and Microsoft 365 with Power Platform access to call it from Power Automate or Power Apps. Building a custom connector — required for v2, optional for v1 — needs a Power Automate Premium or Power Apps Premium license.

Yes — the MIT License with Commons Clause lets you use, modify, and integrate Benedict PDF freely. The one restriction: you can't resell Benedict PDF itself, or a minimally modified version of it, as a standalone product or service.

Benedict PDF runs as your own Azure Function inside your own Azure subscription. Benedict Corp. doesn't operate any infrastructure your documents pass through, and has no access to a deployed instance.

Report bugs or ask questions via GitHub Issues on the v1 or v2 repository. For a custom Power Platform solution built around Benedict PDF, contact us directly.

Don't see your question answered here?

Ask us directly