topic Re: Subject: Can’t Assign Workspace to Power BI Embedded Capacity (excstds2) in Developer

Subject: Can’t Assign Workspace to Power BI Embedded Capacity (excstds2)

charleshale — Sat, 31 May 2025 03:44:44 GMT

Hi,
I’ve set up a Power BI Embedded capacity (excstds2, SKU A1) and a workspace (Charlie), and I need to assign that workspace to the Embedded capacity for app-owns-data embedding.

I am the capacity admin and workspace admin, but the Power BI portal shows no option to assign the workspace to the capacity — not in the workspace settings, nor in the admin portal.

Azure support routes me to Fabric, which asks for a Premier contract I don’t have.

Can Microsoft please:

Confirm if this workspace is assignable to capacity
Or move it to excstds2 on my behalf?

Subscription ID:

1519c243-1194-43f3-9353-65ab89763c20
Workspace ID: Charlie
Capacity Name: excstds2

Thank you — this is for a live Power BI embed scenario using app-owns-data.

Re: Subject: Can’t Assign Workspace to Power BI Embedded Capacity (excstds2)

v-agajavelly — Mon, 02 Jun 2025 09:45:35 GMT

Hi @charleshale
Thanks for posting your query in microsoft fabric comunity forum.

Based on what you’ve shared, it sounds like your workspace “Charlie” was created as a Fabric-enabled workspace. Currently, Power BI Embedded capacities (like your A1 capacity “excstds2”) are not compatible with Fabric workspaces, which is why you're not seeing the option to assign the workspace to your capacity.

Create a new workspace in Power BI - go to Power BI Service and Click on Workspaces > Create a workspace. Do not enable Fabric features (no checkboxes like OneLake or other Fabric options), once it’s created you can open the workspace and go to Settings > Premium. When you open it you’ll now see the option to assign the workspace to your excstds2 (A1) Embedded capacity.

Re-publish your reports and datasets from the “Charlie” workspace into this new workspace.

Sometime its happen because fabric workspaces are designed for broader Microsoft Fabric capabilities and require a P SKU (Premium per capacity), not an A SKU (Embedded). That’s why assigning an A1 capacity doesn’t show up as an option.

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.

Re: Subject: Can’t Assign Workspace to Power BI Embedded Capacity (excstds2)

v-agajavelly — Fri, 06 Jun 2025 11:50:22 GMT

Hi @charleshale

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.

Re: Subject: Can’t Assign Workspace to Power BI Embedded Capacity (excstds2)

Poojara_D12 — Mon, 09 Jun 2025 06:15:37 GMT

Hi @charleshale

You're trying to assign a Power BI workspace ("Charlie") to an A1 SKU Power BI Embedded capacity (excstds2) for an app-owns-data embedding scenario, but you’re not seeing the expected option to move the workspace under that capacity—even though you're both the capacity admin and the workspace admin. This issue typically occurs when the workspace is a "Fabric" workspace (i.e., created after Fabric was enabled by default), which may not be compatible with Power BI Embedded (A SKUs) unless Fabric is explicitly disabled for that workspace or tenant. Since Fabric and Power BI Embedded capacities (A SKUs) are managed differently, Microsoft limits certain controls unless you're on a Premier or Fabric-supported plan, hence Azure support routing you to Fabric—which unfortunately requires an enterprise-level agreement.

Microsoft will not manually move your workspace for you based on a support request unless you have a Premier support contract, as these operations require validation and administrative privileges not handled over general support. Instead, the recommended approach is to either create a new classic Power BI workspace (not Fabric-enabled) and move your reports and datasets there, or disable Fabric capabilities for that workspace via PowerShell or tenant settings—if that’s permitted in your environment. Once the workspace is compatible, you’ll see the “Assign to capacity” option under the Workspace settings > Premium > Dedicated capacity section.

If you’re unsure whether the workspace is Fabric-enabled or not, you can check this via the Power BI Admin Portal under “Workspaces” or by using Power BI REST APIs to query the workspace metadata. To move forward without a Premier contract, your best option is to manually re-create the workspace under a capacity-compatible environment and publish your reports there for embedding.

Re: Subject: Can’t Assign Workspace to Power BI Embedded Capacity (excstds2)

v-agajavelly — Wed, 18 Jun 2025 04:51:32 GMT

Hi @charleshale

Just checking in were you able to try out the steps we discussed earlier? If it worked, that’s great to hear! Feel free to mark the solution that helped. If you're still running into issues, let us know what you’re seeing even small details can help us troubleshoot more effectively.

Thanks,
Akhil.

Re: Subject: Can’t Assign Workspace to Power BI Embedded Capacity (excstds2)

v-agajavelly — Fri, 20 Jun 2025 07:26:44 GMT

Hi @charleshale

Just checking in to see if the approach shared about Assign Workspace to Power BI Embedded Capacity?

If you found this solution helpful, please consider accepting it and giving it a kudos (Like) it’s greatly appreciated and helps others find the solution more easily. Looking forward to your update.

Best regards,
Akhil