Office 365 roadmap

http://fasttrack.microsoft.com/roadmap

A profile management utility for Lync & Skype for Business

https://bounsky.com/

Avaya and Exchange UM integration - something you need to know about Exchange

https://johanveldhuis.nl/exchange-um-accepteerd-geen-oproepen-meer-na-de-upgrade-naar-sp1/

https://social.technet.microsoft.com/Forums/exchange/en-US/a156daf9-7793-43b6-bbb6-3bd282d5cf7a/um-2013-does-not-answer-calls?forum=exchangesvrunifiedmessaging

Exchange Server runs two unified messaging services, umservice.exe (on Exchange 2010 and Exchange Server 2013 Mailbox Servers) or Microsoft.Exchange.UM.CallRouter.exe (on Exchange Server 2013 Client Access Servers) that listens on TCP 5060 and UMWorkerProcess.exe (both versions of Exchange Server) that listens on TCP 5065 or TCP 5067. The correct process for connecting to Exchange Server unified messaging is to connect to TCP port 5060 and get back a SIP Redirect to either port TCP 5065 or TCP 5067. The reason for the redirect is that Exchange Server starts listening on 5065 and after a week starts a second process listening on 5067 and once the process on 5065 has finished all its call handling it will stop the process listening on 5065. This way Exchange Server manages the process, memory management, etc. without needing to restart the process if it goes bad – it just starts a process on the other port from the current process and directs all new calls at the new process.

  

Azure MFA demo

https://azure.microsoft.com/fr-fr/documentation/articles/multi-factor-authentication-how-it-works/#feature-comparison-of-versions

Skype for Business AutoAnswer call

http://shanselman.github.io/LyncAutoAnswer/


works ok with my SfB 64bit client

Skype for Business Survival Guide

http://bit.ly/Skype4bSG 

Two words about Lync Reverse Proxy requirements

Reverse proxy can provide

SSL pass-through - RP just passes HTTPS traffic without really changing it

SSL offload - HTTPS traffic is terminated at RP and then passed to internal host in HTTP.

SSL bridging - HTTPS is terminated at RP, proxy have a chance to read unecrypted traffic, then it would opn new HTTPS stream to internal server.

First and third methods are supported by Lync, but not SSL offload.

The prefered and less painful method is  SSL Bridging. You should use a public certificate on RP and a private one in Lync.