Set File Metadata
Set File Metadata operation sets user-defined metadata for the specified file.
|Enabled file share protocol||Available|
You can construct the
Set File Metadata request as follows. We recommend that you use HTTPS.
|Method||Request URI||HTTP version|
Replace the path components that are shown in the request URI with your own, as follows:
||The name of your storage account.|
||The name of your file share.|
||Optional. The path to the parent directory.|
||The name of the file.|
For information about path naming restrictions, see Name and reference shares, directories, files, and metadata.
You can specify the following additional parameters in the request URI:
||Optional. The timeout parameter is expressed in seconds. For more information, see Set time-outs for File service operations.|
||Required. Specifies the authorization scheme, account name, and signature. For more information, see Authorize requests to Azure Storage.|
||Required. Specifies the Coordinated Universal Time (UTC) for the request. For more information, see Authorize requests to Azure Storage.|
||Required for all authorized requests. Specifies the version of the operation to use for this request. For more information, see Versioning for the Azure Storage services.|
||Optional. Sets a name-value pair for the file.
Each call to this operation replaces all existing metadata attached to the file. To remove all metadata from the file, call this operation with no metadata headers.
Metadata names must adhere to the naming rules for C# identifiers.
||Required if the file has an active lease. Available for version 2019-02-02 and later.|
||Optional. Provides a client-generated, opaque value with a 1-kibibyte (KiB) character limit that's recorded in the logs when logging is configured. We highly recommend that you use this header to correlate client-side activities with requests that the server receives. For more information, see Monitor Azure Files.|
||Optional. Version 2022-11-02 and later. The Boolean value specifies if a trailing dot present in request url should be trimmed or not. For more information, see Naming and referencing shares, directories, files, and metadata.|
The response includes an HTTP status code and a set of response headers.
A successful operation returns status code 200 (OK).
For information about status codes, see Status and error codes.
The response for this operation includes the following headers. The response may also include additional standard HTTP headers. All standard headers conform to the HTTP/1.1 protocol specification.
||Contains a value that represents the version of the file. The value is enclosed in quotation marks.|
||Uniquely identifies the request that was made, and it can be used to troubleshoot the request. For more information, see Troubleshoot API operations.|
||Indicates the version of the File service that was used to execute the request.|
||A UTC date/time value that's generated by the service, which indicates the time when the response was initiated.|
||Version 2017-04-17 and later. The value of this header is set to
||Can be used to troubleshoot requests and corresponding responses. The value of this header is equal to the value of the
Only the account owner may call this operation.
Set File Metadata isn't supported on a share snapshot, which is a read-only copy of a share. An attempt to perform this operation on a share snapshot fails with 400 (InvalidQueryParameterValue)
If the file has an active lease, the client must specify a valid lease ID on the request in order to write metadata to the file. If the client doesn't specify a lease ID, or specifies an invalid lease ID, the File service returns status code 412 (Precondition Failed). If the client specifies a lease ID but the file doesn't have an active lease, the File service also returns status code 412 (Precondition Failed).