MicrosoftRob Kennedy - The Oct 31 date was never about enabling TLS 1.2, as TLS 1.2 is already enabled within Office365 and secured communications can succeed over that protocol version today if the client endpoint supports TLS 1.2 (otherwise it would succeed over TLS 1.1 or TLS 1.0). The Oct 31 date has always been about enforcing and requiring a minimum of TLS 1.2 for secured communications with Office365, which requires that TLS 1.0 and TLS 1.1 be disabled and restricted from TLS cipher negotiations.
https://support.microsoft.com/en-ae/help/4057306/preparing-for-tls-1-2-in-office-365
The https://blogs.technet.microsoft.com/nexthop/2018/04/18/disabling-tls-1-01-1-in-skype-for-business-server-2015-part-1/ explicitly states that Lync Server 2010 is out of scope and will not function in a TLS 1.2 enforced configuration, so the information has been publicly available since April 2018. If you've got hybrid established to Office365 via Lync Server 2010, then you absolutely need to get your topology updated to at a minimum Lync Server 2013 (ideally Skype for Business Server 2015) in order to keep hybrid functional once MSFT makes the changes on Oct 31.
