Well, no, he told us how he was controlling WordPress' memory usage, but not the web server's or PHP's. And Azure includes free databases, both SQL Server and MySQL, there's just limits (20mb). Which, y'know, is how it works.
I tried to add php_value memory_limit 128M in .htaccess (it's mentioned in the post), but I wasn't aware that Azure pays no attention to .htaccess and I should've been modifying web.config instead.
But I'm a tech guy. As a customer, I would expect Azure to configure the server and PHP on its own and not bother me with the quotas at all :)
You're a tech guy, and you expected IIS to use Apache configuration files?
EDIT: And as a customer, you're expecting managed hosting from a service that clearly isn't a managed hosting provider? Yeesh. There really are managed hosting providers in the world, if that's what you want.
.htaccess is supported not only by Apache. And I wouldn't be surprised if WAWS supported "at least a subset" of .htaccess configuration keys on Azure, since Microsoft has been trying to make a move into the LAMP world during the latest few years. I would consider it a marketable feature.
If we're discussing terms, then we must have a different understanding of what a managed hosting is. A service that allows you to select an application template, deploys the resources for you, sets up source control software, handles OS patches and host software installation for you, is _clearly not_ a managed hosting? What is then?
EDIT: I do admit that editing .htaccess was my own mistake. Not even sure where it came from actually, since the default WAWS WP template doesn't even contain it.
But I'm a tech guy. As a customer, I would expect Azure to configure the server and PHP on its own and not bother me with the quotas at all :)