{
    "api_version": "1",
    "kind": "dse_post",
    "self": "https://update.dsesecurity.com/api/v1/posts/dse-20260909-123-treat-profiler-byos-as-a-destination-change-not-a-historical-artifact-migration/",
    "item": {
        "id": "https://update.dsesecurity.com/updates/dse-20260909-123-treat-profiler-byos-as-a-destination-change-not-a-historical-artifact-migration/",
        "slug": "dse-20260909-123-treat-profiler-byos-as-a-destination-change-not-a-historical-artifact-migration",
        "url": "https://update.dsesecurity.com/updates/dse-20260909-123-treat-profiler-byos-as-a-destination-change-not-a-historical-artifact-migration/",
        "alternate_urls": {
            "markdown": "https://update.dsesecurity.com/updates/dse-20260909-123-treat-profiler-byos-as-a-destination-change-not-a-historical-artifact-migration.md",
            "json": "https://update.dsesecurity.com/api/v1/posts/dse-20260909-123-treat-profiler-byos-as-a-destination-change-not-a-historical-artifact-migration/"
        },
        "title": "Treat Profiler BYOS as a destination change, not a historical artifact migration",
        "summary": "Will enabling Bring Your Own Storage move existing Profiler or Snapshot Debugger artifacts?",
        "format": {
            "slug": "guide",
            "name": "Guide"
        },
        "priority": {
            "slug": "info",
            "name": "Information"
        },
        "featured": false,
        "image": {
            "theme": "cyber-defense",
            "label": "Cyber defense",
            "alt": "Layered glass and metal cyber-defense structure with controlled blue and gold signal paths.",
            "card_url": "https://update.dsesecurity.com/assets/editorial/cyber-defense-card.webp?v=1.8.20",
            "hero_url": "https://update.dsesecurity.com/assets/editorial/cyber-defense-hero.webp?v=1.8.20",
            "social_url": "https://update.dsesecurity.com/assets/editorial/cyber-defense-social-v2.jpg?v=1.8.20",
            "width": 2400,
            "height": 1350
        },
        "topics": [
            {
                "slug": "cybersecurity",
                "name": "Cybersecurity",
                "url": "https://update.dsesecurity.com/topic/cybersecurity/"
            },
            {
                "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:29:53+00:00",
        "modified_at": "2026-09-10T00:52:38+00:00",
        "reviewed_on": "2026-09-09",
        "reading_minutes": 2,
        "word_count": 267,
        "potentially_affected": "Application Insights Profiler for .NET and Snapshot Debugger deployments changing artifact storage.",
        "dse_recommendation": "Define the artifact cutover and old-data handling separately before linking the new storage account.",
        "primary_source": {
            "name": "BYOS for Profiler and Debugger - Azure Monitor | Microsoft Learn",
            "url": "https://learn.microsoft.com/en-us/azure/azure-monitor/profiler/profiler-bring-your-own-storage",
            "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": "<h2>Source facts</h2>\n<p>Bring Your Own Storage for Application Insights Profiler and Snapshot Debugger stores newly collected artifacts in the customer&#8217;s account; enabling it does not move existing artifacts. Switching back is possible, but Microsoft does not currently support migrating BYOS data into Diagnostic Services storage. BYOS is required with Application Insights Private Link or customer-managed keys and does not cover Code Optimizations trace storage. The account must share the Application Insights location; Private Link use also requires allowing Trusted Microsoft Services. <a href=\"https://learn.microsoft.com/en-us/azure/azure-monitor/profiler/profiler-bring-your-own-storage\" target=\"_blank\" rel=\"noopener noreferrer\">Microsoft Learn</a>.</p>\n<h2>Applicability</h2>\n<p>Inventory the diagnostic tools, existing artifact destination, new account and intended cutover time. Check the documented Diagnostic Services permissions and linked-storage configuration. Separate artifact storage from ordinary Application Insights telemetry tables and from an assumption that all historical diagnostic material will follow a new link.</p>\n<h2>DSE recommendation</h2>\n<p>Define the artifact cutover and old-data handling separately before linking the new storage account. Have the application and storage owners agree where responders will look for artifacts collected before and after the change. Review access, retention and recovery responsibilities for both locations. If reverting later, retain an explicit plan for BYOS artifacts rather than promising an automatic move back into managed storage.</p>\n<h2>Verification</h2>\n<p>After an authorized change, collect a controlled diagnostic artifact and confirm that its new storage location matches the design. Check that authorized investigators can retrieve and analyze it. Verify the old-artifact access plan independently and record the actual cutover evidence. Do not retire the previous evidence path solely because the new linked-storage resource reports successful deployment.</p>\n<h2>Official references</h2>\n<p><a href=\"https://learn.microsoft.com/en-us/azure/azure-monitor/profiler/profiler-bring-your-own-storage\" target=\"_blank\" rel=\"noopener noreferrer\">Microsoft Learn: Configure Bring Your Own Storage for Profiler and Snapshot Debugger</a>. Source reviewed September 9, 2026.</p>",
        "content_text": "Source facts\nBring Your Own Storage for Application Insights Profiler and Snapshot Debugger stores newly collected artifacts in the customer’s account; enabling it does not move existing artifacts. Switching back is possible, but Microsoft does not currently support migrating BYOS data into Diagnostic Services storage. BYOS is required with Application Insights Private Link or customer-managed keys and does not cover Code Optimizations trace storage. The account must share the Application Insights location; Private Link use also requires allowing Trusted Microsoft Services. Microsoft Learn.\nApplicability\nInventory the diagnostic tools, existing artifact destination, new account and intended cutover time. Check the documented Diagnostic Services permissions and linked-storage configuration. Separate artifact storage from ordinary Application Insights telemetry tables and from an assumption that all historical diagnostic material will follow a new link.\nDSE recommendation\nDefine the artifact cutover and old-data handling separately before linking the new storage account. Have the application and storage owners agree where responders will look for artifacts collected before and after the change. Review access, retention and recovery responsibilities for both locations. If reverting later, retain an explicit plan for BYOS artifacts rather than promising an automatic move back into managed storage.\nVerification\nAfter an authorized change, collect a controlled diagnostic artifact and confirm that its new storage location matches the design. Check that authorized investigators can retrieve and analyze it. Verify the old-artifact access plan independently and record the actual cutover evidence. Do not retire the previous evidence path solely because the new linked-storage resource reports successful deployment.\nOfficial references\nMicrosoft Learn: Configure Bring Your Own Storage for Profiler and Snapshot Debugger. Source reviewed September 9, 2026.",
        "content_markdown": "## Source facts\n\nBring Your Own Storage for Application Insights Profiler and Snapshot Debugger stores newly collected artifacts in the customer’s account; enabling it does not move existing artifacts. Switching back is possible, but Microsoft does not currently support migrating BYOS data into Diagnostic Services storage. BYOS is required with Application Insights Private Link or customer-managed keys and does not cover Code Optimizations trace storage. The account must share the Application Insights location; Private Link use also requires allowing Trusted Microsoft Services. [Microsoft Learn](https://learn.microsoft.com/en-us/azure/azure-monitor/profiler/profiler-bring-your-own-storage).\n\n## Applicability\n\nInventory the diagnostic tools, existing artifact destination, new account and intended cutover time. Check the documented Diagnostic Services permissions and linked-storage configuration. Separate artifact storage from ordinary Application Insights telemetry tables and from an assumption that all historical diagnostic material will follow a new link.\n\n## DSE recommendation\n\nDefine the artifact cutover and old-data handling separately before linking the new storage account. Have the application and storage owners agree where responders will look for artifacts collected before and after the change. Review access, retention and recovery responsibilities for both locations. If reverting later, retain an explicit plan for BYOS artifacts rather than promising an automatic move back into managed storage.\n\n## Verification\n\nAfter an authorized change, collect a controlled diagnostic artifact and confirm that its new storage location matches the design. Check that authorized investigators can retrieve and analyze it. Verify the old-artifact access plan independently and record the actual cutover evidence. Do not retire the previous evidence path solely because the new linked-storage resource reports successful deployment.\n\n## Official references\n\n[Microsoft Learn: Configure Bring Your Own Storage for Profiler and Snapshot Debugger](https://learn.microsoft.com/en-us/azure/azure-monitor/profiler/profiler-bring-your-own-storage). 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-123-treat-profiler-byos-as-a-destination-change-not-a-historical-artifact-migration/",
                "url": "https://update.dsesecurity.com/updates/dse-20260909-123-treat-profiler-byos-as-a-destination-change-not-a-historical-artifact-migration/",
                "isPartOf": {
                    "@id": "https://update.dsesecurity.com/#website"
                },
                "lastReviewed": "2026-09-09"
            },
            {
                "@type": "BreadcrumbList",
                "@id": "https://update.dsesecurity.com/updates/dse-20260909-123-treat-profiler-byos-as-a-destination-change-not-a-historical-artifact-migration/#breadcrumbs",
                "itemListElement": [
                    {
                        "@type": "ListItem",
                        "position": 1,
                        "name": "DSE Updates",
                        "item": "https://update.dsesecurity.com/"
                    },
                    {
                        "@type": "ListItem",
                        "position": 2,
                        "name": "Treat Profiler BYOS as a destination change, not a historical artifact migration",
                        "item": "https://update.dsesecurity.com/updates/dse-20260909-123-treat-profiler-byos-as-a-destination-change-not-a-historical-artifact-migration/"
                    }
                ]
            },
            {
                "@type": [
                    "Article",
                    "TechArticle"
                ],
                "@id": "https://update.dsesecurity.com/updates/dse-20260909-123-treat-profiler-byos-as-a-destination-change-not-a-historical-artifact-migration/#article",
                "identifier": "https://update.dsesecurity.com/updates/dse-20260909-123-treat-profiler-byos-as-a-destination-change-not-a-historical-artifact-migration/",
                "url": "https://update.dsesecurity.com/updates/dse-20260909-123-treat-profiler-byos-as-a-destination-change-not-a-historical-artifact-migration/",
                "headline": "Treat Profiler BYOS as a destination change, not a historical artifact migration",
                "description": "Will enabling Bring Your Own Storage move existing Profiler or Snapshot Debugger artifacts?",
                "abstract": "Will enabling Bring Your Own Storage move existing Profiler or Snapshot Debugger artifacts?",
                "articleBody": "Source facts\nBring Your Own Storage for Application Insights Profiler and Snapshot Debugger stores newly collected artifacts in the customer’s account; enabling it does not move existing artifacts. Switching back is possible, but Microsoft does not currently support migrating BYOS data into Diagnostic Services storage. BYOS is required with Application Insights Private Link or customer-managed keys and does not cover Code Optimizations trace storage. The account must share the Application Insights location; Private Link use also requires allowing Trusted Microsoft Services. Microsoft Learn.\nApplicability\nInventory the diagnostic tools, existing artifact destination, new account and intended cutover time. Check the documented Diagnostic Services permissions and linked-storage configuration. Separate artifact storage from ordinary Application Insights telemetry tables and from an assumption that all historical diagnostic material will follow a new link.\nDSE recommendation\nDefine the artifact cutover and old-data handling separately before linking the new storage account. Have the application and storage owners agree where responders will look for artifacts collected before and after the change. Review access, retention and recovery responsibilities for both locations. If reverting later, retain an explicit plan for BYOS artifacts rather than promising an automatic move back into managed storage.\nVerification\nAfter an authorized change, collect a controlled diagnostic artifact and confirm that its new storage location matches the design. Check that authorized investigators can retrieve and analyze it. Verify the old-artifact access plan independently and record the actual cutover evidence. Do not retire the previous evidence path solely because the new linked-storage resource reports successful deployment.\nOfficial references\nMicrosoft Learn: Configure Bring Your Own Storage for Profiler and Snapshot Debugger. Source reviewed September 9, 2026.",
                "datePublished": "2026-09-10T00:29:53+00:00",
                "dateModified": "2026-09-10T00:52:38+00:00",
                "mainEntityOfPage": {
                    "@id": "https://update.dsesecurity.com/updates/dse-20260909-123-treat-profiler-byos-as-a-destination-change-not-a-historical-artifact-migration/"
                },
                "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-123-treat-profiler-byos-as-a-destination-change-not-a-historical-artifact-migration/#primaryimage",
                    "url": "https://update.dsesecurity.com/assets/editorial/cyber-defense-social-v2.jpg?v=1.8.20",
                    "contentUrl": "https://update.dsesecurity.com/assets/editorial/cyber-defense-social-v2.jpg?v=1.8.20",
                    "width": 1200,
                    "height": 630,
                    "caption": "Treat Profiler BYOS as a destination change, not a historical artifact migration"
                },
                "articleSection": [
                    "Cybersecurity",
                    "IT"
                ],
                "keywords": [
                    "Cybersecurity",
                    "IT",
                    "Guide",
                    "Information priority"
                ],
                "genre": "Guide",
                "about": [
                    {
                        "@type": "Thing",
                        "name": "Cybersecurity",
                        "url": "https://update.dsesecurity.com/topic/cybersecurity/"
                    },
                    {
                        "@type": "Thing",
                        "name": "IT",
                        "url": "https://update.dsesecurity.com/topic/it/"
                    }
                ],
                "wordCount": 267,
                "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": "BYOS for Profiler and Debugger - Azure Monitor | Microsoft Learn",
                    "url": "https://learn.microsoft.com/en-us/azure/azure-monitor/profiler/profiler-bring-your-own-storage"
                }
            }
        ]
    }
}