Two small documentation improvements for the za edition.
-
In Challenge 2's revoke and recover exercise, disabling the customer managed key does not immediately fail blob reads, because Azure Storage caches the key for roughly ten minutes. During that window the read still succeeds, so attendees may conclude the revocation test failed when it is actually working as designed. The recovery direction has the same delay. Worth noting the expected cache window so people wait before drawing a conclusion.
-
Challenge 3's KQL examples that use the bang in operator (!in) break when pasted into an interactive bash shell, because bash treats the bang as history expansion and errors with event not found. Running set +H first, or rephrasing the query to avoid the bang, would save confusion. This bites in Azure Cloud Shell bash, which the walkthroughs recommend.
Two small documentation improvements for the za edition.
In Challenge 2's revoke and recover exercise, disabling the customer managed key does not immediately fail blob reads, because Azure Storage caches the key for roughly ten minutes. During that window the read still succeeds, so attendees may conclude the revocation test failed when it is actually working as designed. The recovery direction has the same delay. Worth noting the expected cache window so people wait before drawing a conclusion.
Challenge 3's KQL examples that use the bang in operator (
!in) break when pasted into an interactive bash shell, because bash treats the bang as history expansion and errors withevent not found. Runningset +Hfirst, or rephrasing the query to avoid the bang, would save confusion. This bites in Azure Cloud Shell bash, which the walkthroughs recommend.