GuideInformationCybersecurityIT

Treat Profiler BYOS as a destination change, not a historical artifact migration

Will enabling Bring Your Own Storage move existing Profiler or Snapshot Debugger artifacts?

Layered glass and metal cyber-defense structure with controlled blue and gold signal paths.
DSE visual intelligenceCyber defenseGuide · 2 min read
Executive summary

What you need to know

Will enabling Bring Your Own Storage move existing Profiler or Snapshot Debugger artifacts?

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.

Source facts

Bring 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.

Applicability

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.

DSE recommendation

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.

Verification

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.

Official references

Microsoft Learn: Configure Bring Your Own Storage for Profiler and Snapshot Debugger. Source reviewed September 9, 2026.

Primary reference

Review the official source

BYOS for Profiler and Debugger - Azure Monitor | Microsoft Learn · Verified September 9, 2026

Open official reference ↗
Plan the next step

Need help applying this guidance safely?

DSE can help confirm applicability, protect service continuity, and validate the result across physical security and IT systems.

Talk with DSE