FAQ

VaultPDF is a deterministic document rendering engine that generates structured PDFs from JSON data. It runs entirely inside your Microsoft tenant, enabling secure document generation for enterprise business applications such as Dynamics 365, Dataverse, SharePoint, and other internal systems.

No. VaultPDF is designed as a no-egress document engine. All rendering and document processing occur inside your Microsoft tenant, ensuring full data privacy. See the Architecture page for a full breakdown of the no-egress model.

VaultPDF runs in Azure Functions inside your tenant. It integrates with SharePoint document libraries for template management, document storage, and metadata tracking.

Yes. VaultPDF supports both real-time rendering and asynchronous processing using Azure Service Bus queues, which are optional and configurable per tenant. See Pipeline for queue architecture details.

VaultPDF itself is not a hosted SaaS platform. Since it runs entirely inside your Microsoft tenant, it inherits Microsoft 365 and Azure security, compliance, and data residency controls, including SharePoint Online permissions and Managed Identity access.

Documents stored in SharePoint leverage tenant-level permissions. Optional PDF password protection is also supported for sensitive documents. Audit trails can be stored in SharePoint lists or document libraries if enabled.

Yes. VaultPDF supports deployment in Microsoft cloud environments that allow Azure Functions and SharePoint Online, including government and regulated cloud environments where these services are available.

VaultPDF connects to structured JSON data from:

• Dynamics 365 / Dataverse
• SharePoint document libraries
• SQL and internal systems

It interprets schemas for deterministic PDF rendering and maps fields, hierarchy, and layout constraints automatically.

Yes. Rendering jobs can be:

• Direct / real-time: HTTP-triggered, immediate response
• Queued: Service Bus triggered for asynchronous or high-volume batch workloads

Queueing is optional and configurable via tenant settings.

Templates are stored in SharePoint libraries, which provide built-in version history, audit trails, and permission management, giving full visibility into changes over time.

VaultPDF provides a system status report PDF requested via GET /status. It includes engine health, configuration checks, and monitoring information. For monitoring tools, append ?ping=true to receive a status PDF with HTTP response codes reflecting system health (200 healthy, 501 unhealthy).

VaultPDF uses tenant-based licensing with two tiers:

Licenses can be updated or replaced per tenant. Expired licenses are automatically disabled.

Yes. VaultPDF allows multiple license tiers to be assigned to a single tenant, such as a trial license alongside an enterprise license.

Usage tracking is optional and mainly applies to Direct Render or Trial customers. Enterprise deployments running inside the tenant are effectively unlimited since compute and storage are controlled by the customer.

Templates are stored in SharePoint document libraries, benefiting from:

• Version history
• Permission control
• Governance via Microsoft 365

VaultPDF supports schema-driven templates rendering.

Yes. VaultPDF uses schema-aware rendering, which supports:

• Nested tables
• Overflow handling
• Hierarchical or dynamic data
• Deterministic layout generation

Yes. Templates can include logos and branding. Optional watermarks can be applied for both browser-rendered and function-rendered PDFs, with configurable placement, opacity, and angle.

Traditional PDF APIs focus on either static layouts or developer-intensive integrations. VaultPDF is designed as document infrastructure:

• Runs entirely inside your Microsoft tenant (no-egress)
• Handles structured data with deterministic rendering
• Supports workflows, batch processing, and tenant-bound security

This makes VaultPDF ideal for enterprise applications where compliance, scale, and control are critical.

VaultPDF supports complex tables, adaptive overflow, schema-aware layouts, and integrated workflows, making it suitable for enterprise-scale document operations beyond simple report generation. See Capabilities & Features for a full breakdown.