{"id":8792,"date":"2022-11-03T10:44:53","date_gmt":"2022-11-03T17:44:53","guid":{"rendered":"https:\/\/www.microsoft.com\/insidetrack\/blog\/?p=8792"},"modified":"2023-06-13T15:45:19","modified_gmt":"2023-06-13T22:45:19","slug":"understanding-our-business-with-app-telemetry","status":"publish","type":"post","link":"https:\/\/www.microsoft.com\/insidetrack\/blog\/understanding-our-business-with-app-telemetry\/","title":{"rendered":"Understanding our business with app telemetry in Microsoft Azure"},"content":{"rendered":"
\n
\n
<\/div>\n

This content has been archived, and while it was correct at time of publication, it may no longer be accurate or reflect the current situation at Microsoft.<\/p>\n<\/div>\n<\/div>\n

\"MicrosoftMicrosoft Digital Employee Experience (MDEE), the organization that is powering, protecting and transforming Microsoft supports a wide variety of apps and services across the organization that are used to engage with customers, track leads, fulfill goals and objectives, and deliver products and services. The apps we support come from several different sources: Microsoft product-group development teams, third-party vendors, and our development teams within MDEE. While Microsoft Azure has native tools to monitor most application components, our app portfolio\u2019s distributed nature makes it difficult to trace a customer’s experience along business processes, regardless of the underlying infrastructure. As the reach and responsibility of our app portfolio in Azure increases, so does the need for a more complete, concise picture of our end-to-end business process.<\/p>\n

Striving to serve the customer\u2019s needs<\/h2>\n

Like most large enterprises, MDEE supports a large and diverse app and service portfolio. Most apps and services have built-in logging and reporting for application, platform, and infrastructure components. However, many of our business processes require application data and business process-specific telemetry to complete the end-to-end user perspective. To effectively track business process dataflow in this environment, we need a standardized method for collecting data. After monitoring solutions collect data in a central location, we aggregate, combine, and manipulate that data to gain insights into user behavior and the end-to-end business process. The figure below presents an example of how application and business process telemetry are collected alongside application, platform, and infrastructure data to capture a complete business process workflow.<\/p>\n

 <\/p>\n

\"An
Capturing end-to-end business process telemetry.<\/figcaption><\/figure>\n

We use telemetry-based data solutions to address several issues and needs that Microsoft employees and business groups report:<\/p>\n