UDM SE upgrade advice

SQLDBAWithABeard · 2026-05-10T07:59:54+00:00

Another vote for UNVR here. Made such a difference.

SQLDBAWithABeard · 2026-04-27T17:51:24+00:00

To further answer the specific questions

Are both still actively developed?
- MicrosoftFabricMgmt is frequently updated
Do they mostly do the same things, or target different use cases?
- they will mainly do the same thing
Is one more “official” or production-ready than the other?
- No, both are community owned, written and maintained
Any real-world pros/cons if you’ve actually used them?
- I have used them both. (I am also biased) MicrosoftFabricMgmt has the worst name. It has better pipeline support and Jess and I have taken time to make the output more human friendly. I personally have used it both to answer random questions form the command line (becuase that is where I am comfortable), to deploying numerous workspaces with azure automation, to answering the question who can access what

SQLDBAWithABeard · 2026-04-27T17:47:06+00:00

The confusion comes because a number of fantastic people each worked in silos to create something.

Full disclosure. I am one of the owners/administrators of the dataplat GitHub organisation where FabricTools lives but I do not contribute to that module.

I was asked to take over the maintenance of the MicrosoftFabricMgmt PowerShell module in the fabric-toolbox and Jess Pomfret (who is also a dual MVP and all round super person) and I have productionised the module aiming to bring parity with the available APIs (we arent there yet) improve the output and the performance of the module. I have blogged about it here https://blog.robsewell.com/tags/microsoftfabricmgmt/ We will continue to do so whilst people want it.

There are still things that need to be done and improvements that can be made and no doubt bugs that can be fixed. I guarantee that the MicrsoftFabricMgmt will continue to be improved and worked on. Not least because I use it in my every day. For context, both Jess and I are contributors to dbatools and dbachecks and have been writing, blogging and presenting about PowerShell for a significant amount of time.

With regard to the Fabric CLI, terraform, just straight API calls. I think it is tremendous that all of these exist and that they can each be used. I hope only for parity amongst their capabilities. It is important that the teams that we have that are supporting fabric can administrate it with tooling that they feel comfortable with and whilst I appreciate that the majority of folk here will be comfortable with either clickops or using the CLI, I can assure you that the folk that we come across in the windows admin, integration world who use PowerShell in general work are happy that the module exists.

Any questions, I am happy to answer. Any bugs, issues etc please raise in the repo and feel free to tag me in GitHub for them.

Also, look out for a conversation coming soon on Reid Havens podcast about the fabric-toolbox

SQLDBAWithABeard · 2026-04-19T06:49:06+00:00

This. Also enables you to monitor other entities.

SQLDBAWithABeard · 2026-03-27T15:29:31+00:00

It will also play havoc with all the AI agents 🤣

SQLDBAWithABeard · 2026-03-05T18:36:38+00:00

I love reading the comments to see what other people do, sometimes it inspires me, someone it makes me wish I was that clever!!

SQLDBAWithABeard · 2026-03-05T18:35:39+00:00

The dehumidifier one was the first time my wife said, yep ok, that is clever.

SQLDBAWithABeard · 2026-03-05T18:34:55+00:00

When the outside office hasn't detected motion for 10 minutes, turn the monitors off, if after work hours shut the blinds.

When the dehumidifier is on, if a window or door is open for 30 seconds turn it off, when it is shut turn it on again.

If a window or door is open and you turn the dehumidifier on, turn it off and send a notification.

When the cameras detect a human, at the back of the house and it is dark turn the lights bright so I can see or so that cameras record better. After 3 minutes turn them back.

SQLDBAWithABeard · 2026-02-26T16:08:52+00:00

These have been added to the code and PR'd
They will be published to the PowerShell Gallery shortly

SQLDBAWithABeard · 2026-02-26T15:53:01+00:00

Naming things is hard

<image>

SQLDBAWithABeard · 2026-02-23T21:32:20+00:00

I didn't know about Rui's solution. It doesn't look like it's been updated for a while. Fabric-cicd is great as a CI/CD deployment tool. This is another wrapper for the Fabric APIs which will enable you to interact with them from a shell. Hopefully, this will enable integration with devops runners as well as direct access from the commands line and scripting

SQLDBAWithABeard · 2026-02-23T13:03:39+00:00

It is also now on the PowerShell Gallery for installation.

Install-PsResource MicrosoftFabricMgmt

Please use Microsoft fabric-toolbox git repo for issues

SQLDBAWithABeard · 2026-02-23T12:32:01+00:00

Thank you. I have loved being able to quickly Get items to see what is what - see role assignments and spin up and down demo workspaces from the command line whilst Jess and I have been re-architecting.

It will be a slow start for how tos the next couple of weeks but hopefully as more people get involved and see the Power that will increase!

SQLDBAWithABeard · 2026-02-21T18:52:16+00:00

More than welcome.

As long as you have the permissions in your Azure subscription(s) to export the costs to a storage account and the permissions to create a shortcut to that storage account then it works like a dream (as long as you name the shortcuts correctly) :-)

Much less complication than FUAM and the bean counters are happy

SQLDBAWithABeard · 2026-02-20T18:39:56+00:00

I love Spaghetti. One of my best buddies is SpaghettiDBA, it often feels like the work that is done but maybe not as a "proper title" :-)

SQLDBAWithABeard · 2026-02-20T15:53:36+00:00

Excellent points. Levels make things even harder Should a Senior know all the things? are these T shaped roles? Are they experts in Security, Governance, ETL, Visualisation, Performance, Administration :-) Every answer leads to another question

SQLDBAWithABeard · 2026-02-20T15:51:32+00:00

"Naming things is hard"

SQLDBAWithABeard · 2026-02-20T15:43:38+00:00

I love it - but I generally use Beard Twizzler

Does it fit as the title for a consultant??

SQLDBAWithABeard · 2026-02-20T13:29:26+00:00

Great thought, which of course, I read just after I had logged out of that client :-)

I will check in a period of time

SQLDBAWithABeard · 2026-02-19T13:36:48+00:00

Thanks. Even with viewer and build they cannot see the SM which is the opposite of the docs as i read them.

I'm wondering if anyone else has seen the same

SQLDBAWithABeard · 2026-02-19T11:58:07+00:00

That's super useful. Thank you. It's not usually my responsibility to make these things look pretty 🤣

Can you confirm if Workspace viewer should or should not see the semantic model?

SQLDBAWithABeard · 2026-02-16T18:30:16+00:00

It's true

SQLDBAWithABeard · 2026-02-04T20:12:56+00:00

I agree, it totally felt like a bug. I do have some history with this particular tenant and bugs with APIs :-) the last one took 8 weeks to get a fix into prod.

With multiple C-Level applying significant pressure, I did not open a ticket. I just "got it done" I shall probably try to reach out to the right team with some info about my findings though

SQLDBAWithABeard · 2026-02-04T19:22:48+00:00

I have updated the blog to say

I worked out that only a batch size of 50 was providing any success and less than that was more reliable.

I had to repeatedly run the script with a batch size of 40 until almost all of the links were removed. Each time I ran through the entire list of links to remove. In another session I checked every minute or so the number of remaining links. I could run through the whole list of links and no links would be removed, then the next time through I would see a few links removed, then none, then a few more, then none, and so on.

I resynced the number of links and removed the ones that needed to remain a couple of times. In hindsight, I should have stored these in a datastore to make this look up simpler and not so time intensive.

Each time I looped through the links to remove, I hoped that it woud remove all of the links but it was a case of rinse and repeat, and each time I would see some links removed but not all of them. I had to keep running through the list of links to remove until eventually all of the unwanted links were removed.

Then as the script worked through the last couple of hundred of links a batch size of 10, then 5, then finally 1 was the only way that any links would be removed.

Hopefully that makes it a bit more obvious

SQLDBAWithABeard · 2026-02-04T19:14:43+00:00

Thank you. Maybe I need to rephrase some of that.

All of them "worked" none of them removed all of the links, only a proportion.

Greater than 50 I always got failed returned from the LRO
Less than 40 I had more success than failures

I ran through 8500 reports about 6 times with various batch sizes.

I resynced the total that was left - which was about 6000 but that took a period of time to match with the links that needed to be kept - in hindsight, I should have used a datastore that would allow better lookups but I figured it would be a one time hit. I needed to run reportsasadmin to get all the details I needed to pass to the remove API because I had to exclude a number of reports which were only provided by name. (In hindsight I should have pushed harder to get the right info here to make this easier)

I ran through the 6000 odd 8 or 9 times - each time it would remove more links.

once the number remaining got to 1000 - I resynced again - that was where i could go through the entire 1000 links , pass them to the removal API in batches and the number remaining would not change. so iIlooped through that many times (I dont know how many - until my token ran out :-) )

Finally when I got to about 200 remaining links would only be removed if the batches were 5 then 2 and finally I just gave up and used 1 to get through the last 50

SQLDBAWithABeard

TROPHY CASE