Fabric Capacity and Embed for Customer - still not possible?

[LasseMr]

Dear community,

According this article Fabric should be fully capable of doing Embedded on same terms as A and P SKUs: https://powerbi.microsoft.com/en-us/blog/power-bi-embedded-with-microsoft-fabric/?

However, after GA a few days ago, I wanted to test if that is really the case.

I have a .NET webapp application running Embedded for Customer (app-owns-data) using A SKUs. All works fine.

Test;

1. Created a Fabric F16 capacity
2. Created a Power BI Workspace and allocated it to the F16 capacity
3. Created 2 simple reports, one powered by a Fabric lakehouse semantic model and another with a simple dataset without a "F"-features model
4. Added the security group having the apps service principal users with Admin rights to the workspace (same security group as used for the A SKU approach)
5. In the webapp I can authenticate and get list of reports in the F16 Workspace.
6. In the webapp embedding an actual report from F16 Workspace (using exactly the same API methods as for A SKU) I a blocked by CORS policy error, causing a series of subsequent app errors as the fetching is blocked.

Access to fetch at 'https://xxx.azurewebsites.net/api/Embed/' from origin 'https://app.xxx.xxx' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.

I do not get this error using A SKU workspaces.

Any ideas?

I would really love to move into Fabric for embedded solutions, and it strikes me strange that the API allows listing reports successfully but not report embedding.

[lbendlin]

If you have a Pro license you can open a Pro ticket at https://admin.powerplatform.microsoft.com/newsupportticket/powerbi - otherwise you can raise an issue at https://community.fabric.microsoft.com/t5/Issues/idb-p/Issues .