Check where a saved Log Analytics query lives before claiming customer-key protection
Distinguish query packs from the linked-storage route for customer-managed encryption.
Read the guideDSE security knowledge hubIT
IT
Knowledge
Page 13 of the DSE IT knowledge center, with source-backed guidance and practical next steps.
DSE-authoredOfficial sourcesReviewed guidance
Search the library Explore this topic
Start with the cornerstone guide IT knowledge center
Production-minded guidance for endpoints, servers, updates, cloud services, administration, and supportable operations.
DSE post stream
1,297 articlesIT
Guard workbook queries when an optional Log Analytics table is absent
Design workbook visibility around the tables available in each target workspace.
Read the guide
Enable ARM debug detail separately for nested deployments
A parent deployment's debug setting does not automatically populate nested request details.
Read the guide
Publish a Machine Configuration package with matching URI and content hash
Keep policy metadata aligned with the exact package artifact.
Read the guide
Guard short input before calling substring in an Azure Policy rule
Separate a deliberate policy result from a template-function error.
Read the guide
Timestamp planned-maintenance CSV exports before using them as an Azure change inventory
Treat an exported impacted-resource list as a snapshot of the export time.
Read the guide
Route blob immutability changes outside Storage Explorer’s access-policy editor
DSE recommends identifying the requested policy type before choosing the tool or approving the change.
Read the guide
Bound Table Storage retry concurrency before increasing request volume
DSE recommends capturing request rate, concurrent work, error categories, and retry behavior from the same representative workload period.
Read the guide
Preserve existing ASR exclusions when adding a PowerShell exception
Which PowerShell operation changes one ASR exclusion without replacing the complete existing list?
Read the guide
Preserve source-event identifiers in aggregated Defender detection queries
How should an aggregated custom detection query retain the event context needed for its alert?
Read the guide