This past week wasn't the finest for Microsoft's Office 365 service (see the ZDNet story), but it did give us an opportunity to see how Microsoft handles customer service and exercises their "financially-backed guarantee".
Here's what happened: on November 8th and again on November 13th, some Office 365 customers in North America reported that they were experiencing e-mail problems. Microsoft then acknowledged that some customers in the Americas had intermittent failures accessing Office 365 e-mail services. Customers reported various issues ranging from partial to full outages and also for various lengths of time, some for over two hours.
Office 365 is an enterprise service with a 99.9% up time SLA. There are 30 days in November, 24 hours per day and 60 minutes in an hour... 30 x 24 x 60 = 43,200 minutes (720 hours) in November. 99.9% of 43,200 is 43,157, or just over 719 hours. That means that if Office 365 was down for an hour or more for your business they missed their 99.9% up time guarantee.
What do you do to get your service credit? Normally you would need to report the outage and request your credit through the Office 365 portal's Service Request page. Microsoft would then credit a future bill to compensate for the lost service you paid for. In this case, though, Microsoft went above and beyond...
Microsoft announced in e-mails to Office 365 service admins (the account holders) the following:
I don't know for certain that all North America Office 365 accounts were sent this notice, but I didn't notice an outage on either of those days with either of the two separate Office 365 accounts I use daily. I'm being provided with a service credit apparently even though I didn't report an issue and didn't experience any issues. I imagine that the service credit is probably for the entire region.
Dear Admin:
The Office 365 team strives to provide exceptional service to all of our customers. On Thursday, November 8 and Tuesday, November 13 we experienced two separate service issues that impacted customers served from our data centers in the Americas. We apologize for the inconvenience these issues caused you and your employees.
We are committed to communicating with our customers in an open and honest manner about service issues and the steps we’re taking to prevent recurrences.
Here are more details about the recent issues:Across the organization, we are executing a full review of our processes to proactively identify further actions needed to avoid these situations.
• The first service incident occurred on November 8 and resulted in prolonged mail flow delays for many of our customers in North and South America. Office 365 utilizes multiple anti-virus engines to identify and clean virus messages from our customers' inboxes. Going forward, we have built and implemented better recovery tools that allow us to remediate these situations much faster, and we are also adding some additional architectural safeguards that automatically remediate issues of this general nature. • On November 13, some customers in North and South America were unable to access email services. This service incident resulted from a combination of issues related to maintenance, network element failures, and increased load on the service. These three issues in combination caused customer access to email services to be degraded for an extended period of time. Significant capacity increases are already underway and we are also adding automated handling on these type of failures to speed recovery time.
We understand that any disruption in service may result in a disruption to your business. As a gesture of our commitment to ensuring the highest quality service experience Microsoft is changing the standard credit procedure for this incident and is proactively providing your organization a credit equal to 25 percent of your monthly invoice. The credit will appear on a future invoice, and there’s no need to contact Microsoft to receive this credit. Please note, processing of the credit may take as long as 90 days.
If you have additional questions, please do not hesitate to contact us. Questions and answers about this and other Office 365 issues can be found at our Office 365 community site.
Thank you for choosing Office 365 to host your business productivity applications. We appreciate the serious responsibility we have as a service provider to you, and we know that any issue with the service is a disruption to your business and that’s not acceptable. We apologize for the inconvenience these issues caused you and your employees.
Thank you,
The Office 365 Team
Say what you will about Microsoft. Everyone messes up sometimes. I know that e-mail outages are frustrating and sometimes result in a real loss of revenue. In some cases e-mail is even more critical and lives and careers can depend on it. Realistically, though, there are alternatives for communication when e-mail goes down:
- You can still use the phone (even if you don't want to talk)
- You can temporarily use an alternate e-mail service (Yahoo mail or even those other guys whose name begins with a G)
- Most businesses still have fax machines - yes... they do.
- You could use a courier
- Just wait a while... it WILL come back.
In other cases, you exercise your objections to outages by demanding your money back (or a credit). Hit businesses where it hurts... in their wallets. This is how you encourage good behavior and how services improve... when customers demand it. Know your rights as a customer and stick up for yourself. Your vendors won't always treat you with respect and be as proactive as Microsoft was.
Here are some links to the Service Level Agreements for Microsoft's Office 365 and for Google's Apps for Business:
- Office 365: http://microsoftvolumelicensing.com/DocumentSearch.aspx?Mode=3&DocumentTypeId=37
- Google Apps for Business: http://www.google.com/enterprise/earthmaps/maps-sla.html
Monthly
Uptime Percentage
|
Service
Credit
|
< 99.9%
|
25%
|
< 99%
|
50%
|
< 95%
|
100%
|
Based upon the numbers from the top of this story, there are 43,200 minutes in November and 99% of that is 42,768 minutes or 712.8 hours. So unless you experienced more than 7.2 hours (43,200-42,768=432/60=7.2) of outage this month you just got the correct credit (25%) without having to submit a ticket.
The cloud isn't perfect. Is it better than what you could do on your own though? Could you do better security? Almost certainly not... I don't care how big or small your organization is. Could you beat the cost? I doubt it... calculate the cost of equipment, support engineers (not cheap!), outside consultants, ongoing upgrades, power, cooling, etc. Oh, then add in the cost of backup software, high-availability across geographically dispersed locations and more. Can you do that on your own? At any price?
The cloud is getting better though... and will continue to. Services improve and I would bet that eventually you will see the SLA guarantees creep up to four-nines (99.99% up time guarantee). In the meanwhile, though, if you need more up time than you can get from Office 365 you can consider a companion product so that your risk is spread across multiple vendors. One such product is Mimecast(PDF). They guarantee 100% up time for your e-mail. It looks good on paper, but I haven't tried it out yet. If anyone has experience with the product I'd love to hear about it.
In any case, I think Office 365 is like Democracy. Everyone says that Democracy is the worst form of government ever conceived... except for all of the others. Office 365 (and cloud services in general) is still a relatively new service and when it goes down it really stinks. I think its still much better than the alternatives though. The calculations that make cloud computing compelling haven't changed. Hold your vendors to their guarantees, but keep in mind that service is just going to get better.
No comments:
Post a Comment
Due to excessive spam, only registered users may post comments. Comments are unmoderated and post immediately but they are monitored. Inappropriate content will be removed promptly and will get you banned.
If you wish to communicate with me outside of this blog please e-mail me at scott@quitecloudy.com.