I'm really not much of a reference, being technically very inexpierienced in the field. From a development perspective, the integration with visual studio and sql server managment studio makes it very comfortable to use, if your web-app is developed with those tools. Though the "one-click" publish method rarely works as advertised, once you have the site deployed and working, updating any aspect of it does indeed become almost a one-click afair. Well, at least for simple apps like websites.
On the service provision side, well... azure is really kind of too big to just host a website. Azure is designed to be a rentable data-center with flexible scaling, redundancies and globaly distributed failover servers. So if I got a million visitors tomorrow between 10 and 12 for some silly reason, I allegedly could keep the site going with a few mouseclicks, or even automatically if I configured my scaling options in advance. I don't think I would want the bill for that, though. The whole system is designed so you pay for the resources you actually use, which comes with the disadvantage that I currently don't know the exact monthly costs...
Another reason that I went with azure though is that I know that it can very well get a potential employers attention. Azure is primarily targeted at businesses, and having working experience with it can be an asset when looking for a job.