With the move to the new Fabric capacities, if you want to share reports and apps with clients or other non-licensed users, you need at least an F64 capacity. That is a very steep increase from the current situation where you can use an A1 capacity to achieve the same. While I understand that A capacities have been designed for embedding reports, currently you are able to share reports and apps with unlicensed users using A.That is an increase from USD $735 to USD $9811 (AUE in this example) a month. This is especially annoying if you are working in a global environment where you multiple regions with the requirement to keep data on-shore. That means, we would have to deploy an F64 capacity in each region, just to be able to share reports with our clients. That does not make any sense to me. I am happy to pay for as much Fabric computing power as I require, but I dont want to spend 10x more just to be able to share reports with clients. There are a few alternatives to avoid this issue, but I think they are all flawed: Continue using A capacities: You could continue using the A capacities for semantic models and reports and be able to share that with clients. And then an additional low F capacity (< F64). Since one workspace can only be associated with one capacity, it would require us to have 2 workspaces for each project, one connected to the Fabric capacity with all Fabric items, and one connected to the A1 capacity, containing all PBI items. That is a duplication of effort and not really practical Assigning clients and non-licenses users with PBI Pro: While PBI Pro is a bit overkill just to view reports, it seems acceptable for internal stakeholders. However, for clients that are just consuming reports for a short amount of time, it does really not make sense and introduces additional overheads. Please consider making sharing reports and apps available also in lower tier F capacities. ... View more