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

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.

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.