Forum Discussion
Guest External User Edit button greyed out
- 11 months ago
Hi MichaelBristol,
This changed recently with the move to Fabric-wide B2B controls. The legacy Power BI tenant toggle named "Allow external guest users to edit and manage content" has effectively been replaced by a set of Fabric admin settings under Tenant settings. Here is a quick checklist to get your guest Contributor the Edit button back:
- Confirm the Fabric B2B tenant settings (Power BI Admin portal - Tenant settings - Export and sharing settings). Make sure these are enabled for the right security group(s):
- "Guest users can access Microsoft Fabric" – controls whether B2B guests can access Fabric at all. Docs: Export and sharing tenant settings
- "Users can invite guest users to collaborate through item sharing and permissions" – replaces the older "Share content with external users" wording and governs inviting new guests through Fabric UIs.
- "Guest users can browse and access Fabric content" – lets guests use left nav and browse. Even if this is off, guests with explicit workspace roles still retain those permissions, but browsing is limited.
For high-level B2B guidance and limitations, see Distribute Power BI content to external guest users with Microsoft Entra B2B (includes the new tenant switcher and guest limitations). - Have the guest switch into your tenant when working. Guests often land in their home tenant where Edit will be missing. Ask them to use the account manager "Switch" option to your tenant, then open the item from your workspace. Steps are documented under "Tenant switcher" in the B2B page linked above.
- Verify workspace role and dataset permissions:
- Contributor or Member in the workspace that hosts the report is required to edit the report. Role capabilities are listed here: Roles in workspaces.
- If the report uses a semantic model in a different workspace, the guest also needs Build permission on that semantic model or Contributor in the model’s workspace. Without Build, the Edit button can be disabled even if they are a Contributor where the report lives. See Build permission for shared semantic models and the note about Build being included via workspace roles in Roles in workspaces.
- Open from the workspace, not an app. Apps are read-only distribution experiences. To edit, the guest should navigate to the workspace item itself. See the distinction in Collaborate and share in the Power BI service.
- Check licenses:
- Editing content requires a paid Power BI license (Pro or PPU). Types of licenses for Power BI business users
- Guests can bring their own Pro license (BYOL) or you can assign one in your tenant; PPU workspaces require PPU for everyone who edits. See Azure AD B2B guest users can now edit and manage content in Power BI and the license matrix in service features by license type.
Why you no longer see the old toggle: Microsoft consolidated and renamed B2B controls under Fabric. The capabilities previously governed by "Allow external guest users to edit and manage content" now map to the Fabric B2B switches above (for example "Guest users can access Microsoft Fabric" and "Users can invite guest users..."). See the renamed and new settings in Export and sharing tenant settings and the current B2B overview in Distribute Power BI content to external guest users with Microsoft Entra B2B.
If you walk through those 5 checks, the Edit button for your external Contributor should appear when they open the report from your workspace in your tenant.
If this helped, some kudos are appreciated. If it solved it, please mark as solution.
- Confirm the Fabric B2B tenant settings (Power BI Admin portal - Tenant settings - Export and sharing settings). Make sure these are enabled for the right security group(s):
While this is not directly related to your issue, I have worked with a lot of customers where trying to do things via a guest account becomes very hard to do due to restrictions and guest accounts not being able to do everything a normal account can do. If this is a significant piece of work, I would highly recommend creating a user account in your domain which will alleviate a lot of the issues you are facing. And potential issues you could face further down the line?