{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/dse-20260909-317-check-every-linked-application-before-requesting-an-on-demand-net-profile/", "item": { "id": "https://update.dsesecurity.com/updates/dse-20260909-317-check-every-linked-application-before-requesting-an-on-demand-net-profile/", "slug": "dse-20260909-317-check-every-linked-application-before-requesting-an-on-demand-net-profile", "url": "https://update.dsesecurity.com/updates/dse-20260909-317-check-every-linked-application-before-requesting-an-on-demand-net-profile/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/dse-20260909-317-check-every-linked-application-before-requesting-an-on-demand-net-profile.md", "json": "https://update.dsesecurity.com/api/v1/posts/dse-20260909-317-check-every-linked-application-before-requesting-an-on-demand-net-profile/" }, "title": "Check every linked application before requesting an on-demand .NET profile", "summary": "Does Profile now capture only the operation or application currently being viewed?", "format": { "slug": "guide", "name": "Guide" }, "priority": { "slug": "info", "name": "Information" }, "featured": false, "image": { "theme": "managed-it", "label": "Managed IT operations", "alt": "A controlled technology lifecycle progressing from assessment to approved production.", "card_url": "https://update.dsesecurity.com/assets/editorial/managed-it-card.webp?v=1.8.20", "hero_url": "https://update.dsesecurity.com/assets/editorial/managed-it-hero.webp?v=1.8.20", "social_url": "https://update.dsesecurity.com/assets/editorial/managed-it-social-v2.jpg?v=1.8.20", "width": 2400, "height": 1350 }, "topics": [ { "slug": "it", "name": "IT", "url": "https://update.dsesecurity.com/topic/it/" } ], "author": { "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/#editorial-team", "type": "Organization" }, "publisher": { "name": "Detection Systems & Engineering", "url": "https://dsesecurity.com/" }, "published_at": "2026-09-10T00:26:39+00:00", "modified_at": "2026-09-10T01:40:03+00:00", "reviewed_on": "2026-09-09", "reading_minutes": 2, "word_count": 245, "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.", "primary_source": { "name": ".NET Profiler settings - Azure Monitor | Microsoft Learn", "url": "https://learn.microsoft.com/en-us/azure/azure-monitor/profiler/profiler-settings", "published_on": null, "authority": "Microsoft Learn" }, "publishing_principles": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/", "usage_info": "https://update.dsesecurity.com/usage/", "copyright_notice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.", "content_html": "

Source facts

\n

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.

\n

Applicability

\n

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.

\n

DSE recommendation

\n

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.

\n

Verification

\n

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.

\n

Official references

\n

Microsoft Learn: .NET Profiler settings. Source reviewed September 9, 2026.

", "content_text": "Source facts\nProfile 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.\nApplicability\nUse 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.\nDSE recommendation\nInventory 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.\nVerification\nAfter 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.\nOfficial references\nMicrosoft Learn: .NET Profiler settings. Source reviewed September 9, 2026.", "content_markdown": "## Source facts\n\nProfile 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).\n\n## Applicability\n\nUse 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.\n\n## DSE recommendation\n\nInventory 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.\n\n## Verification\n\nAfter 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.\n\n## Official references\n\n[Microsoft Learn: .NET Profiler settings](https://learn.microsoft.com/en-us/azure/azure-monitor/profiler/profiler-settings). Source reviewed September 9, 2026." }, "json_ld": { "@context": "https://schema.org", "@graph": [ { "@type": "Organization", "@id": "https://dsesecurity.com/#organization", "name": "Detection Systems & Engineering", "alternateName": "DSE Security", "url": "https://dsesecurity.com/", "logo": { "@type": "ImageObject", "url": "https://update.dsesecurity.com/assets/dse-logo-20260812.png?v=1.8.20" } }, { "@type": "Organization", "@id": "https://update.dsesecurity.com/#editorial-team", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/", "parentOrganization": { "@id": "https://dsesecurity.com/#organization" } }, { "@type": "WebSite", "@id": "https://update.dsesecurity.com/#website", "name": "DSE Updates", "alternateName": "DSE Security Knowledge Hub", "url": "https://update.dsesecurity.com/", "inLanguage": "en-US", "publisher": { "@id": "https://dsesecurity.com/#organization" }, "potentialAction": { "@type": "SearchAction", "target": { "@type": "EntryPoint", "urlTemplate": "https://update.dsesecurity.com/?q={search_term_string}" }, "query-input": "required name=search_term_string" } }, { "@type": "WebPage", "@id": "https://update.dsesecurity.com/updates/dse-20260909-317-check-every-linked-application-before-requesting-an-on-demand-net-profile/", "url": "https://update.dsesecurity.com/updates/dse-20260909-317-check-every-linked-application-before-requesting-an-on-demand-net-profile/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-09-09" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/dse-20260909-317-check-every-linked-application-before-requesting-an-on-demand-net-profile/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Check every linked application before requesting an on-demand .NET profile", "item": "https://update.dsesecurity.com/updates/dse-20260909-317-check-every-linked-application-before-requesting-an-on-demand-net-profile/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/dse-20260909-317-check-every-linked-application-before-requesting-an-on-demand-net-profile/#article", "identifier": "https://update.dsesecurity.com/updates/dse-20260909-317-check-every-linked-application-before-requesting-an-on-demand-net-profile/", "url": "https://update.dsesecurity.com/updates/dse-20260909-317-check-every-linked-application-before-requesting-an-on-demand-net-profile/", "headline": "Check every linked application before requesting an on-demand .NET profile", "description": "Does Profile now capture only the operation or application currently being viewed?", "abstract": "Does Profile now capture only the operation or application currently being viewed?", "articleBody": "Source facts\nProfile 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.\nApplicability\nUse 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.\nDSE recommendation\nInventory 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.\nVerification\nAfter 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.\nOfficial references\nMicrosoft Learn: .NET Profiler settings. Source reviewed September 9, 2026.", "datePublished": "2026-09-10T00:26:39+00:00", "dateModified": "2026-09-10T01:40:03+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/dse-20260909-317-check-every-linked-application-before-requesting-an-on-demand-net-profile/" }, "inLanguage": "en-US", "isAccessibleForFree": true, "author": { "@type": "Organization", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/#editorial-team" }, "publisher": { "@id": "https://dsesecurity.com/#organization" }, "image": { "@type": "ImageObject", "@id": "https://update.dsesecurity.com/updates/dse-20260909-317-check-every-linked-application-before-requesting-an-on-demand-net-profile/#primaryimage", "url": "https://update.dsesecurity.com/assets/editorial/managed-it-social-v2.jpg?v=1.8.20", "contentUrl": "https://update.dsesecurity.com/assets/editorial/managed-it-social-v2.jpg?v=1.8.20", "width": 1200, "height": 630, "caption": "Check every linked application before requesting an on-demand .NET profile" }, "articleSection": [ "IT" ], "keywords": [ "IT", "Guide", "Information priority" ], "genre": "Guide", "about": [ { "@type": "Thing", "name": "IT", "url": "https://update.dsesecurity.com/topic/it/" } ], "wordCount": 245, "timeRequired": "PT2M", "publishingPrinciples": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/", "usageInfo": "https://update.dsesecurity.com/usage/", "copyrightHolder": { "@id": "https://dsesecurity.com/#organization" }, "copyrightNotice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.", "citation": { "@type": "CreativeWork", "name": ".NET Profiler settings - Azure Monitor | Microsoft Learn", "url": "https://learn.microsoft.com/en-us/azure/azure-monitor/profiler/profiler-settings" } } ] } }