The PDFNet SDK relies on several extension modules to support features such as HTML‑to‑PDF, CAD‑to‑PDF, and Microsoft Office‑to‑PDF conversion. These modules run as separate executables launched by the SDK.
When deployed within an Azure Function, these executables are typically published to the C: drive. However, Azure Functions enforce restrictive permissions on the C: drive, preventing the extension modules from executing there.
To ensure the modules run correctly, they must be copied to and executed from the function’s temporary, ephemeral storage location on the D: drive. We recommend using the following path:
D:/local/Temp
Running the extension modules from this directory ensures they have the necessary permissions during function execution.