Export (0) Print
Expand All

Security and Archiving

Office 365

Applies to: Office 365

Topic Last Modified: 2014-12-12

Microsoft Office 365 traffic (both signal and media traffic) is encrypted by using the Transport Layer Security (TLS) protocol. Anyone who intercepts a communication sees only encrypted text. For example, if a user accesses Lync Online IM, calls, and presentations while using a public Wi-Fi network, such as at an airport, the user’s communications are encrypted to potential interception by network “sniffers.”

The Microsoft Office 365 plans support at a minimum, Lync 2010. For customers with on-premises deployment of Lync Server 2013, a client version control feature lets you specify the versions of clients that you want to support. This can help control the costs associated with supporting multiple client versions.

Client version rules cannot be customized by Lync Online customers.

Lync Online provides archiving of peer-to-peer instant messages, multiparty instant messages, and content upload activities in meetings. The archiving capability requires Exchange and is controlled by the user’s Exchange mailbox In-Place Hold attribute, which archives both email and Lync contents.

All archiving in Lync Online is considered “user-level archiving” because you enable or disable it for one or more specific users or groups of users by creating, configuring, and applying a user-level archiving policy for those users. There is no direct control of archiving settings from within the Lync admin center.

For information about meeting content retention (independent from archiving), see Lync Meetings.

Data access is restricted to authorized users identified by the customer.
The following types of content are not archived in Lync Online:
  • Peer-to-peer file transfers

  • Audio/video for peer-to-peer instant messages and conferences

  • Application sharing for peer-to-peer instant messages and conferences

  • Conferencing annotations

Lync users can access Lync sign-in logs with one click in both Lync Server 2013 and Lync Online. If there were no errors during the sign-in process, the logs will be empty. If the user had problems connecting to the server, the logs will show the errors, the steps Lync made in order to connect to the server, and the results for each step. To learn how to access sign-in logs, see Helping troubleshoot Lync sign-in errors.

To view feature availability across Office 365 plans, standalone options, and on-premise solutions, see Lync Online Service Description.

If you have comments or questions about this topic, we'd love to hear from you. Just send your feedback to Office 365 Service Description Feedback. Your comments will help us provide the most accurate and concise content.

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
© 2015 Microsoft