Microsoft’s Shared Key REST example requires Authorization, x-ms-date, and x-ms-version headers for its List Containers request. The date header carries UTC request time, while the version header identifies the REST API version. The optional x-ms-client-request-id value can be recorded in storage analytics logs when logging is enabled. Microsoft Learn
\nUse this checklist when maintaining a custom Azure Storage REST client based on the documented Shared Key List Containers example, rather than relying on a storage SDK.
\nDSE recommends capturing a sanitized request description that includes the method, target account, operation, API version, and request time before investigating an authorization failure. Verify the required headers against the operation being called. Use a nonsecret correlation value where useful, and keep account keys and authorization material out of the troubleshooting record. Review the request over the approved secure transport and compare one controlled call with the documented operation.
\nInspect the response status and retain the sanitized request details with the observation time. Where the expected analytics logging is enabled, look for the chosen correlation value and confirm it relates to the same request. Record missing evidence or a remaining authorization failure explicitly; do not infer that correct headers alone establish a valid signature or successful operation.
\n