Azure Databricks Workspace stuck in "Accepted" provisioning state and cannot be deleted (ApplianceBeingCreated)

Hello @Denys Aleksieiev

Thanks for providing the deployment details and correlation ID.

Based on the symptoms, this appears to be a backend provisioning issue rather than a subscription or quota problem. The key indicators are:

• The workspace remains in provisioningState = Accepted for an extended period.
• The ARM deployment has already been canceled.
• The managed resource group was created successfully.
• Deletion fails with ApplianceBeingCreated, indicating Azure still considers the managed application to be in an active creation state.

Before Microsoft investigates, it may be worth checking a few additional items:

• Review the Activity Log for the Databricks workspace and managed resource group to identify the last successful or failed resource provider operation.
• Verify whether the Microsoft.Databricks resource provider is registered and healthy for the subscription.
• Check Azure Service Health for any ongoing incidents affecting Germany West Central or Azure Databricks provisioning.

If these checks don't reveal anything, the workspace is likely stuck in an inconsistent backend state that cannot be resolved through the Azure Portal or Azure CLI. In that case, a Microsoft engineer will typically need to clear or reset the managed application state before the resource can either complete provisioning or be deleted.

Since you've already included the correlation ID and confirmed that quota is not the issue, it would be helpful if a Microsoft moderator could escalate this to the Azure Databricks provisioning team to review the backend deployment state and manually release the ApplianceBeingCreated lock if necessary.

Please "Accept the Answer" if this information helped you. This will help us and others in the community as well.