Look at Office for an example. It's a 30-year-old code base and everything about it shows. Office is clearly designed to maximize the number of tick marks marketing can put in their materials, and very little else.
I think a lot of the flack Office catches is because of how wide it casts its net. Just because you don't use a piece of functionality doesn't mean that it is bad.
I used to think Excel was the one exception to Office being awful until I was assigned a project creating an app in Excel using VBA and found out how incredibly fragile Excel is. This was about 6 years ago.
However, I don't think anyone thinks Office is bad because it has stuff they don't use, but that the stuff they do use either doesn't work well (e.g., Outlook) or it's too hard to use (e.g., Word).
Oh yeah, this is generally where I'd say things start to fall over. A development platform, it ain't. Generally my advice around VBA is that if you're at the stage you need anything but the simplest VBA, you probably want something else (Access for DB style work or Python/R for data munging).
Outlook has got much better - most of the previous issues around lockups and poor performance have improved if not gone away entirely. Can't speak for Exchange.
Enterprise also carries the meaning (again for me) of terribly architected software, possibly designed by someone who read about microservices and took it to the extreme that they've got an AWS lambda for doing strpad.