Forum Discussion
Helper VCannot publish to the workspace
Dears,
I have a problem i cannot publish to the workspace ( prem Capacity )
I have Pro account plus iam an admin in the workspace , and i receive this error
Thank you
i think we can close the topic , the user is checking with the Admin of the capacity
i think the admin give me the access to publish onlythank you again
10 Replies
- Shahid12523
Community Champion
You only see My Workspace because of one of these:
Workspace is PPU → need PPU license (not just Pro).
Tenant settings block publishing.
Access not synced (recheck Member/Admin role).
Try sign out/in of Power BI Desktop or publish via Service.
v-kpoloju-msftCommunity Support
Hi ahmedshalabyy12,
Thank you for reaching out to the Microsoft fabric community forum. Also, thanks to Shahid12523, for his inputs on this thread. Here are some troubleshoot steps those might help:
Workspace type (Premium per user vs Premium capacity): If the workspace is on Premium per user (PPU), you will also need a PPU license to publish there. A Pro license alone won’t be enough. You can confirm this in the workspace settings under Premium.
https://learn.microsoft.com/en-in/fabric/enterprise/powerbi/service-premium-what-isIf you are accessing the workspace as a guest user in another tenant, Desktop will not let you publish directly. In that case, you will need to either:
- Upload the PBIX directly in the Service (Workspace → New → Upload a file), or
- Use an account that belongs to the same tenant as the workspace.
Signed into a different tenant in Desktop: Sometimes Desktop is signed in to another org/tenant. Try signing out in Desktop and signing back in with the same account you use in the Service where the workspace lives.
https://learn.microsoft.com/en-in/power-bi/create-reports/desktop-upload-desktop-filesMake sure you are using the latest version of Desktop. If your PBIX is very large, the capacity might block it due to Max Offline semantic model size. Next steps I’d suggest: First, check the workspace settings in the Service to see if it’s PPU or Premium capacity. Then, confirm you are signed in to Desktop with the correct account/tenant. If you are a guest user, try uploading from the Service instead of Desktop.
Hope this helps. If you have any doubts regarding this, please feel free to ask here. We will be happy to help.
Thank you for using the Microsoft Community Forum.- v-kpoloju-msft
Hi ahmedshalabyy12,
Just checking in to see if the issue has been resolved on your end. If the earlier suggestions helped, that’s great to hear! And if you’re still facing challenges, feel free to share more details happy to assist further.Thank you.
ahmedshalabyy12not solved yet
- ahmedshalabyy12
Workspace it's prem capacity
user is pro license and i assigned him as an adminthis user is belong to another tenant
----
I am an admin in this workspace despite i belong to another tenant but i can publish freely- v-kpoloju-msft
Hi ahmedshalabyy12
Thanks for sharing the additional details, this really helps us narrow it down.From what you described, the key point is that the affected user belongs to another tenant. Even though you have assigned them as an admin in the workspace (which is on Premium capacity), cross-tenant (guest) accounts have a limitation: Power BI Desktop does not allow direct publishing to a workspace when signed in as a guest user.
https://community.fabric.microsoft.com/t5/Desktop/Publishing-from-PBI-Desktop-as-Guest/td-p/4052590That is why you are able to publish (since you are in the home tenant), but the guest user cannot. To work around this, they can either:
• Upload the PBIX file directly in the Power BI Service (Workspace → New → Upload a file).
• Or, if possible, use a native account from the same tenant as the workspace when publishing from Desktop.
This is expected behaviour for guest users in another tenant. The workaround would be uploading via Service or using a tenant-native account for Desktop publishing.
Hope this clears things up. If you have any doubts regarding this, please feel free to ask here. We will be happy to help.Thank you for using the Microsoft Community Forum.
