Office 365 Planned Service Changes – December 2017 Updates

A quick post announcing the recent updates to the Office 365 Planned Service Changes series of posts:


Office 365 Planned Service Changes for 2017 | Updated: December 27, 2017

  • Moved Yammer notes to Word Online conversion to Archive
  • Moved Retirement of to Archive


Office 365 Planned Service Changes for 2018 | Updated: December 27, 2017

  • Added Mandatory use of TLS 1.2 in Office 365 - action required by March 1, 2018


Office 365 Planned Service Changes for 2020

  • No updates for December 2017


Hopefully this information is helpful in keeping pace and managing change in Office 365.


Comments (3)
  1. wrootw says:

    We are using internal SMTP based on IIS 6.0 on Windows Server 2012 to rely messages from internal systems to Exchange Online (based on official MS support article). I have checked traffic on the server via Wireshark and i can see it uses TLSv1.2 when talking to Exchange Online inbound server. So, i assume we are already ok with TLS 1.2 switch. But i would love to hear a definitive answer. As IIS 6.0 had no support for new TLS in the past. But i guess in this scenario and on WS2012 it actually supports it?

    1. Hi wr – does this recent post from the Exchange Team help address your questions?


      1. wrootw says:

        Not really. We don’t have on-premise Exchange. But as Windows Server 2012 has TLS 1.2 by default and we have latest security updates, i think we should be ok.

Comments are closed.

Skip to main content