Skip to content

Teardown

The current operator does not expose an automated teardown command. Plan teardown with your Azure administrator and Sprig support so ownership is verified immediately before each destructive action.

A complete teardown covers:

  1. Platform resources. The platform resource group contains the gateway and DAB Container Apps, metadata and package storage, the shared SQL resources, the certificate vault, and the dedicated release registry.
  2. Entra. Remove the installation’s platform API, CLI, gateway, connector, and OBO applications plus its users and operators groups.
  3. The Fabric application, if you created one. Enabling Fabric sources requires an application and service principal that you register yourself, so the installer does not own it and no ownership tag identifies it. It is a separate object from the connector application in the previous step. If you followed Expose an existing database to enable Fabric sources, remove that application, and confirm its entry under Enterprise applications is gone as well. Also revoke the database-side grant you made on the Fabric side, since that grant names the serving identity rather than the application.
  4. Subscription budget. Remove the installation’s monthly budget.

Deleting the platform resource group also deletes every imported image. Export audit data, certificates, or images that must survive before approving deletion. Use the sprig-managed ownership tags and the active operator context as evidence; a matching name alone is not ownership proof.

Claude Code users forget the MCP sign-in with claude mcp remove sprig. Claude access ends when the tenant administrator removes the connector and organization skills.

Deleting the platform resource group leaves its Key Vault in Azure’s 90-day soft-delete state. A later installation may need the vault recovered or purged before its deterministic name can be reused. Purging is irreversible; do it only after confirming that no certificate or secret must be recovered.