A Removal Was Refused

For how removals work end to end, see Removals.

Still attached: a warning, not a refusal

These five do not stop a removal. Where a confirm shows them, it lists what is still attached. The records listed are not removed with it: remove or disconnect them yourself, or keep them.

Code	What you see
REFERENCED_BY	Something else in this workspace still points at it. Remove what is listed first, or remove them together.
SURFACE_NOT_EMPTY	A surface cannot be removed while it still holds things. Remove what is listed first, or remove it together with the surface.
DATA_STORE_HAS_DATABASES	A data store cannot be removed while databases still live in it. Remove those databases first, or remove them together.
DATABASE_HAS_TABLES	A database cannot be removed while it still holds containers. Remove those containers first, or remove them together.
DATABASE_STILL_READ	A database cannot be removed while a warm query or a surface still reads it. Disconnect them first, or remove them together.

This kind cannot be removed

Code	What you see	What to do
KIND_NOT_DELETABLE	Records of this kind are never removed from a workspace. (A kind with its own reason says that instead; the landing zone's is below.)	Nothing
REMOVER_NOT_ALLOWED	This kind cannot be removed from here. The removal guidance names the doors that can remove it; some kinds are a person's to remove.	Remove it in one of the ways named
KIND_TEARDOWN_UNSUPPORTED	Removing this kind is not built yet: nothing would take down what it runs, so it is refused rather than left running and billing behind a record that is gone.	Leave it in place
DELETE_TYPE_UNSUPPORTED	Nothing takes down what this type runs, so removing it would leave it running with no record pointing at it. Only the types with a teardown can be removed today.	Leave it in place
ACTUATOR_NOT_REGISTERED	Nothing is registered to take this kind down in Azure, so the removal stops here rather than clearing the record while what it runs keeps running.	Leave it in place
FROM_SURFACE_NOT_SUPPORTED	This kind is removed as a whole record, not from one surface.	Remove the whole record, or leave it

Today KIND_TEARDOWN_UNSUPPORTED is the answer for data stores, IoT, communications and Provenance.

Your landing zone is refused with its own sentence:

Your landing zone holds the data archives of everything removed from this workspace, so it outlives every other removal.

Provisioned databases and containers

A database or container that exists in its Cosmos account needs a copy of its data taken before it is removed, and that copy is not switched on yet. A provisioned one is kept, and so is its data.

Code	What you see
PROVISIONED_DATABASE	This database exists in its Cosmos account, and the copy of its records that must be taken before it is removed is not switched on yet. Until it is, the record is kept rather than removed from the workspace while the data stays.
TABLE_PROVISIONED	This container exists in its Cosmos account, and the copy of its documents that must be taken before it is removed is not switched on yet. Until it is, the record is kept rather than removed while the documents stay.
DATABASE_UNRESOLVABLE	This database cannot be traced to a data store account, so whether anything exists in Azure behind it is unknown. Repair the link first.
TABLE_UNRESOLVABLE	This container cannot be traced to a data store account, so whether anything exists in Azure behind it is unknown. Repair the link first.
TABLE_STILL_REFERENCED	The message names the warm queries and surfaces that still read the container. Disconnect them, then remove it.
HANDLING_UNSUPPORTED	The handling asked for is not one this kind of record accepts. Asking for a full copy does not by itself let a provisioned database or container be removed.

Access

Code	What you see	What to do
ACCESS_CONFIGURATION_ASSIGNED	People still hold an access card issued from this configuration. Removing it would take away what they have; withdraw the cards first. (The message adds how many.)	Withdraw the cards, then remove the configuration
NOT_A_MEMBER	You are not a member of this workspace.	Ask the owner to add you
ACCESS_MANAGE_REQUIRED	Only the workspace owner or someone with the 'Workspace.Access.Manage' right can change a user's access.	Ask a member who holds that right
ACCESS_RIGHT_REQUIRED	You do not hold the access right Licenses.Manage in this workspace, which is needed to change this workspace's licences, plans, prices, coupons or Stripe keys.	Ask a member who can grant it
DEPLOY_NOT_ALLOWED	You do not have permission to deploy this workspace. (The button reads Activate to Deploy.)	Ask a member with Workspace.Deploy

Any workspace member can accept a proposal; some changes (access, licences, connected-app requests) need a management right. See Team & Access Rights.

The record has moved on

Code	What you see	What to do
TARGET_NOT_FOUND	There is no saved record by that name to remove. (On an accept: the record is no longer in this workspace.)	Reload; someone else may have removed it
ALREADY_STAGED	This record is already waiting to be removed on the next Deploy.	Nothing; it is already waiting
RECORD_STAGED_FOR_DELETE	This record is waiting to be removed on the next Deploy, so it cannot be changed. Take it off the pending removals first.	Restore it, then make your change
TEARDOWN_STARTED	This removal has already started, so it can no longer be taken off the list. Wait for the deploy to finish.	Wait
STAGE_ON_ACTUATED_SAVE	A removal cannot be added while this save is deploying. Save the removal on its own, then deploy.	Save the removal by itself first
TARGET_IS_PROPOSAL_ONLY	Only a pending proposal describes this record; it was never saved. Reject that proposal instead of removing a record that does not exist.	Reject the proposal
STAGE_DELETES_SHAPE	Removals are asked for one at a time, each naming what it removes. (Or: Removal '...' does not say what it removes.)	Ask for each removal on its own

Proposed removals

Code	What you see	What to do
DELETE_CONFIRM_REQUIRED	This bundle removes records, so it can only be accepted with an explicit confirmation.	Accept it yourself, through the confirm
DELETE_WITH_PROPOSED_FIELDS	A removal carries only its delete settings (Metadata.Removal). Ask for the removal on its own, and propose any edit separately.	Propose the removal and the edit apart
REMOVAL_SETTING_REQUIRED	A delete setting this kind requires has no answer, so the removal cannot deploy or be accepted yet.	Answer the setting on the waiting node

Deploy and archive

Code	What you see	What to do
DEPLOY_PLAN_CHANGED	One removal is waiting for this deploy. Confirm the list below, then deploy again. (With more, it names how many; records moving to your private cloud are counted too.)	Read the fresh list, then Deploy again
DEPLOY_IN_PROGRESS	A deploy is already running for workspace '...'. ... Wait for it to finish, then try again. (While a setup window is deploying: The ... setup window is deploying for workspace '...'.)	Wait for it to finish
MOVE_HELD	One record would move to your private cloud, and its kind cannot move yet. Nothing was deployed.	Leave that record where it is for now
ARCHIVE_PLAN_CHANGED	What archiving this workspace will do has changed since it was shown. Read the new plan, then confirm again.	Read the new plan, then confirm again
DATA_ARCHIVE_GATED	Removing these records requires a copy to be taken first, and that copy is not switched on yet, so nothing was torn down.	Restore the removal, or leave it waiting
WORKSPACE_ARCHIVE_BLOCKED	1 removal still waiting for the next deploy. Deploy or restore them, then archive the workspace.	Deploy or restore what is waiting
PROVENANCE_WORM_ACTIVE	'...' is locked: ... A container under a locked immutability policy can never be deleted, so this workspace cannot be archived.	Nothing; the lock decides how long the records stay

The checks could not run

On Save it reads: "The workspace capability checks could not be loaded, so nothing was committed. Try again shortly."

If a refusal shows a code that is not on this page, its sentence reads "This removal was refused, and its reason has no sentence yet. The refusal code names what stopped it."