Well, first off, big developers are known to occasionally ship features that Apple wouldn't like. Facebook used their enterprise cert to ship a spyware VPN, and

Well, first off, big developers are known to occasionally ship features that Apple wouldn't like. Facebook used their enterprise cert to ship a spyware VPN, and Epic used a hotfix to ship a direct payments feature in Fortnite. So there's no reason to treat Adobe or Microsoft as more trustworthy based on reputation when you're specifically imposing business requirements on them that they won't like. If you're not looking at what they submit, eventually they are going to try and ship something under Apple's nose. Second, Apple really hates the idea of special rules for specific developers. When they make an exception for, say, Kindle; they don't just approve Kindle. They change the App Store rules to say "apps that are just viewing content purchased on other devices don't have to use IAP". The closest thing they have to special rules are entitlements; things like Zoom's special camera multitasking entitlement comes to mind. However, even that ultimately wound up being something other developers of video chat apps could ask for, they just didn't say anything about it until they got called out on it. The 1Password example you cite is plain 'ol trademark infringement. I imagine Apple isn't particularly interested in doing trademark enforcement for third parties, though I'm pretty sure they wrote the rules to allow them to do exactly that. This is definitely something where Apple could be more proactive, but there's a limit to how much they can do before you get people complaining about Apple going overboard.