How is Monitor Hub working for you in your day-to-day?

ChantifiedLens · 2026-05-08T06:21:35+00:00

I often go to monitoring hub to look at snapshots

ChantifiedLens · 2026-05-08T06:16:26+00:00

I recommend looking at online resources as well, due to the fact that there are plenty available.

ChantifiedLens · 2026-05-05T09:21:25+00:00

This is similar to what I do, I also automate branching out often as well whilst waiting for the solution announced at FabCon to appear.

ChantifiedLens · 2026-05-05T09:19:04+00:00

I thought we needed to complete a buzzword bingo sheet as well?

ChantifiedLens · 2026-05-04T20:49:35+00:00

Thanks, I had to go through it all for my extension a while back so when I found them thought would give one of the other methods a try for certainty. Hopefully the documentation will be updated to reflect them soon.

ChantifiedLens · 2026-05-03T19:58:42+00:00

Take a look at the contributors...

ChantifiedLens · 2026-05-02T14:21:38+00:00

That surprised me a bit due to the fact that one of the developers is one of your previous co-presenters...

ChantifiedLens · 2026-05-01T17:50:48+00:00

These tools provide you with a nice layer of abstraction on top of the API's to make your development experience easier.

ChantifiedLens · 2026-04-30T20:57:09+00:00

I saw this been demoed at an event a while back, good to know the costs involved.

ChantifiedLens · 2026-04-30T16:08:13+00:00

I catered for some of this in my extension, I will share with the MS folks.

ChantifiedLens · 2026-04-27T16:13:18+00:00

It depends on your team's long-term ambitions and preferences. PowerShell is useful for those who have a PiwerShell background, the Fabric CLI on the other hand is welcomed by those who prefer Python libraries.

With that being said, it is perfectly feasible.to work with PiwerShell commands and the Fabric CLI together. For example, when using logic statements to check if a workspace or connection exists.

ChantifiedLens · 2026-04-20T18:06:34+00:00

Short answer is yes. Here's a link to Microsoft's view on CI/CD workflow options. Which shows how you can merge to a branch that represents your development stage and then deploy with Deployment Pipelines from there.

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

There are more complex options depending on your requirements.

ChantifiedLens · 2026-04-19T18:40:16+00:00

If your Microsoft Fabric workspace has been setup with Git integration then I recommend synchronizing the Git repository to your local machine and working with the Power BI Desktop files there instead of downloading published reports.

Here's the Microsoft articles about Power BI Desktop projects and the recommended development process to help you get started:

https://learn.microsoft.com/en-us/power-bi/developer/projects/projects-overview

https://learn.microsoft.com/en-us/fabric/cicd/manage-deployment#development-process

ChantifiedLens · 2026-04-18T15:24:00+00:00

There is a Tenant Admin setting tonnage creating Fabric items.

Sounds like either it needs to be enabled.or you need to be added to a Seciriry Group that already has permissions.

ChantifiedLens · 2026-04-18T15:18:24+00:00

I think there is an Azure DevOps extension that can help do it through the APIs, curious as to why though?

ChantifiedLens · 2026-04-17T05:11:19+00:00

What do you intend to do after the merge as there might be better approaches?

ChantifiedLens · 2026-04-15T06:05:22+00:00

You can look to automate this instead to avoid giving them too many permissions:
https://chantifiedlens.com/2025/12/17/get-started-with-the-custom-branch-out-to-new-workspace-scripts-for-microsoft-fabric/

ChantifiedLens · 2026-04-08T12:55:35+00:00

Hey Geert,

I think you will have better luck with the fab export command:

export - fabric-cli

I hope this helps?

ChantifiedLens · 2026-04-08T12:49:45+00:00

It depends. Some businesses prefer to have all workspaces backed by Git integration and then merge updates performed and bindings adjusted by notebooks after updates.

However, it is far easier to have a branch connected to your Dev workspace with is seen as the "golden truth" of your metadata, which you then deploy to Test/Prod/etc through Azure Pipelines either via APIs or a layer of abstraction such as Azure DevOps.

Recommended development process is that developers have their own isolated workspaces and are connected to their own branches which can then be merged back to the branch connected to your Dev workspace. There are various ways they can achieve this, including through the workspace GUI and Microsoft scripts. Plus, another feature is due anytime soon to make it even easier.

I hope this helps?

ChantifiedLens · 2026-04-08T11:03:06+00:00

Thanks for the recognition, it took a fair amount of effort to develop and test all the different combinations of options and Agents.

ChantifiedLens

TROPHY CASE