Tagged: Exchange

Exchange Online Unified Messaging is transitioned to Cloud Voicemail

In this post I’d like to point out the most important aspects of the discontinuation of Exchange Online Unified Messaging (hereinafter: EXO UM, voicemail and auto attendant capabilities). EXO UM is discontinued as announced by Microsoft months ago. Now, Microsoft published an information regarding the planned transition towards Cloud Voicemail. Below a short summary of the announced information by Microsoft:

  • EXO UM will be transitioned and migrated to Cloud Voicemail in calendar year 2019 (not later than February 2020)
  • Voicemail messages can still be stored on Exchange Online as well as Exchange Server
  • You’ll receive a transition notification by Microsoft via Office 365 Admin Center
  • You can postpone the transition to Cloud Voicemail via the support panel in the Office 365 Admin Center (however before February 2020)
  • EXO UM with Lync Server 2010 will not be supported anymore and will not be transitioned
  • EXO UM with Lync Server 2013 will be transitioned to Cloud Voicemail
  • EXO UM with Lync Server 2015 will be transitioned to Cloud Voicemail
  • EXO UM Auto Attendants must migrated to Cloud Auto Attendant services
  • EXO UM Auto Attendants must be re-created on the Cloud Auto Attendant service

Conclusion, opinion and summary

EXO UM will be replaced by Cloud Voicemail. The EXO UM service will be transitioned to Cloud Voicemail based on Azure. To me it seems that it will not be a big difference for your users. They’ll still get voicemail and auto attendant capabilities. It’s more an slight cut over to a different backend for the same features.

However, if you are still on Lync Server 2010 you should consider to upgrade to Skype for Business Server to carry on providing voice mail and attendant services.

In case of many auto attendant services on EXO UM you should prepare and plan to re-create auto attendant services on Cloud Voicemail.

Further Resources

Exchange Server Role Requirements Calculator v8.4 released

To calculate your Exchange Server Role Requirements you can now use the latest version of the Exchange Server Role Requirements Calculator >>here<<. It supports you in planning your Exchange Server Deployment based on your requirements.

Further details on how to use the calculator you find in the link in the description of the above linked webpage.

Additionally you can check requirements >>here on TechNet<< or >>Exchange (2013) Deployment Assistant<<.

Kemp Loadmaster Templates – Lync 2013, Office 2013 Web Apps

Kemp Technologies bietet für Microsoft Lync 2013 (auch Exchange 2013) Templates an. Diese können beim Erstell von Lync VIPs auf einem Loadmaster dienen, z. B. für die Lync 2013 Webservices oder den Office 2013 Web Apps Server. Somit braucht die lange Anleitung für die Konfiguration eines Reverseproxys für Lync 2013 Mobility, Addressbook Download, … und Office 2013 Web Apps nicht mehr durchgearbeitet werden.

Template Import

Template Import

Template Verwendung

Template Verwendung


Auf dem NextHop-Blog wurde ein guter Beitrag veröffentlicht, der zeigt, wie ein KEMP LoadBalancer für Lync eingerichtet werden kann (http://blogs.technet.com/b/nexthop/archive/2014/02/14/configuring-reverse-proxy-access-to-microsoft-lync-server-2013-using-kemp-loadmaster.aspx)

Microsoft Office 2013-Produktfamilie für Geschäftskunden erhältlich

Die Microsoft Office 2013-Produktfamilie ist jetzt für Geschäftskunden erhältlich, die eine Volume Lizenz besitzen laut Redmond Channel (http://rcpmag.com/articles/2012/12/04/office-2013-via-volume-licensing.aspx).

Die Produktfamilie umfasst

  • Microsoft Office 2013
  • Microsoft Exchange 2013
  • Microsoft Lync 2013
  • Microsoft SharePoint 2013

Offizielles Statement von Microsoft: http://blogs.office.com/b/office-news/archive/2012/12/03/the-new-office-is-now-available-for-business-customers.aspx