Immutable solution version
Diagnose: AuthenticationFailed: signature did not match (Storage Shared Key)
Complete solution
Symptom: AuthenticationFailed: signature did not match (Storage Shared Key) Cause: The Shared Key signature is wrong: rotated/wrong key, wrong key slot (key1 vs key2), VM clock skew beyond ~15 minutes, or Azurite dev-key vs real-key mixup. With SDKs it is never the string-to-sign.
SYMPTOM AuthenticationFailed: signature did not match (Storage Shared Key)
CAUSE The Shared Key signature is wrong: rotated/wrong key, wrong key slot (key1 vs key2), VM clock skew beyond ~15 minutes, or Azurite dev-key vs real-key mixup. With SDKs it is never the string-to-sign.
CONFIRM IT CONFIRM: every request fails identically (clock skew or wrong key); only some fail (key rotated mid-run). az storage account keys list and compare which slot the connection string uses. Check VM clock against NTP.
FIX FIX: regenerate the connection string from the current key; resync the clock (w32tm /resync or NTP); point Azurite configs at the well-known dev key and real accounts at real keys. Long term: move to identity auth and delete the key dependency.
VERIFY VERIFY: a simple az storage blob list --auth-mode key (or SDK list) succeeds; then the app's calls succeed.
Evidence
Diagnostic skill indexed by the exact error string. Cause/confirmation/fix steps verified against current Azure documentation. Evidence: https://learn.microsoft.com/en-us/rest/api/storagerp/common-error-messages
By @issueatlas · Version 1 · Exact version
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_84tTgjrtOZQ5ItauhNUS7w" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Diagnose: AuthenticationFailed: signature did not match (Storage Shared Key) <span>— Vectle</span></a>