Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

A new Data Days event is coming soon! This time we’re going bigger than ever. Fabric, Power BI, SQL, AI and more. Don't miss out.

Reply
Roomie117
Helper I
Helper I

Migration SSRS to POWERBI

Hi @PowerBI @Everyone , 

Could you guide me the  best approach for migrating SSRS reports to Power BI. All of my data sources are SQL Server on-premises. Additionally, could you guide me through the step-by-step process migrating SSRS reports to power Bi?
When I publish directly, I’m unable to see the semantic model. 

Thanks

 

1 ACCEPTED SOLUTION

Hi @Roomie117 ,

 

When you are deploying paginated reports through GitHub, the process works a bit differently from publishing directly in the Power BI Service. Publishing from Report Builder is fine for quick, manual work, but in a Dev environment where you want repeatable deployments, GitHub becomes the source of truth.

 

The RDL files stored in your repository should be the versions that move through your environments, and your GitHub workflow can publish those reports to the workspace using Power BI’s APIs or PowerShell modules. The one thing GitHub cannot do is create data sources in the Service, so those need to be set up manually in the workspace ahead of time, along with the gateway connection for your on-prem SQL Server. Once the data source exists, your pipeline can publish the RDL and rebind it automatically.

 

This way, you keep a clean CI and Dev process while still supporting manual publishing if you ever need it, but GitHub should be considered the main deployment path when you're managing environments.

Best Regards,
Tejaswi.
Community Support

View solution in original post

11 REPLIES 11
AnalyticPulse
Solution Sage
Solution Sage

I am using GitHub for deployments from local to Dev. How should this be handled, considering that we can publish reports directly to the Power BI Service? 

Hi @Roomie117 ,

 

When you are deploying paginated reports through GitHub, the process works a bit differently from publishing directly in the Power BI Service. Publishing from Report Builder is fine for quick, manual work, but in a Dev environment where you want repeatable deployments, GitHub becomes the source of truth.

 

The RDL files stored in your repository should be the versions that move through your environments, and your GitHub workflow can publish those reports to the workspace using Power BI’s APIs or PowerShell modules. The one thing GitHub cannot do is create data sources in the Service, so those need to be set up manually in the workspace ahead of time, along with the gateway connection for your on-prem SQL Server. Once the data source exists, your pipeline can publish the RDL and rebind it automatically.

 

This way, you keep a clean CI and Dev process while still supporting manual publishing if you ever need it, but GitHub should be considered the main deployment path when you're managing environments.

Best Regards,
Tejaswi.
Community Support

Hi @Roomie117 ,

 

I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions.

Thank you.

Hi @Roomie117 ,

 

I wanted to follow up and see if you had a chance to review the information shared. If you have any further questions or need additional assistance, feel free to reach out.

Thank you.

@Roomie117 
do you have deployment pipiline for dev to QA and QA to prod?
if yes then its sorted already, if not then create a pipeline. 

alish_b
Super User
Super User

Hey @Roomie117 ,

 

I am assuming you are using the Power BI Report Builder to publish the SSRS reports as Power BI paginated reports.
In that case, the paginated reports do not have semantic model like the regular reports authored in Power BI Desktop do. You can simply edit the connection settings of the Paginated report itself (click on the three dots beside it > Manage) and update it accordingly.

Hope it helps!

I am using GitHub for deployments from local to Dev. How should this be handled, considering that we can publish reports directly to the Power BI Service? 

@Roomie117 , I am assuming you are using Github actions for the deployment and using either FabricPS module or the older PowerBIMgmt module. In either of them, you should be able to deploy rdl files to the service.
As for datasource connection creation, you need to create the connections in Power BI service and this cannot be created programmatically yet. You should be able to bind the report to the appropriate connection programmatically.

Hope it helps!



 

I am using an older Power BI model. However, when I publish the report to the workspace, I don’t see the source/report available to update in the Power BI workspace.

Hey @Roomie117 ,

 

Since you said the report itself is not present in the workspace, then maybe there is an issue in the deployment script. It could be possible that the deployment script was written with only pbix files in mind. If that is the case then you will have to extend the deployment script to consider the rdl files. 

 

Hope it helps!

Helpful resources

Announcements
May Power BI Update Carousel

Power BI Monthly Update - May 2026

Check out the May 2026 Power BI update to learn about new features.

Fabric SQL PBI Data Days

Data Days 2026 coming soon!

Sign up to receive a private message when registration opens and key events begin.

New to Fabric survey Carousel

New to Fabric Survey

If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.

Power BI DataViz World Championships carousel

Power BI DataViz World Championships - June 2026

A new Power BI DataViz World Championship is coming this June! Don't miss out on submitting your entry.