Blue Prism makes it almost impossible not to bash out something resembling proper, abstracted object oriented design (reusable objects, methods on those objects, etc).

Unfortunately, it does this in a hamfisted way that makes the product harder to learn and use than it needs to be. It's fine if that's all you use, but you're not going to be able to quickly crosstrain / ramp someone up on it.

IMHO, that defeats a core value proposition: enable non-developers to develop.

I've demo'd the MS offering (Power Automate), but haven't daily driven it. It's slick.

The question I have is where MS is positioning it. I don't think it's an independent product, so I think they might see it as filling in a gap in the O365 offering? I don't think legacy support is a major point for them, which will probably be good enough for most people.