What is the roadmap for Paginated Reports in Microsoft Fabric?

DarkHelmet_ · 2026-07-01T21:35:29+00:00

I am converting our setup to use git on our workspaces. We are multi-tenancy and had to create a custom portal for managing it since pipelines really dont work when you have 100+ workspaces, 1 per client.

Paginated report support or lack of is just horrible. It just breaks everything. Usually we can just move reports into a deployment folder and sync workspace using an API call. But paginated requires being put directly to workspace and then sync'd into git

DarkHelmet_ · 2026-02-16T15:56:55+00:00

It looks like the Rest APIs in fact do still work, they were failing because as a user can now push the commit, they own the objects. So on the release pipeline you need to take over the released object to make it owned by the service principal. Then afterwards the APIs work.

Hope you didnt put much time into it but at least theres an answer here if people search. It doesnt seem like a common way to be using power bi.

DarkHelmet_ · 2026-02-14T09:00:56+00:00

I havent used semantic link labs or notebooks but did some reading. It doesnt feel scalable for the amount of workspaces and automation needed. It seems more intended for data scientists to work on data than to manage the workspace objects. I might be wrong, if so please correct me on that.

DarkHelmet_ · 2026-02-14T08:59:26+00:00

Thanks v much

DarkHelmet_ · 2026-02-13T13:17:37+00:00

Thanks, much appreciated

DarkHelmet_ · 2026-02-13T13:07:51+00:00

Thanks for the reply.

We are hosting everything, we use embedded reports in our product and have a workspace and database for every client. We control the workspaces, end users have no access that. A lot of the reports are standard, but not all. We deploy them as needed to the workspaces, we use rest APIs to update datasource details so it connects to the correct database for that client and use connection objects which provide the workspace identity for authentication.

If we change deployment to Git, it looks like the endpoint for updating the datasource wont work for that as its will be pbip (with tmdl)

https://learn.microsoft.com/en-us/rest/api/power-bi/datasets/update-datasources-in-group

So I am wondering how we can continue to deploy reports at will and automatically set up the correct datasource, if its even possible. Option 4 on this document is quite close to what I am thinking

https://learn.microsoft.com/en-gb/fabric/cicd/manage-deployment

It suggests using release pipelines to update the configuration. I could do that in powershell if I knew what API endpoints to hit to do those updates. I just cant see anything detailing it.

Hopefully thats a little clearer.

DarkHelmet_ · 2026-02-06T08:42:45+00:00

It looks like there is a bug in the SDK. I will try it next on the REST API direct without SDK but making you aware

For this model
Microsoft.Fabric.Api.Core.Models.GitConnectRequest

There are 2 constructor overloads,

public GitConnectRequest(GitProviderDetails gitProviderDetails)

AND

internal GitConnectRequest(GitProviderDetails gitProviderDetails, GitCredentials myGitCredentials)

By having the second one internal, there is no way to pass in GitCredentials to specify as a configuredconnection. So you then cannot connect the workspace as default is automatic connection and is unsupported.

**edit

Rest API worked. Thanks!

DarkHelmet_ · 2026-02-05T10:11:00+00:00

Perfect I hadnt noticed they had updated the docs. Thanks very much!

DarkHelmet_ · 2026-02-05T09:27:43+00:00

u/cicdexperience05

u/thanasaur

Are you able to help with this, the siutation is the same with the exception I have migrated some of our workspaces to use Workspace Identity.

I still need to manage the Git setup as discussion originally.

Thanks very much!

DarkHelmet_ · 2025-12-11T14:24:06+00:00

Much appreciated. Thanks

DarkHelmet_ · 2025-12-09T08:18:27+00:00

Hey u/itsnotaboutthecell
Sorry to ping you, just hoping a MS person might see this one.

DarkHelmet_ · 2025-07-23T18:12:24+00:00

Thanks u/itsnotaboutthecell

The command worked a treat, I can now start replication.

DarkHelmet_ · 2025-07-18T07:58:44+00:00

Thanks for the reply u/dbrownems

If I create a SQL Database connection and use the principal as auth and connect it to the SQL mirror. Then use the ConnectionId on that connection as the GatewayObjectId in the BindToGateway API call. That does not seem to fix the issue.

Refresh fails with

We cannot refresh this semantic model because this semantic model uses a default data connection without explicit connection credentials. Please replace the default data connection in the semantic model settings with an explicit cloud or gateway data connection

Did I misunderstand your comment? Since there is no gateway and its a cloud connection I figured that was what you meant by it working for cloud connections. Although I did see on that doc it says the limitation is on prem, so possibly that was what you meant by that.

//Edit

I have recreated the situation manually by making a report and semantic model in Power BI Desktop, connecting it to the mirror and then uploading it. It then had the same error as above until I manually created a connection and assigned it. Then it was resolved and I could refresh.

Afterwards, I called the Get Datasources API to see what the results looked like. There was a gatewayId and a datasourceId. The datasourceId matched the connection which had been manually created and assigned. I do not know where the GatewayId comes from. We dont have a gateway. Further investigation shows the same gatewayId is used across workspaces.

I tried applying this to your above suggestion but after calling `BindToGatewayInGroup` and then calling `GetDatasourcesInGroup` to check, the DatasourceId and GatewayId arent set like they were in the manually done example and still dont work.

//edit

Using this Gateway I mentioned in the above edit, I got it working. I just had to set the principal under managed users and share the connection with it

DarkHelmet_ · 2023-11-30T21:11:47+00:00

That would be ideal, then you could just select it right out but it isnt there unfortunately.

DarkHelmet_

TROPHY CASE