Secure Exchanges SDK Documentation
Search Results for

    Show / Hide Table of Contents

    Azure Functions Deployment

    This page describes how to deploy a Function App that uses SecureExchanges.Signature.NetCore to certify PDFs with headless Chromium.

    Because Chromium cannot run inside the Azure Functions Windows sandbox, deployment must target a Linux container on a Premium plan. The Dockerfile, Chromium system dependencies and environment variables are described on the dedicated Linux + Docker page; this page focuses on the Azure-specific setup (registry, managed identity, image selection, restart).

    Prerequisites

    • Azure Functions Premium plan in container mode (Linux).
    • Azure Container Registry — Basic SKU is enough for a single image.
    • System-assigned managed identity on the Function App with the AcrPull role on the ACR.
    • A Docker image built from your Function App using the Linux + Docker Dockerfile.
    Tip

    A working sample is available on GitHub: AzureFunctionsSignature.netCore.

    Steps

    1. Create an Azure Container Registry. A Basic SKU registry in the same region as your Function App is sufficient. Admin user is not required when you use a managed identity.

    2. Build the Docker image from your Function App using the Dockerfile described in Linux + Docker. Prefer ACR Tasks (az acr build) to build server-side — no local Docker daemon required.

    3. Enable a system-assigned managed identity on the Function App and grant it the AcrPull role on the ACR. Then configure the Function App to use that identity when pulling from ACR.

    4. Point the Function App at the new image.

    5. Restart the Function App. It will pull the image from ACR and boot.

    Tip

    The repo ships a reference script build-and-push.ps1 that automates step 2 (build the image with az acr build and push it to ACR). It is documented alongside the Function App source code.

    App settings reference

    Setting Value Reason
    SE_DISABLE_AUTO_DOWNLOAD 1 Chromium is already in the image; block runtime re-download.
    FUNCTIONS_WORKER_PROCESS_COUNT 1 One Chromium instance per Function App worker — lower RAM footprint on EP1.

    See Also

    • Sample project on GitHub — full working Function App
    • Linux + Docker — Dockerfile and Chromium system dependencies
    • PDF Certification — SDK usage and code examples
    In this article
    Back to top Secure Exchanges Inc. - Documentation