Keep the prior Recovery Services encryption key available through rotation
When can the previous key version be retired after Recovery Services vault key autorotation?
Read the guideDSE security knowledge hubNetworks & Infrastructure
Networks & Infrastructure
Knowledge
Page 60 of the DSE Networks & Infrastructure 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 Networks & Infrastructure knowledge center
Guidance for resilient networks, Wi-Fi, firewalls, cabling, power, exposure reduction, and connected-device planning.
DSE post stream
1,594 articlesNetworks & Infrastructure
Generate confidential-container enforcement policy through the supported tooling
Can a handwritten enforcement policy substitute for generated policy on confidential Azure Container Instances?
Read the guide
Treat a custom DDoS threshold as a replacement for that protocol's autotuning
Does a preview Azure DDoS custom threshold supplement or replace adaptive tuning?
Read the guide
Do not assume every Service Fabric node retains the same old certificates
Certificate rotation through the Key Vault VM extension can leave different certificate histories on existing and newly added nodes.
Read the guide
Fix the Site Recovery appliance's address choice before registration
Which appliance identity and installation choices should be settled before configuring modernized VMware or physical-server recovery?
Read the guide
Do not use blob tag search as a complete inventory of previous versions
Tags can remain attached to an older blob version without being available to the blob index query engine.
Read the guide
Treat secondary-region storage reads as potentially inconsistent across related updates
A successful read from a geo-redundant secondary can combine changes that have not yet arrived in their original order.
Read the guide
Read SDK retry counts as attempts, not an inventory of lost telemetry
How should Application Insights SDK stats distinguish retries, drops and successful delivery?
Read the explainer
Inspect the provider error before treating every Azure HTTP 429 as quota exhaustion
A provider can return 429 for a temporary resource condition, including a conflicting operation, rather than a request limit caused by your client.
Read the guide
Verify the Gateway Load Balancer service chain before claiming inline inspection
Does enabling Azure DDoS Protection alone demonstrate that traffic traverses a partner L7 appliance?
Read the guide