Skip to main content

Uninstall your Outermind Azure environment

If you deployed Outermind's Deploy-to-Azure template into your own Azure subscription, this page explains how to remove it completely. The template created an Azure AI Foundry resource (your model deployments) and, if you chose it, a Storage account, all in one resource group named outermind-<tenantShortId>-rg.

Follow the steps in order. Disconnecting first matters: if you delete the resources while Outermind still routes work to them, that work fails until you disconnect.

Just want to stop using one service, without deleting anything in Azure? See Disconnect a single service below instead of following the full uninstall below.

Models verified but not yet switched over, or a switch that failed? See Switch your models from the Azure Environment page below. You no longer have to walk the setup wizard again to switch or retry.

Disconnect a single service without uninstalling​

Go to Settings > Azure Environment to disconnect your Storage account or your Foundry models on their own, while leaving the rest of your Azure environment connected:

  • On the Data stores panel, a connected Storage account shows a Disconnect button.
  • On the Models & routing panel, connected Foundry models show a Disconnect button.

Clicking Disconnect opens a confirmation that lists exactly what changes before you confirm:

  • Storage: Outermind stops writing new logs and artifacts to your Storage account; new data goes to Outermind storage instead. Everything already in your account stays there and remains yours. Nothing is deleted in Azure.
  • Foundry: your agents stop using your Foundry models; each work type goes back to the model it used before you connected Foundry (or stops being armed to switch to it, if you had not switched yet). Nothing is deleted in Azure, and your Foundry resource and billing are unchanged.

Outermind can refuse a Foundry disconnect if a work type would be left with no model to use; the confirmation names the affected work type so you can assign it a model in model assignments and try again. Disconnecting Cosmos is not available yet.

This does not delete any Azure resources and does not remove the service principal Outermind uses, it only stops Outermind from using that service. To remove the resources themselves, follow the full uninstall below.

Switch your models from the Azure Environment page​

Once Outermind has verified your Foundry models, they are Armed: ready to switch, but not yet carrying any work. You can switch them from Settings > Azure Environment at any time, without walking back through the setup wizard.

  • On the Overview tab, the Models section shows "Armed, ready to switch" (or, after a failed attempt, "Switch failed" with the reason, in warning styling). Click Review and switch (or Review and try again) to go to the Models & routing tab.
  • On the Models & routing tab, the switch section shows the same preview the wizard's last step shows: which work types move to your Foundry, which are skipped, and the one-way consequence note. Click Switch now (or Try the switch again after a failure) to run it.

The switch runs in the background and the page refreshes automatically when it finishes. If you only have read access to settings, the section tells you to ask an administrator with permission to change settings to switch instead of showing the button.

A failed switch leaves your models on whatever they were using before, with nothing half-moved; retry with the same button once the underlying problem (shown in the failure reason) is resolved.

Before you start​

You need:

  • An Outermind Platform Admin account, for step 1
  • An Azure account that can delete resource groups in the subscription (Owner or Contributor), for steps 2 and 3
  • An Azure account that can remove role assignments (Owner or User Access Administrator), for step 4
  • A Microsoft Entra role that can delete enterprise applications (for example Cloud Application Administrator), for step 5

The commands below use the Azure CLI. Each step can also be done in the Azure portal.

Step 1: Disconnect in the Outermind console​

  1. Go to Workforce > Intelligence > AI Models.
  2. In Your setup, click Manage on the Azure AI Foundry tile in the Connections strip, then click the trash icon. The provider is removed straight away, without a confirmation prompt.

Outermind moves each work type that was using your Foundry models back to the model it used before you connected, or to your default model if it had none, so nothing is routed to your resource once it is gone. If you pointed a work type at a Foundry model yourself, or made one your fallback model, reassign it to another model first: Outermind refuses to remove a provider whose models are still in use.

Step 2: Delete the resource group​

az group delete --name outermind-<tenantShortId>-rg --yes

This deletes the resource group and everything in it, including anything you added to it yourself, and it cannot be undone; --yes skips Azure's confirmation prompt, so check the group's contents first with az resource list --resource-group outermind-<tenantShortId>-rg -o table. Anything already written to your Storage account belongs to you and is deleted with it, so export anything you want to keep first.

Step 3: Purge the Azure AI Foundry account​

Azure does not fully delete an Azure AI Foundry account straight away. It keeps a soft-deleted copy for up to 48 hours, which holds the account's name and your model quota. Reinstalling Outermind's template under the same name fails until that copy is purged.

List the soft-deleted accounts:

az cognitiveservices account list-deleted

Then purge each Outermind account (named om-...), once per location:

az cognitiveservices account purge \
  --location <location> \
  --resource-group outermind-<tenantShortId>-rg \
  --name <account name>

You can also purge in the Azure portal: Azure AI Foundry > Manage deleted resources > Purge. Choose the subscription and deleted account you want to purge.

Reinstalling after deleting your Foundry account​

Deleting the account or its resource group leaves a soft-deleted account for 48 hours. Deploying again under the same name during that window fails with FlagMustBeSetForRestore.

For a fresh installation, list and purge the deleted accounts with the commands in step 3 (or use the portal path above), then deploy again. Purging permanently removes the deleted account.

To recover an account you have not purged, check your deployment on the wizard's Verify step. When Outermind reports that your previously verified Foundry account is no longer visible, choose Restore my deleted Foundry account. This sends the restore choice only for that deployment. Restore covers every Outermind Foundry account in the deployment, so use it only when all of them were deleted and none has been purged; otherwise purge the remaining deleted accounts and deploy again. Restore requires the next template release; if Outermind says it is not available yet, purge instead and deploy again. If the account still exists, check the Outermind app's Azure role rather than purging or restoring it.

See Microsoft's recover or purge deleted resources guide for Azure recovery requirements.

Step 4: Remove any Cost Management Reader assignment​

Skip this step if you still use Outermind's Azure cost reporting.

If you gave Outermind's cost reporting application the Cost Management Reader role outside the resource group (for example on the subscription), remove it. Do this before step 5: these commands look the application up by its ID, which no longer works once its service principal is deleted.

az role assignment list --all --assignee <application (client) id> -o table
az role assignment delete --assignee <application (client) id> --role "Cost Management Reader" --scope <scope>

Step 5: Remove the Azure environment's service principal​

Deleting the resource group does not touch Microsoft Entra ID. Remove the application you approved for the Azure environment itself:

  1. In the Microsoft Entra admin center, go to Enterprise applications.
  2. Find the Outermind application you approved when you set up your Azure environment, and delete it.

Keep your other Outermind applications. Searching for "Outermind" also lists the applications the rest of Outermind uses, such as Mail & Calendar, SharePoint & OneDrive, and Teams. Deleting one of those stops that feature for your whole organization, so delete them only if you are leaving Outermind entirely.

Or, with the Azure CLI:

az ad sp delete --id <application (client) id>

Optional: remove the deployment record​

The portal leaves a deployment record at subscription scope. It holds no resources, but you can delete it:

az deployment sub delete --name <deployment name>

What stays in your Azure​

Removing the environment from Outermind never deletes anything in your Azure on its own: the resources and any data in them stay yours until you delete them in steps 2 and 3. Outermind keeps the rest of your workspace data in its own service, as it did before you connected.

If a model deployment goes missing​

You do not need to uninstall to fix a missing model. If a model deployment that your work types use has been deleted or renamed, those work types stop until the deployment exists again; Outermind never moves that work to its own capacity. Re-run your Outermind Deploy-to-Azure template, or recreate the deployment in Azure AI Foundry.