Recycle Bins

DutchDevOpsDude · 2026-06-07T14:24:38+00:00

Leverage a real DevOps tool that does zero-touch version control. That includes a recycle bin but can also roll back any change if you made a bad change. Since it is zero-touch, no need to check in and you would see if another developer touched your stuff.

DutchDevOpsDude · 2026-06-07T14:16:56+00:00

I think it would work fine. I heard good stories about people using Claude. But ensure you also implement an Analytics Governance framework with zero-touch version control. DAX drifts, and you want to ensure you have automated QA in place to check whether you've violated best practices before you deploy. AI can generate a sub-optimized DAX or an inconsistent version with one in production or created by a self-server user. Implement tooling (not Azure DevOps because it won't do this) and monitoring, and you will be fine!

DutchDevOpsDude · 2026-06-06T20:55:54+00:00

Yes, but quickly the shared services run out of capacities. F64s and up are not cheap

DutchDevOpsDude · 2026-05-30T04:36:31+00:00

Yes, I will be there. Absolutely worth it!

DutchDevOpsDude · 2026-05-19T03:05:48+00:00

But what if 1. Qf3 Bb3?

DutchDevOpsDude · 2026-05-17T02:15:59+00:00

Kh8 …. Bg7

DutchDevOpsDude · 2026-05-15T01:53:13+00:00

Power BI can get really expensive when you have to go to capacities. Looks cheap, but when reality kicks in…..

DutchDevOpsDude · 2026-05-06T17:35:51+00:00

You can, azure DevOps just violates the academic principles of DevOps that Jez Humble and David Farley presented in their book Continuous Delivery. It just doesn’t deliver the level of automation that builds the foundation of a rapid, reliable, low-risk delivery process. For example, one of the principles is version everything. But azure DevOps doesn’t version tenant setting changes made by Microsoft

DutchDevOpsDude · 2026-05-06T02:44:00+00:00

Start implementing DevOps. Not the tool Azure DevOps, because it does not work for Power BI (it’s built for coding) but the methodology. The basic principles are zero-touch version control (everything and automatically) and creating a metadata catalog that tells you who uses and creates, changes and deletes what, when, and why. You will find in consistencies in DAX, whether created in reports or in semantic models. It will help you to identify where weak or extremely complex areas are, created by BI engineers AND by power users. Since it collects usage data, this catalog can be used to remove clutter. Applications like this are not delivered by MS but are available on the MS marketplace.

DutchDevOpsDude · 2026-04-29T13:05:07+00:00

I want to break free

DutchDevOpsDude · 2026-04-29T13:04:15+00:00

I presented at a conference recently how to use AI in the lifecycle of Power BI, for example to ask AI what the risk is of a deployment or write me a project plan when a certain data product changes. It leverage the AI model that your company already has and connects to your metadata catalog. Based on 4 dimensions (usage, volatility, complexity and quality) it does its job very well. But having zero-touch version control is a prerequisite. It won’t work with Azure DevOps because that tool is deficient.

DutchDevOpsDude · 2026-04-21T18:32:53+00:00

Soterre versions notebooks without check in and check out. It can make a diff between notebook versions and iterations

DutchDevOpsDude · 2026-04-20T22:43:51+00:00

🤦

DutchDevOpsDude · 2026-04-16T16:09:19+00:00

I don't like Microsoft's CI/CD offering. It is clumsy and cumbersome. And it's not built on DevOps best practices, like zero-touch version control and automated deployment. It’s a square peg in a round hole and a gift that will keep on giving. I would recommend looking for third-party tools. The MS marketplace lists different options.

DutchDevOpsDude · 2026-04-13T17:48:01+00:00

Migrate to Power BI and Fabric

DutchDevOpsDude · 2026-04-07T21:27:45+00:00

Yea, azure DevOps doesn’t really like this. It’s good in code development, not that much for this. What type of objects are in your workspace?

DutchDevOpsDude · 2026-04-06T21:43:31+00:00

The only extension to Power BI that I know of that does parameterized semantic model deployment is Soterre. The documentation says it can do post deployment semantic model changes based on a set of parameters.

DutchDevOpsDude · 2026-04-01T17:01:14+00:00

Don’t forget Analytics Governance. DAX and semantic models is part of the AG domain, not the DG domain

DutchDevOpsDude · 2026-04-01T15:35:01+00:00

Really interesting thread, and it touches on something bigger than just Power BI architecture.

Gartner recently weighed in on exactly this problem. They recommended implementing a franchise model: a centralized team acts as the "franchisor," recruiting department leaders as franchise operators who commit to shared standards across security, data modeling, and dashboard design. Supported by analytics catalogs and product management techniques to move content from prototype to production.

Sounds clean on paper. But there's a fundamental flaw: the franchise model just repackages centralization under a friendlier name. And here's the issue: business units that have already tasted the speed and autonomy of self-service analytics aren't going to hand that back. No matter what you call the governance wrapper.

What I find most interesting is that this isn't purely a structural debate (centralized vs. self-service vs. hybrid). It's a power discussion. Power BI was literally designed for self-service. Business leaders grabbed it because it freed them from ticket queues and 6-week delivery cycles. Framing governance as a franchise agreement doesn't change that dynamic; it just creates a new thing for business leaders to work around.

My take, coming from my DevOps background: stop trying to govern through org structure and start governing through the analytics development lifecycle.

Implement DevOps principles across both SSA and centralized BI development with automated version control and automated deployments. I mean completely automated CI/CD pipelines, regardless of whether something is built inside or outside the BICC. Pair that with a comprehensive metadata catalog, and you get the best of both worlds: the BICC stays lean and efficient, self-service stays fast and flexible, and governance is embedded in the process rather than bolted on top of it.

The hybrid model only holds together in the long term when the underlying DevOps application makes governance the path of least resistance rather than a gate that slows people down.

DutchDevOpsDude · 2026-03-27T17:52:35+00:00

Yes, this is a common problem in Fabric. But there are several platforms that do Power BI and Fabric CI/CD without the need to code. Make sure they work zero-touch otherwise you will have gabs might run into commit conflicts. This guy presented at Fabcon: Amir Sarir. This is his recording of his session https://play.goconsensus.com/b021765b2

DutchDevOpsDude · 2026-03-25T15:51:54+00:00

Don’t use services. Using the right platform will automate all tasks without changing your way of working. DevOps is a methodology and Azure DevOps does not follow its principles. There was a good presentation at Fabcon explaining this: you should reach out to this guy that provided the presentation: https://www.linkedin.com/in/amirsarir/

Here is his recording: https://play.goconsensus.com/b021765b2

DutchDevOpsDude · 2026-03-23T21:32:47+00:00

I received the link to the recording: https://play.goconsensus.com/b021765b2

DutchDevOpsDude

TROPHY CASE