Power BI report authors can store images in a Microsoft Fabric Lakehouse and use OneLake URLs to display them in reports, rather than relying on SharePoint or anonymous blob storage. This approach is relevant to makers and report developers who need images in Power BI visuals and want to control access to the underlying files. Guy in a Cube demonstrates the OneLake workflow, including dynamic image URLs and folder-level access.
The approach puts image files in OneLake, Fabric’s storage layer, and references those files from Power BI. The video description presents it as an alternative to SharePoint links and anonymous blob storage for report images. Its key mechanics are a OneLake HTTPS URL, a Power BI image measure when the image needs to respond to a slicer, and access granted through OneLake security roles.
A dynamic image measure lets a report select an image based on a user’s filter or slicer choice. Rather than relying on one fixed image address for every report state, the measure can return a different image URL as the selection changes. The description also recommends using workspace and item GUIDs in URLs to make them more resilient than URLs that depend on names.
This is a storage and image-addressing pattern, not a change to the image itself. The source material does not provide a precise URL template, a DAX formula, or a full walkthrough of the Power BI model, so those implementation details should be checked in the Fabric and Power BI experiences used by your organization.
The workflow is aimed at Power BI report authors who need to show images and have access to a Microsoft Fabric Lakehouse in OneLake. You will also need a way to add the OneLake image URL to the report and, if images should change with a selection, a dynamic measure that returns the appropriate URL.
Access matters: the publisher’s description specifically calls out OneLake security roles and read access to image folders. That means the report’s intended viewers need the relevant access to the files; moving images to OneLake does not mean they are automatically available to everyone who can open a report. The source material does not state which licenses, Fabric capacity, tenant settings, or regional availability are required.
No rollout stage or preview status is given in the material available for this article. It also does not specify a minimum Power BI Desktop version or identify which Power BI visuals support these URLs, so verify the behavior in the visuals and report experiences you plan to use.
The demonstrated workflow starts by placing the image files in a Fabric Lakehouse. From there, the report uses HTTPS OneLake links to refer to the images. A dynamic measure can construct or select the image URL according to report data, while GUID-based references help avoid relying on workspace or item names.
The source does not provide the exact menu path for uploading files, the formula syntax for a measure, or the role-creation steps. Treat the list as the high-level sequence described, not as a complete click-by-click setup guide. Validate the final URL and permissions using the account and report context your audience will use.
GUID-based URLs are described as more resilient, not unbreakable. The publisher’s description explicitly warns that image URLs can still break, but it does not enumerate every failure condition. It is therefore worth checking the URL, the target file, and the viewer’s folder permissions when an image does not load.
OneLake access controls remain part of the implementation. A user who lacks read access to an image folder may not be able to see its files through the report. Test with a normal report consumer rather than assuming the author’s access will match everyone else’s.
The supplied material does not establish licensing requirements, supported image formats, specific visual compatibility, or whether this workflow is available in every tenant. It also does not give a complete migration process for existing SharePoint links. If you are considering a move, first identify the image URLs used by your reports, then validate a OneLake version and its permissions before replacing existing links.
SharePoint is not described as unusable for all purposes; the specific recommendation is about where report image files are stored and how Power BI retrieves them. The publisher’s guidance favors OneLake for this image workflow, while leaving the exact cases where an existing SharePoint link might work outside the detail provided here.
Store the image in a Microsoft Fabric Lakehouse, build an HTTPS OneLake URL to the file, and use that URL in Power BI. For a slicer-driven image, use a measure that returns the URL for the selected item.
Yes. The described approach uses a dynamic image measure so the image URL can change based on a slicer selection.
The source describes granting folder-level read access with OneLake security roles. It does not provide detailed role setup steps or specify required licenses.
No. The material recommends workspace and item GUIDs to make URLs more resilient, but also notes that image URLs can still break.