That's what I was afraid of. Thanks. Any thoughts about dirsync at that level of O365 if they decide to move forward with the $5/mo product?
On Tue, Dec 15, 2015 at 11:29 PM, Jonathan Raper <[email protected]> wrote: > If you’re entertaining O365, you need to ditch Outlook 2007 and get on a > newer version. I strongly advise going with nothing less than 2013….and > consider moving to 2016 once it is proven. I’ve seen some quirkiness with > 2010 and O365. > > > > http://windowsitpro.com/blog/why-exchange-2016-ignores-outlook-2007 > > > > from that article “Exchange 2016 supports the same set of Outlook clients > as Exchange Online does“ > > > > Jonathan > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Richard Stovall > *Sent:* Tuesday, December 15, 2015 10:04 PM > *To:* [email protected] > *Subject:* [Exchange] O365 and standalone Outlook > > > > I have a garage client that is thinking about moving to O365's $5/mo plan > for e-mail hosting. My Google-fu is failing me at the moment, and I can't > seem to find the minimum version of Outlook required to connect via RPC > over HTTPS/Outlook Anywhere/whatever-they're-calling-it-now. Does anyone > know for sure if Outlook 2007 and newer will work? > > > > Thank you. This will be my first foray into O365 land and I'm sure this > won't be the last question. > > > > Cheers, > > RS > > > > PS Dirsync works at this level, right? Even the password hash option > that requires people to sign in to Outlook manually? >
