Publish Report via API with Registered Resources

Hi Anonymous,

Thanks for reaching out to the Microsoft fabric community forum.

Yes, this is a known limitation when working with .pbip files that include registered resources like images. When publishing via the Fabric REST API, the API currently doesn't handle those registered resources properly evem though they’re included in the .pbip structure, the API doesn't resolve them during deployment. That’s why you're seeing the “resource cannot be located” error.

At the moment, there’s no official support or workaround through the API for this. The safest options for now are eitheravoid using registered resources in .pbip files you plan to deploy via API, or publish the report directly from Power BI Desktop, which handles the resource references correctly.

Hopefully this is something that gets addressed in a future update, but as of now, this behavior is expected.

If I misunderstand your needs or you still have problems on it, please feel free to let us know.  

Best Regards,
Hammad.
Community Support Team

If this post helps then please mark it as a solution, so that other members find it more quickly.

Thank you.

Hi Anonymous 

What you’re encountering when publishing reports that include Registered Resources—such as images—via the Microsoft Fabric API is a known limitation or current gap in support. Although the Fabric API allows publishing of reports and datasets programmatically, Registered Resources like images or other embedded assets often require additional handling because the API does not automatically upload or reference these resources alongside the report content. As a result, when the report tries to load these Registered Resources, it cannot locate them, causing the error you described. This is a fairly common issue, especially in newer or evolving APIs where resource management is still being improved. Currently, there isn’t a fully streamlined way to package and publish Registered Resources together with the report via the API in one step. Workarounds typically involve manually uploading these resources separately to the appropriate location (e.g., a content library or resource storage in the Power BI or Fabric service) before publishing the report, or embedding images directly within the report if possible. Until Microsoft enhances the API to support Registered Resources natively during publishing, you may need to continue using such manual steps or alternative workflows to avoid this error.