5 ms·
My experience falls in line with yours. I had an MVP in azure web services. I had 20 users in my "beta" phase that were using the product and giving me feedbac
by banashark 7y ago
My experience falls in line with yours.
I had an MVP in azure web services. I had 20 users in my "beta" phase that were using the product and giving me feedback.
One day, I got a message that I need to update my billing method. Strange, I was using mostly free tier with one paid component and the card on file was good til 2022, but ok. I put in another card because maybe there's something wrong with the system.
The next day I get a call that the site isn't working from one of my beta users. I log in and all of my azure resources are gone.
I immediately try to reach out to azure support via various mechanisms (their support chat, email, twitter, etc). Funny enough, twitter is always the fastest way to get support. Just write that something bad happened and tag their product, and you get someone who can communicate. However, they just redirected me to their support channel.
Two days go by and I get a template email response. I have an email chain going back and forth over the week to try and get the resources restored.
In the end, they tell me that not only will they be unable to restore my resources (a production database. the backups were all "gone" because the resource didn't exist anymore), but that I had to create a new azure account to use any services because of how screwed up my account got.
I tried escalating, but received the same response.
Now I just go with AWS. I'd even go with google as long as they don't delete my production database.
I've previous experience as a Devops engineer for a Large company which at the time was one of the larger customers of Azure (as in they'd put our company on the marketing materials). Support was obviously better when we could get a turn around time of <1 day to talk to an engineer that worked on a piece of infrastructure. Still wasn't a pleasant experience.
It's really unfortunate, all of this. I know that there are so many teams that are putting out great products, but their cloud approach is awful. _Some_ of the offerings are actually pretty nice, but combined with UI churn, the worst support (I'd rather take googles non-existent support as long as my data doesn't get deleted) of all cloud providers (IME) and empty apologies on the internet (you can say you're sorry, but I don't believe you unless you act on the mistake), I don't see myself going back anytime soon.
- dtrailin 7y agoTypically in the free tiers there is a caveat in the service agreement that it is not meant for production services and your resources can be shut down at any time. It's important to read the fine print.
- banashark 7y agoThis is good to know. I'll definitely have to check more fine print when deciding to have certain services on lower tier. In my case, I was paying for the database and the object storage, both of which had their contents (db data and backups) lost.