Episode Details
Back to Episodes
Business Central Telemetry With Power BI: How To Use Application Insights, Fix Blind Spots & Spot Performance Problems Early
Season 1
Published 6 months, 3 weeks ago
Description
Imagine rolling a D20 every morning just to see if Business Central will behave. No telemetry? That’s like rolling blindfolded. In this episode, we start with that reality: admins and consultants trying to keep environments stable using only helpdesk tickets and vague “it’s slow” complaints, with no real visibility into sessions, deadlocks, or performance patterns. You’ll learn how to connect the Business Central telemetry feed to Azure Application Insights, why the one 36‑character Application ID in the Azure portal blocks more rollouts than any boss fight, and what changes in your day‑to‑day once those signals show up in Power BI as live dashboards instead of unreadable log walls.
WHY TELEMETRY IS YOUR HIDDEN MINI‑MAP
Telemetry is the hidden mini‑map you didn’t know you were missing. With it turned off, you’re not “keeping it simple”—you’re choosing to run blind: deadlocks stay invisible until payroll explodes, SQL latency creeps up over weeks, and misbehaving extensions quietly slow everything down. We walk through how telemetry captures behavior signals (sessions, page views, SQL durations, environment events) while leaving business data like invoices out of scope, why that matters for privacy, and how a single switch like “Skip Replication Counter Update” only becomes obvious once telemetry shows you the pattern behind the pain. Instead of reacting to disasters, you start seeing slopes and trends in time to schedule fixes on Tuesday afternoon instead of sacrificing your weekend.
CHOOSING THE RIGHT POWER BI APP (AND UNLOCKING REAL DATA)
Microsoft gives you two Power BI apps for telemetry—“Dynamics 365 Business Central Usage” and “Dynamics 365 Business Central App Usage”—and most admins install the wrong one for the question they’re asking. In this episode, we break down when to use the environment “Usage” app for system‑wide health (logins, client mix, performance across the tenant) and when to use the extension “App Usage” app to isolate a single customization’s behavior. You’ll learn the practical workflow: install from AppSource using the aka.ms shortcuts, understand why you see only sample data at first, and then plug in your own Application Insights resource so the dashboards light up with your real telemetry instead of mannequins. We also cover why a Power BI Pro license is non‑negotiable for live telemetry and how the automatically created workspace fits into your admin story.
THE AZURE PORTAL PUZZLE: FINDING THE APPLICATION ID
The final boss in this setup isn’t Business Central—it’s the Azure portal. We walk step‑by‑step through where the Application ID actually lives inside your Application Insights resource, why it never appears in Business Central or Power BI, and how to avoid chasing the wrong “ID” values for hours. Once you drop that ID into the Power BI app configuration, the portal maze suddenly pays off: sample dashboards flip over to live environment data, and your mini‑map fills in with real session, error, and performance streams. From there, we talk about access rights, why blank reports usually mean a permission problem rather than a broken setup, and how to share these insights with dev, ops, and leadership without drowning them in raw logs.
WHY TELEMETRY IS YOUR HIDDEN MINI‑MAP
Telemetry is the hidden mini‑map you didn’t know you were missing. With it turned off, you’re not “keeping it simple”—you’re choosing to run blind: deadlocks stay invisible until payroll explodes, SQL latency creeps up over weeks, and misbehaving extensions quietly slow everything down. We walk through how telemetry captures behavior signals (sessions, page views, SQL durations, environment events) while leaving business data like invoices out of scope, why that matters for privacy, and how a single switch like “Skip Replication Counter Update” only becomes obvious once telemetry shows you the pattern behind the pain. Instead of reacting to disasters, you start seeing slopes and trends in time to schedule fixes on Tuesday afternoon instead of sacrificing your weekend.
CHOOSING THE RIGHT POWER BI APP (AND UNLOCKING REAL DATA)
Microsoft gives you two Power BI apps for telemetry—“Dynamics 365 Business Central Usage” and “Dynamics 365 Business Central App Usage”—and most admins install the wrong one for the question they’re asking. In this episode, we break down when to use the environment “Usage” app for system‑wide health (logins, client mix, performance across the tenant) and when to use the extension “App Usage” app to isolate a single customization’s behavior. You’ll learn the practical workflow: install from AppSource using the aka.ms shortcuts, understand why you see only sample data at first, and then plug in your own Application Insights resource so the dashboards light up with your real telemetry instead of mannequins. We also cover why a Power BI Pro license is non‑negotiable for live telemetry and how the automatically created workspace fits into your admin story.
THE AZURE PORTAL PUZZLE: FINDING THE APPLICATION ID
The final boss in this setup isn’t Business Central—it’s the Azure portal. We walk step‑by‑step through where the Application ID actually lives inside your Application Insights resource, why it never appears in Business Central or Power BI, and how to avoid chasing the wrong “ID” values for hours. Once you drop that ID into the Power BI app configuration, the portal maze suddenly pays off: sample dashboards flip over to live environment data, and your mini‑map fills in with real session, error, and performance streams. From there, we talk about access rights, why blank reports usually mean a permission problem rather than a broken setup, and how to share these insights with dev, ops, and leadership without drowning them in raw logs.
Listen Now
Love PodBriefly?
If you like Podbriefly.com, please consider donating to support the ongoing development.
Support Us