I would really love to have back the number of hours I wasted trying to figure out why I couldn't get into SharePoint online with powershell because mfa was active on my admin account ... but I guess that's water under the bridge now, as I'm finally back to working with MFA on.
Talking about consistency, it has always driven me mad how they seem oblivious to mismatches between GUI and powershell experiences. Examples:
In SharePoint 2010, you would "Retract" a solution in the Admin Center, but with Uninstall-SPSolution.
In SharePoint 2010, a timer job that appears as "Content Type Subscriber" is called MetadataSubscriberTimerJob if you want to work with it in Powershell.
In O365 even the security roles are completely crazy. What Microsoft calls them in documentation is different from what you'll find in the Powershell work, and even within the powershell assignments they aren't consistent, like some have an extra "service" thrown in, one has an extra word "support" thrown in, and "Password Administrator" is about as far as you can get from "Helpdesk Administrator." Here's my translator guide on that stuff ...
What it says in the support doc ... and what the "display name" is for Powershell work.
Global Administrator = Company Administrator
Billing Administrator = Billing Administrator
Exchange Administrator = Exchange Service Administrator
SharePoint Administrator = SharePoint Service Administrator
Password Administrator = Helpdesk Administrator
Skype for Business Administrator = Lync Service Administrator
Service Administrator = Service Support Administrator
User Management Administrator = User Account Administrator
Reports Reader = Reports Reader
Power BI Administrator = Power BI Service Administrator
Message Center Reader = Message Center Reader