Infrastructure components
Use this inventory to plan a deployment review, then compare it with the Azure resources actually deployed. Services and settings vary by release and operating model.
Application services
Azure Functions host the public APIs and background workflows. Separate applications own ingest, customer operations, staff operations, workflows, MCP, proof submission, and other bounded services.
Validate:
- managed identity and least-privilege role assignments;
- authentication middleware and public route exposure;
- network ingress, egress, private endpoints, and DNS;
- health and readiness probes;
- scale limits and database connection budgets; and
- deployment slots, release artifacts, and rollback procedures.
Data stores
VeriProof uses PostgreSQL for customer and operational records. Some deployments can use Azure SQL Database Ledger as the selected proof provider.
Validate:
- tenant and application scope at the service and database layers;
- encryption at rest and in transit;
- database roles and grants;
- backup, restore, retention, and deletion;
- connection pooling and scale assumptions; and
- ledger digest storage and verifier access when Azure SQL Ledger is selected.
Keys and secrets
Azure Key Vault stores supported secrets and cryptographic key material. Applications use managed identities and secret references where the release supports them.
Name the key owner and review rotation, recovery, emergency access, version selection, and audit logs. Use the release runbook for secret names and reference formats.
Storage and queues
Azure storage services support background work, retained artifacts, and selected evidence workflows.
Check retries and handling for messages that repeatedly fail. Review storage access, lifecycle policies, reconciliation jobs, and any required immutability settings.
Do not assume that every container has a locked retention policy.
Portals and documentation
Customer and staff portals are separate web applications with API-backed data access. Hosting, edge, content-security, and custom-domain controls depend on the deployed architecture.
Validate the generated configuration, API origins, content security policy, authentication redirect URLs, and failure behavior in the target environment.
Monitoring
Application Insights and Azure Monitor can collect service telemetry and alert on operational failures. Customer-managed Azure customers own the monitoring configuration in their subscription.
Avoid sending secrets, prompt content, personal data, or raw evidence to operational logs.
Proof providers
The selected provider is either Solana or Azure SQL Ledger.
- Solana uses a public network reference and approved RPC access.
- Azure SQL Ledger uses append-only ledger tables and protected digests.
Confirm who operates and pays for the selected provider resources under the deployment agreement. In Customer-managed Azure, include resources in your subscription in the cost review.
Also check data exposure, verification access, provider health, and reconciliation. These affect evidence availability independently of cost.