Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!The Power BI Data Visualization World Championships is back! It's time to submit your entry. Live now!
I have two queries related to the Power BI landscape admin reports and would appreciate your guidance:
1) Deprecation of Power BI Integration within SharePoint Lists and Libraries:
As an admin, how can we identify all reports in the landscape that are impacted due to this deprecation?
Ideally, is there an API query or direct method to pull this information from the landscape metadata?
2) Deprecation of Bing Maps Visual in Power BI:
With the Bing Maps visual being deprecated and the recommendation to migrate to Azure Maps, what is the process to find all reports affected by this change
Solved! Go to Solution.
1. Not aware of such a deprecation. Have a link?
Anyway, you use the tenant admin APIs to enumerate semantic models and their data sources across your tenant
2. Same process. Use the tenant admin APIs to enumerate all reports in the tenant (ignore the ones in Pro workspaces), then use scripts to enumerate through all visuals in each page of each report to retrieve the visual type.
Needless to say, both of these processes can be a little overwhelming.
Hi @lbendlin,
I believe this is what the OP is talking about: https://powerbi.microsoft.com/en-us/blog/deprecation-of-power-bi-integration-within-sharepoint-lists...
Not a deprecation of using Sharepoint Libraries and Lists as a whole, just this specific feature that automatically creates a semantic model in a SPList personal workspace. .
If you found this helpful, cosnider giving Kudos. If I solved your problem or answered your question, mark this post as a solution.
Hi DPandey,
We are following up to see if what we shared solved your issue. If you need more support, please reach out to the Microsoft Fabric community.
Thank you.
Thankyou, @lbendlin, @tayloramy and @Poojara_D12 for your responses.
Hi DPandey,
We appreciate your inquiry through the Microsoft Fabric Community Forum.
We would like to inquire whether have you got the chance to check the solutions provided by @lbendlin, @tayloramy and @Poojara_D12 to resolve the issue. We hope the information provided helps to clear the query. Should you have any further queries, kindly feel free to contact the Microsoft Fabric community.
Thank you.
Hi @DPandey
Both of your queries relate to upcoming Power BI feature deprecations that require proactive monitoring across your organization’s report landscape.
For the deprecation of Power BI integration within SharePoint Lists and Libraries, Microsoft hasn’t yet provided a dedicated admin API endpoint specifically to list all reports or dashboards embedded via the old “Power BI integration” in SharePoint. However, as a Power BI admin, you can use the Power BI Admin REST APIs (specifically the Get Reports in Group and Get Report Embed URLs endpoints) or Microsoft 365 Audit Logs to identify reports that have SharePoint embed links (URLs containing “sharepoint.com/sites/…” or “_layouts/15/reportEmbed.aspx”). This helps detect reports currently relying on SharePoint integration. You can also export this data via Power BI Activity Logs or PowerShell cmdlets like Get-PowerBIReport to review embed configurations across all workspaces.
For the deprecation of Bing Maps, Microsoft recommends transitioning to Azure Maps visual, but Power BI doesn’t yet include a native admin-level API that flags visuals using Bing Maps. To identify affected reports, you can leverage the Power BI Scanner API — which scans the entire tenant’s metadata, including report definitions, visuals, datasets, and data sources. By exporting the scanner API output into a data model, you can search for reports where the visual type is "BingMap". This is the most efficient and scalable method to audit your entire landscape and identify which reports need updating.
1. Not aware of such a deprecation. Have a link?
Anyway, you use the tenant admin APIs to enumerate semantic models and their data sources across your tenant
2. Same process. Use the tenant admin APIs to enumerate all reports in the tenant (ignore the ones in Pro workspaces), then use scripts to enumerate through all visuals in each page of each report to retrieve the visual type.
Needless to say, both of these processes can be a little overwhelming.
Hi @lbendlin,
I believe this is what the OP is talking about: https://powerbi.microsoft.com/en-us/blog/deprecation-of-power-bi-integration-within-sharepoint-lists...
Not a deprecation of using Sharepoint Libraries and Lists as a whole, just this specific feature that automatically creates a semantic model in a SPList personal workspace. .
If you found this helpful, cosnider giving Kudos. If I solved your problem or answered your question, mark this post as a solution.
| User | Count |
|---|---|
| 21 | |
| 13 | |
| 8 | |
| 6 | |
| 4 |
| User | Count |
|---|---|
| 50 | |
| 43 | |
| 39 | |
| 13 | |
| 12 |