Usage, Adoption, and Archiving Requirements

Nearly every organization is required to retain communications data for compliance purposes. Organizations across all common verticals must follow strict regulations, and these regulations will carry over to the Lync infrastructure to retain data such as instant messaging conversations and web conferencing content. Additionally, some organizations require audio recordings of all calls for certain users. There are many ways to meet these requirements, including Lync Server 2013 built-in functionality, as well as third-party solutions.

It is also important to track the usage and adoption of the Lync system. Monitoring the usage and overall adoption of a Lync service is critical in the deployment and post-deployment stages. During the deployment, identifying how users are adopting the solution will provide key metrics for success of the project, as well as the return on investment (ROI) of the solution. Post-deployment, identifying how users are utilizing the system can provide insight into cost analysis, as well as performance tweaking metrics. These are just some examples of why it is important to monitor the usage and adoption of the Lync system. Many organizations have key performance indicators (KPIs) for their Lync deployment, and monitoring these areas is critical in reporting on the status of those KPIs.