Power BI - Requirements to Use Analyze in Excel

I think I now got this question 4 times in the last months, so I thought I'd write it down so I can reference it later, and point people to it 😄

What are the requirements so (a group of) colleagues can start using Analyze in Excel?

Good question, let me break it down. 
In general, I think it's also better to use Analyze in Excel than Export to Excel!
Reza Rad also wrote about why that's important earlier.

Prerequisites to use Analyze in Excel

• Power BI license
  You either need a Power BI Pro or PPU license, or the semantic model you connect to must be in a workspace backed by a Power BI Premium / Fabric F-capacity, this needs to be an F64 or higher SKU. Although I have seen some instances where it might have (temporarily) worked with a lower F-SKU, this is not supported/allowed (see Power BI licensing).
• Tenant Setting
  Your Power BI / Fabric Administrator needs to enable the Tenant setting in the Admin Portal: "Users can work with Power BI semantic models in Excel using a live connection". You can learn more about that setting on the admin portal documentation.
  
• Semantic Model permissions
  The user needs at least build permissions on the semantic model, or at least the Contributor role in the workspace. Ideally you put people in an Entra ID group and give that the appropriate permissions.
• Excel
  You obviously need Excel Desktop or Excel for the web installed for it to work. You might have to install some updates for it to work.

A few things to be aware of:

• Analyze in Excel creates a dynamic, live connection to the Power BI dataset, so any changes to the dataset will be reflected when the Excel report is refreshed

• Free users can analyze data from Premium workspaces without needing a Pro license, provided they have the appropriate role (at least build permissions or Contributor role) assigned in that Premium workspace

• You'll need to use measures in the PivotTable's values area, as you can't directly drag numeric columns like 'cost' into that area. It's anyway better to create explicit instead of implicit measures

Fabric Quality of Life Update: No More Default Semantic Models!

Another quick post, because today is an important day for everyone working with Fabric and Power BI!

Last month, Microsoft announced they are Sunsetting Default Semantic Models: Yaay! 😀
Today marks that day: No more automatic child semantic models!

The info message also states only a SQL endpoint is created

So now whenever you create a warehouse, lakehouse, SQL database, or mirrored database, you only will get that item, and the SQL analytics endpoint connected to it.

No more default semantic models!

This means from now on you always have to manage the semantic model yourself, whenever you create one of the above items.

What about my existing default semantic models?

To be clear: existing (default) semantic models are not affected (yet!). But by the end of December (2025) they will be decoupled from their connected item, and you will have to manage that model manually.

Conclusion

Now that Fabric is getting more widely used, the demand for stronger governance and greater control over semantic models was growing. This change takes away the auto/generated models and gives you more control in the creation of your semantic models.

To read more about this:

• Take a look at the documentation of semantic models
• Or at the blog post announcing the deprecation

There's more information in those links about the exact changes and menu-items going away, the timeline and future updates/blog posts.