LinkedIn Twitter
Director, OpenShift Strategy at Red Hat. Founder of Rishidot Research, a research community focused on services world. His focus is on Platform Services, Infrastructure and the role of Open Source in the services era. Krish has been writing @ CloudAve from its inception and had also been part of GigaOm Pro Analyst Group. The opinions expressed here are his own and are neither representative of his employer, Red Hat, nor CloudAve, nor its sponsors.

4 responses to “Why I Think Office 365 Is Not (Yet) Ready”

  1. Sameer

    Hi Krishnan,
    Today read your 2 yr old article
    Doesn’t seem like gone big in two years.

    They are not able to attract too many clients.
    Is this because people still don’t have conviction in cloud computing???


  2. Chris Johnson

    Hi Krishnan,

    I wanted to correct you point about APIs. There are in fact LOADS of APIs for Exchange Online, Lync Online and SharePoint Online.

    In your example “If I want to build an app to manipulate the docs stored in Office 365, I can’t.” This is plain and simple wrong. SharePoint Online has a number of APIs you can use to work with content such as Web Services and the Client Side Object Model (XML/JSON). There are 3rd party apps that integrate with 365 using these today like Colligo’s products for PCs and iPads ( (i’m not affiliated, but i like their products)

    Exchange Online supports the majority of the APIs available to on-prem customers too. EAS and Web Services for example.

    Although i think some of your other point are good, i have some comments on a couple:

    – Simplicity. I agree things could be easier to understand. But 365 does A LOT more than Google Apps very basic functionality. So its no surprise its slightly more complex.

    – Scale. Time will tell i guess.

    – Mobile. I don’t really agree with you on this one. You are trying to compair apples to oranges a little on this i think. Office 365 has really good mobile support. There are loads of apps that connect to its various services. On iOS for example, you can use Lync Mobile for Voice, Colligo Briefcase for access to SharePoint documents and the built in Mail/Calendar apps for Exchange Online. They work offline (except voice of course) & I very rarely need to dive into a browser. In fact i hate doing anything in a browser, its plain painful IMHO even with modern HTML5 type apps.

    – Social. I guess it depends what you call Social. Public social stuff … sure you have a point. Enterprise Social? I disagree.

    Anyway … i started out just wanting to point out your misunderstanding on the API side of things … and ended up with a much longer post than intended.



  3. Chris Johnson

    Thanks Krishnan,

    For SP APIs a good starting spot is:

    I agree the ecosystem isn’t there yet. But it is growing and more and more apps are integrating like Colligo, SharePlus, Filamente to name a couple. They are out there, but just aren’t organized in an easy to consume list.

    On Mobile, i hope MS doesnt spend time improving the browser based experience. My vote is firmly in rich applications, native to the device. Call me a nay sayer, but i just don’t see a future in browser based apps anymore.