---
title: "Teams Disconnect"
method: DELETE
path: "/v1/integrations/teams/connection"
tags: ["integrations"]
---

# Teams Disconnect

`DELETE /v1/integrations/teams/connection`

## Request

- Base URL: `https://api.patricia.app` (the document declares no server; this is the origin it was published from)
- URL: `https://api.patricia.app/v1/integrations/teams/connection`
- Auth: HTTP bearer

Disconnect this tenant's Teams workspace and free the Teams slot for a different one.

Scoped to the bearer principal's tenant, so a caller can only ever disconnect their own
workspace. Idempotent: a tenant with no Teams rows gets ``{"disconnected": false}`` and a 200,
because "there is nothing to disconnect" is the outcome the caller asked for, not an error.

What this removes is Patricia's side of the connection: the workspace identity and the
installation, including the encrypted bot credentials. It does NOT uninstall the Patricia app
from Microsoft Teams and it cannot — that is an action inside the customer's Microsoft 365
tenant. The dashboard copy says so, because an admin who expects the app to vanish from Teams
and finds it still there will assume the disconnect failed.

Returns 409 when an armed autonomous grant still references the installation
(``WorkspaceSlotReleaseBlocked``); nothing is removed in that case.

## Headers

- `X-Tenant-Id` string, nullable

## Response `200`

Successful Response

- object

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/patricia/apis/patricia-api.md) · [All operations](https://skmtc.dev/patricia/apis/patricia-api/llms.txt) · [OpenAPI document](https://skmtc.dev/patricia/apis/patricia-api/revisions/0dfb44495ea1?raw)
