Feel that pain, Azure already resembling a proving ground for testing weaponized bad naming.

Ah yes I’ll try to search for technical details about a Function, cool how they named one of the most common Azure resource types using possibly the single most overloaded word in computer science.

Good thing they engineered and documented it all really great so no one has to find esoteric solutions to half baked implementations of things with names that sound maliciously generic!