Hi Rob Sewell,
Check from the Power BI Admin side (even if the workspace looks empty) Some associations (capacity, pipelines, hidden bindings) live in admin views and can block deletion.
- Admin Portal → Workspaces: open the specific workspace and review: Capacity assignment (reassign if needed). Deployment pipelines: if the workspace is connected to a pipeline, remove that link first.
- If nothing shows in the UI Use Power BI Admin APIs to list and clear hidden bindings. https://learn.microsoft.com/rest/api/power-bi/
- Delete the workspace programmatically Power BI doesn’t have a direct
Remove-PowerBIWorkspacecmdlet, so use REST
https://stackoverflow.com/questions/76090783/how-to-remove-a-workspace-in-powershell - Delete the AAS server After the workspace is gone, delete the AAS server in Azure Portal.
The migration linkage often surfaces as a state that blocks delete (the AASMigration_ActiveMigrationExists flag) rather than a prominent workspace toggle. In practice, clearing pipelines/capacity/dataset bindings is what resolves it; once cleared, the workspace and then the AAS server can be deleted.
I hope this information is helpful! If you still have questions or you come across issues, please let us know what is needed in the comments so this question can be answered.