Microsoft in the clear to add Google CalDAV support to Windows Phone

Microsoft in the clear to add Google CalDAV support to Windows Phone

Summary: Even though Google is dropping support for the CalDAV sync interface later this year, it looks like Microsoft is among those developers 'whitelisted' to work with it.


Google's surprise announcement on March 13 that it is shutting down support for the CalDAV application programming interface (API) seemingly isn't going to set back Microsoft's plans to incorporate support for Google's calendar syncing protocol.


At the end of January 2013, Microsoft and Google came to a last-minute agreement to extend Google's support of Google Sync, which is built on Microsoft's Exchange ActiveSync, until July 31 -- instead of terminating it by the end of January, 2013, as previously announced. In the interim, Microsoft would build support into the Windows Phone operating system for CalDAV and CardDAV, the Google calendar and contacts sync protocols, the companies announced.

Yesterday, however, Google announced CalDAV API support was being discontinued on September 16, 2013, with the Google Calendar API becoming the CalDAV replacement. However, according to Google's blog post on the topic, some unnamed "whitelisted" developers would be able to continue to use CalDAV.

Google's CalDAV page already lists the API as being "deprecated." A note on the page adds "If you think you have a compelling use case and would like to be whitelisted for the new version of CalDAV API, please fill out this form."

I asked Microsoft officials if the Windows Phone team was among the whitelisted developers. No word back so far.

Google, however, confirmed this will not impact the agreement with Microsoft and that the Softies will still be able to implement CalDav support on Windows Phone.

The Windows team is not going to be adding CardDAV or CalDAV support for users who are trying to connect to a Google account via Mail/Calendar/People after January 30. Here's Microsoft's guidance as to how these users can sync their Google accounts with Windows 8 and Windows RT.

Microsoft officials haven't said how the company will update the Windows Phone 7.x or 8 operating systems to include support for CalDAV. Microsoft is believed to be working on a new minor update to its Windows Phone 8 operating system, known internally as GDR2 -- which may be ready this summer -- which could possibly include the support. 

Topics: Windows Phone, Google, Microsoft, Software Development


Mary Jo has covered the tech industry for 30 years for a variety of publications and Web sites, and is a frequent guest on radio, TV and podcasts, speaking about all things Microsoft-related. She is the author of Microsoft 2.0: How Microsoft plans to stay relevant in the post-Gates era (John Wiley & Sons, 2008).

Kick off your day with ZDNet's daily email newsletter. It's the freshest tech news and opinion, served hot. Get it.


Log in or register to join the discussion
  • What the heck

    Heh, so it's clear now. Google's cutting down the power users. I hope it won't stay that way though.
  • good, there is choice

    Apple and the plenty of Open Source projects that back and support CalDAV.

    It's Google's choice to shut down services that don't provide enough data mining for them.

    But, what is interesting is Microsoft's position. Are they intending to support CalDAV in their products, or not?
  • I don't get it

    People who already had google accounts synced can still use EAS, and MS isn't supporting caldav and cardav after the why the hell is MS implementing caldav and cardav?
    • Re: I don't get it

      Maybe because iOS uses CalDAV to sync with Google's calendars? The CalDAV is not completely discontinued, it's just not public matter anymore. Only the few chosen ones can use it.
      • iOS CalDAV

        iOS uses CalDAV to sync primarily with iCloud. Apple's OS X Server uses CalDAV for providing the calendar service too. It just happens by coincidence that google are using CalDAV so that you can use Google calendar services with iOS and OS X.
  • I have problems with where Google is going with this

    My initial feel is users are getting hurt.
    • About face...

      A month ago, they said that they were dropping support for Microsoft's AES, because it is proprietary and bad, when there are open protocols, like CalDAV and CardDAV, now they are saying CalDAV is bad and people should switch to Google's proprietary interface...

      So which is it? Are open protocols good or bad? Are proprietary protocols good or bad?

      I guess the answer is, as long as it is Google's own proprietary protocol, it is better than an open protocol, but an open protocol is better than a near industry standard, if it comes from Microsoft...
  • That's why enterprise don't give a sh** about Google.

    • Exactly

      Didn't Google just tell customers to start using CalDAV because they were getting rid of Google Connect? And now they're switching it again??

      All of Google's services should be considered a beta.
    • Make up your mind Google?

      I guess they want to try out a different API and discontinue it to keep everyone on their toes.

      Make a decision and stuck with it for pete's sake.
  • So they cut EAS because its proprietary and say go CALDAV its open

    Then they say we're cutting CALDAV, go with our proprietary calendar api. How google of them.
    Johnny Vegas
  • Lack of Windows 8/RT support appalling. Their workaround for getting Google Services is to just get mail. They offer a solution for adding a Google account to your Microsoft account, but that's only for contacts. No calendar on my Windows 8 laptop I guess.

    Furthermore, one of my accounts affected is an Apps account for work. Google said they'd still support EAS for Apps customers. Guess not.

    For my personal email, I could switch over to Outlook, but none of this wants me want to run with open arms to Microsoft just because they won't do CalDAV on Windows 8/RT. As for work email, tough luck I guess.

    The upside is that the mail and calendar apps are so awful on Windows 8/RT that I don't use them anyway. It's just annoying to be a Microsoft and Google user in this situation, not being able to use the products/services as intended. I feel like I'm a kid stuck in the middle of a messy divorce.
  • CalDAV is NOT Google

    "Google Calendar API becoming the CalDAV replacement" for Google maybe, I bet OpenSourcers and self hosters stick with RFC CalDav.

    Which means your article, like many, is fundamentally flawed in failing to notice that CalDav support on WP8 is practically non-existent in that it ONLY works with Google accounts.
    beau parisi