MC1217651 High Major change

Power BI: End of support for on-prem SharePoint web part

  • Admin

Summary AI-generated

Support for the SSRS Report Viewer SharePoint Webpart ends April 13, 2026; use SSRS report embedding with URL parameters instead.

Suggested actions AI-generated

  • Plan transition from SSRS Report Viewer Webpart
  • Use SSRS report embedding with URL parameters

Written by Azure OpenAI (gpt-4.1) from the text of the post below. It can be incomplete or wrong; the original post is authoritative.

Original post from Microsoft

[Introduction]

We are ending support for the SQL Server Reporting Services (SSRS) Report Viewer SharePoint Webpart feature. This change aligns with our efforts to simplify integration and improve reliability by using modern embedding methods. Instead of the Webpart, we recommend embedding SSRS reports in SharePoint using URL parameters.

[When this will happen:]

Support for the SSRS Report Viewer SharePoint Webpart will end on April 13, 2026.

[How this affects your organization:]

  • Who is affected: Organizations using the SSRS Report Viewer Webpart in SharePoint.
  • What will happen:
    • The SSRS Report Viewer Webpart will no longer receive updates or support after April 13, 2026.
    • Users can still download and use the component, but it will not be maintained.
    • No changes will occur automatically in existing SharePoint environments; the feature will remain functional but unsupported.
[What you can do to prepare:]

No admin action is required for this change. However, we recommend transitioning to the alternative approach: embed SSRS reports in SharePoint using URL parameters

Learn more:

[Compliance considerations:]

No compliance considerations identified, review as appropriate for your organization.

Additional details from Microsoft

Summary
Support for the SSRS Report Viewer SharePoint Webpart ends April 13, 2026. It will remain functional but unsupported. Organizations should transition to embedding SSRS reports in SharePoint using URL parameters. No admin action is required, and no compliance issues are identified.