Store Business Central Telemetry in Azure Application Insights

Overview

Business Central telemetry needs a place to be stored, and the video names Azure Application Insights as that place. It walks through creating the resource in the Azure portal, from the introduction through setting the instance name and region, choosing the resource mode and workspace, and waiting for deployment.

The resource can be created in classic or workspace-based mode. The presenter says to always use workspace-based mode, since the workspace is where the data is stored and classic mode is deprecated. Deployment takes a few minutes, after which the resource is ready to be connected to Business Central.

Key points

• Business Central telemetry is stored in Azure Application Insights, which is provisioned in the Azure portal via Create resource.
• The resource is configured with subscription, resource group, name, and region (North Europe in the demo).
• Two resource modes exist: classic and workspace-based. The video says to always use workspace-based.
• The video describes classic mode as deprecated.
• In workspace-based mode, the workspace is where the data is actually stored.
• After review and create, deployment takes a few minutes, after which the resource can be added to Business Central.

Features

Every feature below: status not stated, demoed.

Quotes

• 0:00 “to get Telemetry data for business Central you need a place to store that data and that place is called application insights”
• 1:22 “you can choose between two different modes of the resource a classic and a workspace us should should always use the workspace uh based”
• 1:36 “the workspace is actually where the data is stored”
• 1:56 “within a few minutes I will get my application insights resource and I’m ready to add that to business Central”

Disclaimers in the video

• 1:22 subject-to-change: the classic is a deprecated mode