Service settings
Find each setting in the selected release’s infrastructure templates and service configuration. Startup validation checks required values, but it does not replace a working connection test.
Find the setting source
| Group | Purpose | Source |
|---|---|---|
| Deployment | Operating model and environment identity | Release infrastructure parameters |
| Authentication | Issuer, audience, provider, and supported emergency policy | Portal and MCP service startup |
| Data | Service-specific database connections and pool limits | Infrastructure outputs and service configuration |
| Key Vault | Vault URI and supported secret references | Infrastructure templates |
| Agent integration | Portal, API, ingest, MCP, OAuth, and docs addresses | Customer portal and MCP deployment settings |
| Proof provider | Solana or Azure SQL Ledger configuration | Proof anchoring services |
| Workflow schedules | Background processing and reconciliation | Service-specific schedules |
| Monitoring | Application Insights, health, and alert inputs | Azure monitoring configuration |
Customer-managed Azure
Some configuration uses Hybrid for Customer-managed Azure. Follow the exact value and casing requested by the release template; do not substitute the customer-facing name.
The public SDK contract uses one endpoint and does not define EnterpriseHybrid, LocalFirst, or Disconnected modes.
Secret handling
Use Key Vault references or the release-approved secret delivery mechanism. Keep these values out of source control, build logs, screenshots, issue descriptions, and documentation examples:
- database credentials and connection strings;
- application SDK keys and Function host keys;
- OAuth client secrets and refresh tokens;
- signing and encryption keys;
- proof-provider private keys; and
- third-party integration credentials.
Validate configuration
Check each deployed service without exposing its secrets:
- Compare its effective settings with the selected release manifest.
- Confirm that secret references resolve through the intended managed identity.
- Check issuer, audience, resource, callback, and base-URL values.
- Run health and readiness checks.
- Exercise an authorized request and a request that must be denied.
- Retain redacted results with the deployment record.
Do not use a repository local.settings.json as a production template. Local files can contain development-only authentication and service endpoints.