Docufindr

What this plan includes:

• Automated Infrastructure: Provisions required compute, container runtime, networking, and storage components using native ARM templates.
• AI Model & Search Engine: Deploys core document retrieval, indexing, and LLM inference pipelines.
• Scalability & Security: Pre-configured virtual network security rules and identity integrations for enterprise data isolation.

Important Deployment Prerequisites

This application utilizes advanced AI models to process your data efficiently. To support these AI capabilities, the deployment provisions a dedicated GPU virtual machine within your Azure environment.

By default, Azure restricts the quota for GPU virtual machines on new or standard subscriptions. Before deploying this application, you must ensure your subscription has sufficient quota, otherwise the deployment will fail.

Please verify or request the following Compute quotas in your Azure Subscription for your desired deployment region:

Standard NCASv3_T4 Family vCPUs

• Required Quota: 8 vCPUs
• Purpose: Required for the single GPU node that runs the core AI inference services.

*

Standard Dv7 Family vCPUs

• Required Quota: 8 vCPUs
• Purpose: Required for the system nodes (2 nodes, 4 vCPUs each) that run the application backend and web interfaces.

How to Request a Quota Increase in Azure

• Navigate to the Azure Portal.
• Search for "Quotas" in the top search bar and select the service.
• Select Compute and filter by your target deployment region.
• Search for the quota names listed above. If your current limit is below the required amount, select the item and click Request Quota Increase.

Required Azure Account Privileges

• To successfully deploy the DocuFindr Solution Template, the user performing the deployment must have elevated privileges in the target Azure Subscription or Resource Group.
• This is required because the automated deployment script configures essential security policies, including granting the Kubernetes cluster secure access to pull container images and authorizing deployment scripts to execute.
• The customer must have ONE of the following role configurations assigned to their Azure account for the target Resource Group or Subscription:

Option 1 — Recommended & Simplest

• Owner role

Option 2 — Principle of Least Privilege

• Contributor role — allows creation of AKS cluster, virtual networks, and managed identities
• AND the Role Based Access Control Administrator role (formerly User Access Administrator) — allows creation of the necessary Role Assignments

Important: If the deploying user only has the standard Contributor role without RBAC administration rights, the deployment will fail during the role assignment phase.