3 ms·

Disclosure: I work at Azure. We're doing our best, but we're not going to suggest there's not more to do. Every major cloud provider has had issues at one poin

Disclosure: I work at Azure. We're doing our best, but we're not going to suggest there's not more to do. Every major cloud provider has had issues at one point or another (I formerly worked at Amazon and Google), and I'll just say - we hear you, and we are fiercely committed to earning your trust.

lenticular 8y ago
I'm sure you are, and I wish you the best of luck. I'd rather spend money with Microsoft than Amazon, everything else being equal. One way that Azure could really improve on Amazon is docs/usability, for which AWS is terrible.
- dpcx 8y ago
  Do I understand your comment to mean that Amazon has terrible documentation around AWS? Because if that's the case, I'm truly curious what documentation you find terrible. It can be confusing at times for me, but from my experience, that's mostly due to the fact that there's so many different options for some things.
  - jstanley 8y ago
    For one, it is practically impossible to work out how much something is going to cost.
  - sl1ck731 8y ago
    I just ran into an issue with the way they blog their documentation. It isn't hierarchical from what I can tell and they don't go back and update blogs to point you at the latest document. I wasted a lot of time going step-by-step through one to find out it was deprecated. It is a problem because a lot of the good documentation about overall usage or architecture for some reason is in this blog format but I can see it just being written off because "its just a blog". They also leave a lot out of the true documentation such as Landing Zone stuff (in fact they hide this one entirely) and Application Discovery Service (they make no mention how the agents work). There are plenty of other minutia that I have had to contact our rep. to get from the product team. The most common or basic stuff has some great documentation. But once you stray into the "weird" it isn't uncommon to see 2 or 3 line documentation pages about something.
    - CodeWriter23 8y ago
      The deprecated recipes etc. problem is not limited to AWS. I’ve trained myself to observe dates on what I’m reading, and digging deeper if it’s more than 2 years old (or 1 year old for moving targets like newer frameworks/services) especially when learning something new.
  - robohoe 8y ago
    The CloudFormation docs could definitely use some help. Often the examples they provide for Resources definitions are poor in content. Especially on some lesser known Resource types.
salex89 8y ago
I work with Azure daily, my company uses tons of IaaS on all cloud providers, very dynamically. I'm mostly concentrated on Azure. First I want to say, thank you for your service, keep it up, there is a lot to be done, but I see progress. Secondly, please, get your teams together and start communicating. We encounter a lot of issues with things that should just work or should be much simpler. Sometimes we contact support and just get handed from team to team without actually finishing something. Third, please, oh, please, get your SDKs (especially the Python one) fixed. It looks like every new build breaks something, sometimes even the same version on multiple installations since there is a lot of variable versioning done under the hood... Sometimes I get a feeling a lot if things are "leaking" towards the customer. Wanna change an instance type? You get a "instance not available in cluster" error, or something similarly undocumented. Wanna copy a snapshot between regions? Good luck with that, and hope you've got some retry logic and a hell of a timeout. Keep pushin'! :)

lenticular 8y ago

I'm sure you are, and I wish you the best of luck. I'd rather spend money with Microsoft than Amazon, everything else being equal. One way that Azure could really improve on Amazon is docs/usability, for which AWS is terrible.

dpcx 8y ago
Do I understand your comment to mean that Amazon has terrible documentation around AWS? Because if that's the case, I'm truly curious what documentation you find terrible. It can be confusing at times for me, but from my experience, that's mostly due to the fact that there's so many different options for some things.
- jstanley 8y ago
  For one, it is practically impossible to work out how much something is going to cost.
- sl1ck731 8y ago
  I just ran into an issue with the way they blog their documentation. It isn't hierarchical from what I can tell and they don't go back and update blogs to point you at the latest document. I wasted a lot of time going step-by-step through one to find out it was deprecated. It is a problem because a lot of the good documentation about overall usage or architecture for some reason is in this blog format but I can see it just being written off because "its just a blog". They also leave a lot out of the true documentation such as Landing Zone stuff (in fact they hide this one entirely) and Application Discovery Service (they make no mention how the agents work). There are plenty of other minutia that I have had to contact our rep. to get from the product team. The most common or basic stuff has some great documentation. But once you stray into the "weird" it isn't uncommon to see 2 or 3 line documentation pages about something.
  - CodeWriter23 8y ago
    The deprecated recipes etc. problem is not limited to AWS. I’ve trained myself to observe dates on what I’m reading, and digging deeper if it’s more than 2 years old (or 1 year old for moving targets like newer frameworks/services) especially when learning something new.
- robohoe 8y ago
  The CloudFormation docs could definitely use some help. Often the examples they provide for Resources definitions are poor in content. Especially on some lesser known Resource types.

salex89 8y ago

I work with Azure daily, my company uses tons of IaaS on all cloud providers, very dynamically. I'm mostly concentrated on Azure. First I want to say, thank you for your service, keep it up, there is a lot to be done, but I see progress. Secondly, please, get your teams together and start communicating. We encounter a lot of issues with things that should just work or should be much simpler. Sometimes we contact support and just get handed from team to team without actually finishing something. Third, please, oh, please, get your SDKs (especially the Python one) fixed. It looks like every new build breaks something, sometimes even the same version on multiple installations since there is a lot of variable versioning done under the hood... Sometimes I get a feeling a lot if things are "leaking" towards the customer. Wanna change an instance type? You get a "instance not available in cluster" error, or something similarly undocumented. Wanna copy a snapshot between regions? Good luck with that, and hope you've got some retry logic and a hell of a timeout. Keep pushin'! :)