# Check every linked application before requesting an on-demand .NET profile

> Does Profile now capture only the operation or application currently being viewed?

- Canonical URL: https://update.dsesecurity.com/updates/dse-20260909-317-check-every-linked-application-before-requesting-an-on-demand-net-profile/
- Publisher: Detection Systems & Engineering (DSE Security)
- Author: DSE Security Editorial Team
- Published: 2026-09-10T00:26:39+00:00
- Modified: 2026-09-10T01:40:03+00:00
- Last reviewed by DSE: 2026-09-09
- Resource type: Guide
- DSE priority: Information
- Topics: IT
- Reading time: 2 minutes

## What you need to know

Does Profile now capture only the operation or application currently being viewed?

## Potentially affected

Application Insights resources with linked .NET Profiler agents and operators authorized to start an on-demand session.

## DSE recommendation

Inventory the linked applications and agree the collection window with their owners before selecting Profile now.

## Article

## Source facts

Profile now starts capture on all Profiler agents sending data to the selected Application Insights resource, not just a displayed operation. The session normally appears in the list after five to ten minutes. Manually starting it requires at least write access to the Application Insights component. Recent-session details identify the application, machine, capture timestamp and trigger that started the session. [Microsoft Learn](https://learn.microsoft.com/en-us/azure/azure-monitor/profiler/profiler-settings).

## Applicability

Use this scope check before an on-demand .NET profiling request, especially when several applications share one telemetry resource. Confirm which resource the operator is viewing and distinguish permission to inspect telemetry from permission to request this collection.

## DSE recommendation

Inventory the linked applications and agree the collection window with their owners before selecting Profile now. Record the operation under investigation without assuming that its selection narrows the capture population. Choose a period that will contain representative activity for the intended investigation, and avoid repeating the request merely because the results have not yet appeared.

## Verification

After the documented appearance interval, compare the session list with the expected applications and machines. Check capture timestamps and trigger values before selecting a trace for analysis; a nearby session may not be the requested run. Record unexpected participants and missing expected sessions as separate findings. Close the collection step only after the investigator can identify the trace’s application and capture period, rather than using the existence of any new row as proof of success.

## Official references

[Microsoft Learn: .NET Profiler settings](https://learn.microsoft.com/en-us/azure/azure-monitor/profiler/profiler-settings). Source reviewed September 9, 2026.

## Primary reference

- Name: .NET Profiler settings - Azure Monitor | Microsoft Learn
- Authority: Microsoft Learn
- URL: https://learn.microsoft.com/en-us/azure/azure-monitor/profiler/profiler-settings
- Source publication date: Not stated by the source

## Citation and use

Preferred citation: “Check every linked application before requesting an on-demand .NET profile,” DSE Security, https://update.dsesecurity.com/updates/dse-20260909-317-check-every-linked-application-before-requesting-an-on-demand-net-profile/
Publishing principles: https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/
Usage and citation policy: https://update.dsesecurity.com/usage/
Copyright © 2026 Detection Systems & Engineering. All rights reserved.