Per the documentation above: "It's recommended that you use URL encoding or Base64 encoding for names and values containing non-ASCII characters."
This seems to work great for the 'value' portion of the HTTP Header pairs, but the 'name' property does not like the '=' character. I get the following error when trying to save any 'Name' values Base64 encoded because of the terminating equals sign.
"Header name must be a valid HTTP Token."
⚠Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
@TracyGH Thank you for the valuable feedback,we are investigating the issue.
@TracyGH - Thanks so much for your feedback. I've updated the doc to clarify that metadata names should be ASCII characters only and should not be Base64-encoded. They should follow HTTP header naming guidelines.
@tamram - Thank-you for the update! I'm still somewhat puzzled tho, and maybe that's because I'm not understanding the HTTP Header specs correctly. Based on the specs, it appears that a hyphen ('-') would be a legal HTTP Header field name character, but I get the following error when trying to use a hyphen in the the metadata property name of an Azure blob. I receive the same error when trying a number of other characters which should be legal (assuming I'm reading the specs correctly).
In researching a bit more, it looks like there are cases where the specific web server (Apache, NGINX, IIS, etc.) may impose their own character limitations.
Should I open a new issue for this?

@TracyGH - Metadata names must also be valid C# identifiers, so no hyphens are permitted. I'll note that in the doc as well. Thanks!