Duplicate Workspace error message (but this workspace DOES NOT exist within the capacity)

[duncfair]

Got this error adding a Workspace to Premium Capacity but searching the capacity reveals that the workspace DOES NOT exist there. Does this indicate the workspace exists within another of our firm's premium capacities? What is up?

[v-kpoloju-msft · Accepted solution]

Hi @duncfair,

Thank you for reaching out to the Microsoft fabric community forum. Thank you @lbendlin, for your inputs on this thread.

After reviewing the details you provided, I have identified few workarounds that may help resolve the issue. Please follow these steps:

The error occurs because the workspace SDG_MBD_EastGrinstead already exists elsewhere, though it may not be within the capacity you are managing.

In Power BI, when assigning a workspace to a Premium capacity:

• The system checks across all capacities, including default capacities (Pro or non-Premium).
• If the workspace exists in another Premium capacity or the shared default capacity, it is flagged as a duplicate, even if it is not directly visible under your current capacity.
• Occasionally, this can also happen if the workspace is soft deleted (pending backend cleanup) but still registered internally.

Therefore, the error you are encountering is due to the workspace already existing elsewhere in your organization's Power BI environment.

Search the Workspace Globally: Go to the Power BI Admin Portal > workspaces. Use the search bar to locate SDG_MBD_EastGrinstead. Ensure you filter by All workspaces, including Deleted workspaces. Confirm whether it exists and check the capacity assignment.

If the workspace is found, verify its capacity assignment. You may need to move it to the intended Premium capacity or unassign it first.
What is Power BI Premium? - Power BI | Microsoft Learn
Solved solution related to the thread: Solved: Re: Error assigning premium capacity to workspace ... - Microsoft Fabric Community

Sometimes the workspace might be soft deleted but not fully removed yet. Use Power BI PowerShell commands to check hidden or soft-deleted workspaces. In the rare event that the workspace cannot be recovered, please consider creating a new workspace with a slightly different name (e.g., SDG_MBD_EastGrinstead2) to avoid any duplicate name conflicts.

If this post helps, then please give us ‘Kudos’ and consider Accept it as a solution to help the other members find it more quickly.

Thank you for using Microsoft Community Forum.

[v-kpoloju-msft]

Hi @duncfair,

May I ask if you have resolved this issue? If so, please mark the helpful reply and accept it as the solution. This will be helpful for other community members who have similar problems to solve it faster.

Thank you.

[v-kpoloju-msft]

Hi @duncfair,

I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions. If my response has addressed your query, please accept it as a solution and give a 'Kudos' so other members can easily find it.
Thank you.

[v-kpoloju-msft]

Hi @duncfair,

I hope this information is helpful. Please let me know if you have any further questions or if you'd like to discuss this further. If this answers your question, please Accept it as a solution and give it a 'Kudos' so others can find it easily.
Thank you.

[lbendlin]

yes, workspace names need to be unique across all capacities in a tenant.