Microsoft Graph support

ozy

Genuine question about Grommunio current status.
I remember having read somewhere that Grommunio could implement Microsoft Graph API. Is that something planned or in the works ? The only thing I can find is grommunio-next which hasn't seen a commit for awhile.

Thanks for insight.

WalterH

ozy Microsoft Graph API

It is in development but there is currently no ETA.

ozy

Thank you.
I am wondering because of how this API could be leveraged in the future for mail archiving, since EWS is to be sunset.
Best regards.

WalterH

ozy since EWS is to be sunset.

However, this only applies to M365. For all on-premises Exchange installations, EWS remains active.

ozy

True, but on-premises Exchange is quite dead since MS decided that even on-premises must now be linked to O365, so there's no point anymore for this.
Only older on-premises Exchange will continue serving EWS for a while.

mwilliams

ozy

this is (wrong) hearsay.

EWS is discontinued in Exchange Online and in Online only. Not in Exchange, neither 2019 or SE.
I'm curious on where your statement "must now be linked to O365" comes from. There is no such thing as forced hybrid. Personally being close to some at MS, never heard about such thing - neither officially nor inofficially - no statement from microsoft I could find either. the only thing you are "forced to" is the license model switching to subscription only -> that has nothing to do with the hybrid setup.

mwilliams

ozy

aside - back to your question: we are in fact making great progress, and our first estimate for a usable prototype will surface sooner than you might expect.

ozy

@mwilliams I did mean Exchange SE linked to O365 in terms of "subscription service", not hybrid setup. I really hate the "you can't buy your software anymore" paradigm, on top of the "Servers needs to phone to O365 console regulary" scenario.
Anyway, I tend get away from O365 as much as I can nowadays, for those exact sovereign questions.

But you're right, I genuinely thought EWS was sunsetted even on Exchange SE, so my reasoning about not using EWS for archiving in the future was wrong. Thanks.