Forum Discussion
Legacy SSRS reports after upgrading Azure DevOps Server 2020 to 2022 or 25H2
We are currently planning an upgrade from Azure DevOps Server 2020 to Azure DevOps Server 2022 or 25H2, and one of our biggest concerns is reporting.
We understand that Microsoft’s recommended direction is to move to Power BI based on Analytics / OData. However, for on-prem environments with a large number of existing SSRS reports, rebuilding everything from scratch would require significant time and effort.
Since Warehouse and Analysis Services are no longer available in newer versions, we would like to understand how other on-prem teams are handling legacy SSRS reporting during and after the upgrade.
Have you rebuilt your reports in Power BI, moved to another reporting approach, or found a practical way to keep existing SSRS reports available during the transition?
Any real-world experience, lessons learned, or recommended approaches would be greatly appreciated.
3 Replies
Hi, that is a very valid concern for on-prem Azure DevOps Server upgrades. If the warehouse and Analysis Services path is no longer available, I would treat reporting as a separate migration stream rather than part of the server upgrade only. Before upgrading, inventory the SSRS reports, identify which ones are still business-critical, and map them to Analytics/OData or Power BI equivalents so you can avoid a big reporting gap after the move.
Azure DevOps Server 2022 and 25H2 no longer support the legacy Reporting Warehouse or Analysis Services, meaning SSRS reports tied to those data sources will break after upgrade. The only supported path forward is migrating reporting to Power BI using the Analytics Service/OData feed. There is no official method to keep SSRS reports functional post-upgrade.
https://devblogs.microsoft.com/devops/azure-devops-server-2022-deprecation-of-reporting-services/
https://learn.microsoft.com/en-us/power-bi/connect-data/desktop-analysis-services-tabular-data
Thanks for the reply.
We may have found a workable approach for this and are currently validating it internally.
If helpful, I can also share the solution we are testing:
https://www.warehousesync.net/
If the test results continue to look good, I’ll come back and share an update.
