Error when selecting a semantic model to build from

[DamoUK]

Our setup:
Fabric Capacity (F64). Developers (around 40) assigned Power BI Pro licences. All other business users (around 1,000) assigned Fabric Free licenses. I am the Fabric and Power BI tenant/capacity admin. Personal Workspaces are NOT configured to be on the Fabric capacity and checking some of the Free license users (some who have and some who haven't developed reports), it looks like the Personal Workspaces all reside on "Pro" - the shared workspace according to the Microsoft documentation.

However, one Free user, who's been developing their own reports through the Power BI Service for years, by connecting to sematic models with build permissions, can no longer develop. They are being prompted to upgrade their license. They originally had a Free license then we allowed them to have a Power BI Premium Per User trial, and until I started trying to fix the issue today, their workspace was under "Trial" and the Capacity was "Trial-[long string of alphanumerics]".

I've tried reverting their workspace back to "Pro" and also tried moving it to the Fabric capacity, but they still keep getting the same error about needing to upgrade the licence (this appears after they've chosen the semantic model to build from). I've checked their license through the Microsoft Admin Center and they definitley have a Fabric free license and it no longer shows the trial license - and they definitely have build permissions to the models.

Help!

[v-pnaroju-msft]

Hi DamoUK,

We wanted to see if the information we gave helped fix your problem. If you need more help, please feel free to contact the Microsoft Fabric community.

Thank you.

[v-pnaroju-msft · Accepted solution]

Hi DamoUK,

Thank you for the update.

Based on my understanding, since other free users can access the same semantic model without any issues, and the affected user is able to work with existing reports but cannot create new ones from the same model, this appears to be an issue specific to the user’s cached session or legacy licensing token.

Kindly follow the steps mentioned below with the affected user to resolve the issue:

1. Instruct the user to sign out completely from Power BI service and Microsoft 365 across all browsers.
2. Clear the browser cache, cookies, and site data.
3. Reopen Power BI in a new browser or incognito window.
4. Ensure that the user starts a new report from within the correct Fabric-backed workspace, and then connects to the semantic model.

This process helps to reset cached license artifacts, which may be lingering from the expired PPU trial.

We hope the information provided will help resolve the issue. Should you have any further queries, please feel free to contact the Microsoft Fabric community.

Thank you.

[v-pnaroju-msft]

Hi DamoUK,

We are following up to see if what we shared solved your issue. If you need more support, please reach out to the Microsoft Fabric community.

Thank you.

[DamoUK]

Hi @v-pnaroju-msft following your exact instructions has not made any difference. The error connecting to the semantic model remains, when selecting it. Other employees have no issue connecting. Also, this same employee can continue to work from another report they've previously created, linked to datasets, but trying to connect to them with a new connection fails. Again, remember this is in the service, as a Fabric (Free) user.

[v-pnaroju-msft]

Hi DamoUK,

Thank you for your update.

Please note that even with Build permission and App access, Power BI still requires the user to have Viewer or higher workspace role to enable semantic model discovery when initiating a new report. App access does not replace the need for workspace level permissions when building reports.

Kindly follow the approach outlined below to resolve the issue:

1. Assign the user temporary Viewer or Contributor access to the workspace that hosts the model.
2. Once the report is saved, remove the assigned role. The user will continue to have access via the App.

This method allows you to maintain your App based permission strategy effectively.

We hope this information will assist in resolving the issue. Should you have any further queries, please feel free to contact the Microsoft Fabric community.

Thank you.

[v-pnaroju-msft]

Hi DamoUK,

We would like to follow up and see whether the details we shared have resolved your problem.
If you need any more assistance, please feel free to connect with the Microsoft Fabric community.

Thank you.

[v-pnaroju-msft]

Hi DamoUK,

Thank you for the update.

Based on my understanding, the license prompt shows up right after selecting the semantic model, even before saving the report. This means Power BI checks the license at the time of connection, not only when you save or publish the report.

Please follow these steps to help fix the issue:

1. Make sure the user creates the report directly inside a shared Fabric backed workspace, not in a personal workspace or on the browser landing page.
2. The user should click the New report button inside the correct workspace and then select the semantic model. This ensures the right context and capacity.
3. Confirm that the semantic model is hosted in a Fabric backed workspace.
4. Ensure the user has Build permission on the semantic model and Viewer or higher role on the workspace where the semantic model is hosted. Both are required for Free users to discover and use the model in report building.

This approach is very important because trying to connect from outside the capacity context, like from Personal or My Workspace, will cause the license check to appear.

We hope this information helps you solve the problem. If you have any more questions, please feel free to contact the Microsoft Fabric community.

Thank you.

[DamoUK]

@v-pnaroju-msft  we use Apps for permissions to reports to simplify management of audiences. Because they're permissioned to the report through the App, I've only added build permissions to the model. Could you confirm this negates the need for viewer permission to the workspace please? I would prefer not to have to start messing with permissions at the workspace level as well as App!

[v-pnaroju-msft]

Thankyou @BhavinVyas3003, for your response.

Hi DamoUK,

We appreciate your inquiry through the Microsoft Fabric Community Forum.

We would like to inquire whether have you got the chance to check the solution provided by @BhavinVyas3003  to resolve the issue. We hope the information provided helps to clear the query.
Should you have any further queries, kindly feel free to contact the Microsoft Fabric community.

Thank you.

[BhavinVyas3003]

The issue occurs because Free users can’t build reports from semantic models unless both the model and the report workspace are backed by a Fabric capacity. Previously, the user was on a PPU trial, which allowed it. Now that the trial is gone and their workspace isn’t on Fabric capacity, they’re being asked to upgrade. To fix this, move their reports to a shared workspace assigned to the Fabric F64 capacity and ensure they have Build permission on the model. Personal workspaces can’t be assigned to capacity, so they must work in shared Fabric-backed workspaces.

[DamoUK]

@BhavinVyas3003 I don't think this is exactly the case, although useful to know. This is occuring when the free user is trying to build a new report from scratch. As soon as they try to connect to the semantic model, they're getting the license notice. They've not even had a chance to save the report or work from the model.

My talk about the users presonal workspace could just be a red herring as it was my assumption it was caused by this still being trial-[whatever alphanumerics].

Any other ideas? I'd prefer not to have to raise a ticket as I'm leaving the business very soon and won't be able to see it through.