A willow-brake parks desk creates a classic Application Insights resource and then cannot join its telemetry with the rest of the city’s Log Analytics queries. What should the developer create instead?
Select an answer to reveal the explanation.
Short Explanation
Workspace-based Application Insights is the current create path—telemetry lands in Log Analytics so citywide Kusto joins actually work. Classic Insights is the lonely silo the willow-brake team just hit.
Full Explanation
Microsoft’s default Application Insights create experience is workspace-based: the resource stores data in a Log Analytics workspace and participates in shared queries, workbooks, and alerts. Classic resources keep telemetry in a separate store that does not query with the rest of the workspace. Creating a workbook alone, routing only to Blob, or substituting Redis does not give Application Insights APM telemetry in Log Analytics.