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?

Workspace-based Application Insights is the current create path for new resources: telemetry is stored in a linked Log Analytics workspace, so willow-brake parks desk data participates in the same Kusto queries, workbooks, alerts, and cross-resource joins the rest of the city already uses. Classic Application Insights keeps its own separate store; that is why the desk cannot join its telemetry with citywide Log Analytics queries after creating the classic resource.

A workbook alone visualizes or organizes queries; it does not become an Application Insights resource and does not ingest APM telemetry by itself. Pointing classic Insights diagnostic settings only at Blob Storage archives blobs for offline review but still leaves the classic silo outside workspace query scope—Blob is not Log Analytics. Redis is a cache, not an APM or telemetry platform, so tagging a cache instance as an Insights substitute provides neither request/dependency tracking nor Log Analytics participation.

Exam caveat: Microsoft has moved the default create experience to workspace-based Insights; classic resources still exist in many tenants, but new municipal builds should not choose classic when citywide query join is a requirement.

Operational check: after creating the workspace-based resource, confirm the Application Insights resource shows a linked Log Analytics workspace, send a test request with the SDK or connection string configured, then run a cross-resource Kusto query (or open Logs on the workspace) and verify the willow-brake app’s requests or traces appear beside other city data.