{
	"id": "daab30a8-e059-4118-a926-ed1b92ed1fbd",
	"created_at": "2026-04-06T01:29:30.734747Z",
	"updated_at": "2026-04-10T03:20:47.14424Z",
	"deleted_at": null,
	"sha1_hash": "15e7c61518bfc8569da4cbc7e287b87faffdd70c",
	"title": "List Blobs (REST API) - Azure Storage",
	"llm_title": "",
	"authors": "",
	"file_creation_date": "0001-01-01T00:00:00Z",
	"file_modification_date": "0001-01-01T00:00:00Z",
	"file_size": 214320,
	"plain_text": "List Blobs (REST API) - Azure Storage\r\nBy seanmcc-msft\r\nArchived: 2026-04-06 00:40:44 UTC\r\nThe List Blobs operation returns a list of the blobs under the specified container.\r\nYou can construct the List Blobs request as follows. HTTPS is recommended. Replace myaccount with the name of\r\nyour storage account.\r\nMethod Request URI\r\nHTTP\r\nversion\r\nGET\r\nhttps://myaccount.blob.core.windows.net/mycontainer?\r\nrestype=container\u0026comp=list\r\nHTTP/1.1\r\nWhen you make a request against the emulated storage service, specify the emulator hostname and Azure Blob Storage\r\nport as 127.0.0.1:10000 , followed by the emulated storage account name.\r\nMethod Request URI\r\nHTTP\r\nversion\r\nGET\r\nhttp://127.0.0.1:10000/devstoreaccount1/mycontainer?\r\nrestype=container\u0026comp=list\r\nHTTP/1.1\r\nFor more information, see Use Azurite emulator for local Azure Storage development.\r\nYou can specify the following additional parameters on the URI.\r\nParameter Description\r\nprefix\r\nOptional. Filters the results to return only\r\nblobs with names that begin with the\r\nspecified prefix. In accounts that have a\r\nhierarchical namespace, an error will occur\r\nin cases where the name of a file appears in\r\nthe middle of the prefix path. For example,\r\nyou might attempt to find blobs that are\r\nnamed readmefile.txt by using the\r\nprefix path\r\nfolder1/folder2/readme/readmefile.txt .\r\nAn error will appear if any subfolder\r\ncontains a file named readme .\r\nhttps://docs.microsoft.com/en-us/rest/api/storageservices/list-blobs\r\nPage 1 of 16\n\nParameter Description\r\ndelimiter\r\nOptional. When the request includes this\r\nparameter, the operation returns a\r\nBlobPrefix element in the response body.\r\nThis element acts as a placeholder for all\r\nblobs with names that begin with the same\r\nsubstring, up to the appearance of the\r\ndelimiter character. The delimiter can be a\r\nsingle character or a string.\r\nmarker\r\nOptional. A string value that identifies the\r\nportion of the list to be returned with the\r\nnext list operation. The operation returns a\r\nmarker value within the response body if\r\nthe list returned was not complete. You can\r\nthen use the marker value in a subsequent\r\ncall to request the next set of list items.\r\nThe marker value is opaque to the client.\r\nmaxresults\r\nOptional. Specifies the maximum number\r\nof blobs to return, including all\r\nBlobPrefix elements. If the request\r\ndoesn't specify maxresults , or specifies a\r\nvalue greater than 5,000, the server will\r\nreturn up to 5,000 items. If there are\r\nadditional results to return, the service\r\nreturns a continuation token in the\r\nNextMarker response element. In certain\r\ncases, the service might return fewer results\r\nthan specified by maxresults , and also\r\nreturn a continuation token.\r\nSetting maxresults to a value less than or\r\nequal to zero results in error response code\r\n400 (Bad Request).\r\ninclude=\r\n{snapshots,metadata,uncommittedblobs,copy,deleted,tags,versions,\r\ndeletedwithversions,immutabilitypolicy,legalhold,permissions}\r\nOptional. Specifies one or more datasets to\r\ninclude in the response:\r\n- snapshots : Specifies that snapshots\r\nshould be included in the enumeration.\r\nSnapshots are listed from oldest to newest\r\nin the response.\r\n- metadata : Specifies that blob metadata\r\nhttps://docs.microsoft.com/en-us/rest/api/storageservices/list-blobs\r\nPage 2 of 16\n\nParameter Description\r\nbe returned in the response.\r\n- uncommittedblobs : Specifies that blobs\r\nfor which blocks have been uploaded, but\r\nwhich haven't been committed by using Put\r\nBlock List, be included in the response.\r\n- copy : Version 2012-02-12 and later.\r\nSpecifies that metadata related to any\r\ncurrent or previous Copy Blob operation\r\nshould be included in the response.\r\n- deleted : Version 2017-07-29 and later.\r\nSpecifies that soft-deleted blobs should be\r\nincluded in the response.\r\n- tags : Version 2019-12-12 and later.\r\nSpecifies that user-defined, blob index tags\r\nshould be included in the response.\r\n- versions : Version 2019-12-12 and later.\r\nSpecifies that versions of blobs should be\r\nincluded in the enumeration.\r\n- deletedwithversions : Version 2020-10-\r\n02 and later. Specifies that deleted blobs\r\nwith any versions (active or deleted) should\r\nbe included in the response. Items that\r\nyou've permanently deleted appear in the\r\nresponse until they are processed by\r\ngarbage collection. Use the tag \\\r\n\u003cHasVersionsOnly\\\u003e , and the value true .\r\n- immutabilitypolicy : Version 2020-06-\r\n12 and later. Specifies that the enumeration\r\nshould include the immutability policy until\r\ndate, and the immutability policy mode of\r\nthe blobs.\r\n- legalhold : Version 2020-06-12 and later.\r\nSpecifies that the enumeration should\r\ninclude the legal hold of blobs.\r\n- permissions : Version 2020-06-12 and\r\nlater. Supported only for accounts with a\r\nhierarchical namespace enabled. If a request\r\nincludes this parameter, then the owner,\r\ngroup, permissions, and access control list\r\nfor the listed blobs or directories will be\r\nincluded in the enumeration.\r\nhttps://docs.microsoft.com/en-us/rest/api/storageservices/list-blobs\r\nPage 3 of 16\n\nParameter Description\r\nTo specify more than one of these options\r\non the URI, you must separate each option\r\nwith a URL-encoded comma (\"%82\").\r\nshowonly={deleted,files,directories}\r\nOptional. Specifies one of these datasets to\r\nbe returned in the response:\r\n- deleted : Optional. Version 2020-08-04\r\nand later. Only for accounts enabled with\r\nhierarchical namespace. When a request\r\nincludes this parameter, the list only\r\ncontains soft-deleted blobs. Note that\r\nPOSIX ACL authorization fallback is not\r\nsupported for listing soft deleted blobs. If\r\ninclude=deleted is also specified, the\r\nrequest fails with Bad Request (400).\r\n- files : Optional. Version 2020-12-06 and\r\nlater. Only for accounts enabled with\r\nhierarchical namespace. When a request\r\nincludes this parameter, the list only\r\ncontains files.\r\n- directories : Optional. Version 2020-12-\r\n06 and later. Only for accounts enabled with\r\nhierarchical namespace. When a request\r\nincludes this parameter, the list only\r\ncontains directories.\r\ntimeout\r\nOptional. The timeout parameter is\r\nexpressed in seconds. For more\r\ninformation, see Setting timeouts for Blob\r\nStorage operations.\r\nstartFrom\r\nOptional. Version 2023-05-03 and newer.\r\nThe startFrom parameter specifies a fully\r\nqualified path within the container, similar\r\nto how the prefix parameter is used to list\r\nblobs starting from a defined location\r\nwithin prefix’s specified range. For\r\nexample, listing under prefix\r\nfolder1/folder2 with startFrom as\r\nfolder1/folder2/folder3/readmefile.txt will\r\nstart listing from\r\nfolder1/folder2/folder3/readmefile.txt.\r\nhttps://docs.microsoft.com/en-us/rest/api/storageservices/list-blobs\r\nPage 4 of 16\n\nThe following table describes required and optional request headers.\r\nRequest header Description\r\nAuthorization\r\nRequired. Specifies the authorization scheme, account name, and signature. For more\r\ninformation, see Authorize requests to Azure Storage.\r\nDate or x-ms-dateRequired. Specifies the Coordinated Universal Time (UTC) for the request. For more\r\ninformation, see Authorize requests to Azure Storage.\r\nx-ms-version\r\nRequired for all authorized requests, and optional for anonymous requests. Specifies the\r\nversion of the operation to use for this request. For more information, see Versioning for the\r\nAzure Storage services.\r\nx-ms-client-request-id\r\nOptional. Provides a client-generated, opaque value with a 1-kibibyte (KiB) character limit\r\nthat's recorded in the logs when logging is configured. We highly recommend that you use this\r\nheader to correlate client-side activities with requests that the server receives. For more\r\ninformation, see Monitor Azure Blob Storage.\r\nx-ms-upn\r\nOptional. Valid only when a hierarchical namespace is enabled for the account, and\r\ninclude=permissions is provided in the request. If true , the user identity values returned in\r\nthe \u003cOwner\u003e, \u003cGroup\u003e, and \u003cAcl\u003e fields are transformed from Microsoft Entra object IDs to\r\nuser principal names. If false , the values are returned as Microsoft Entra object IDs. The\r\ndefault value is false . Note that group and application object IDs aren't translated because\r\nthey don't have unique friendly names.\r\nNone.\r\nSee Enumerating blob resources for a sample request.\r\nThe response includes an HTTP status code, a set of response headers, and a response body in XML format.\r\nA successful operation returns status code 200 (OK). For information about status codes, see Status and error codes.\r\nThe response for this operation includes the following headers. The response can also include additional, standard HTTP\r\nheaders. All standard headers conform to the HTTP/1.1 protocol specification.\r\nResponse\r\nheader\r\nDescription\r\nContent-Type\r\nSpecifies the format in which the results are returned. Currently this value is application/xml .\r\nx-ms-request-idThis header uniquely identifies the request that was made, and can be used for troubleshooting the\r\nrequest. For more information, see Troubleshooting API operations.\r\nx-ms-versionIndicates the version of Blob Storage used to run the request. This header is returned for requests\r\nmade by using version 2009-09-19 and later.\r\nhttps://docs.microsoft.com/en-us/rest/api/storageservices/list-blobs\r\nPage 5 of 16\n\nResponse\r\nheader\r\nDescription\r\nThis header is also returned for anonymous requests, without a version specified, if the container\r\nwas marked for public access by using the 2009-09-19 version of Blob Storage.\r\nDate\r\nA UTC date/time value that indicates the time at which the response was initiated. The service\r\ngenerates this value.\r\nx-ms-client-request-id\r\nYou can use this header to troubleshoot requests and corresponding responses. The value of this\r\nheader is equal to the value of the x-ms-client-request-id header, if it's present in the request.\r\nThe value is at most 1024 visible ASCII characters. If the x-ms-client-request-id header isn't\r\npresent in the request, this header won't be present in the response.\r\nThe format of the XML response is as follows.\r\nNote that the Prefix , Marker , MaxResults , and Delimiter elements are present only if they were specified on the\r\nrequest URI. If NextMarker is empty, then the list results are complete. If the NextMarker is not empty, the list results\r\nmay or may not be complete. If you want to list all blobs, continue to call List Blobs with subsequent marker values\r\nuntil NextMarker is empty.\r\nSnapshots, blob metadata, and uncommitted blobs are included in the response only if they are specified with the\r\ninclude parameter on the request URI.\r\nIn version 2009-09-19 and later, the blob's properties are encapsulated within a Properties element.\r\nBeginning with version 2009-09-19, List Blobs returns the following renamed elements in the response body:\r\nLast-Modified (previously LastModified )\r\nContent-Length (previously Size )\r\nContent-Type (previously ContentType )\r\nContent-Encoding (previously ContentEncoding )\r\nContent-Language (previously ContentLanguage )\r\nThe Content-MD5 element appears for blobs created with version 2009-09-19 and later. In version 2012-02-12 and later,\r\nBlob Storage calculates the Content-MD5 value when you upload a blob by using Put Blob. Blob Storage doesn't\r\ncalculate this when you create a blob by using Put Block List. You can explicitly set the Content-MD5 value when you\r\ncreate the blob, or by calling the Put Block List or Set Blob Properties operations.\r\nFor versions from 2009-09-19 and later, but prior to version 2015-02-21, you can't call List Blobs on a container that\r\nincludes append blobs. The service returns status code 409 (Conflict) if the result of the listing contains an append blob.\r\nLeaseState and LeaseDuration appear only in version 2012-02-12 and later.\r\nCopyId , CopyStatus , CopySource , CopyProgress , CopyCompletionTime , and CopyStatusDescription only\r\nappear in version 2012-02-12 and later, when this operation includes the include={copy} parameter. These elements\r\nhttps://docs.microsoft.com/en-us/rest/api/storageservices/list-blobs\r\nPage 6 of 16\n\ndon't appear if this blob has never been the destination in a Copy Blob operation. The elements don't appear if this blob\r\nhas been modified after a concluded Copy Blob operation, by using Set Blob Properties , Put Blob , or Put Block\r\nList . These elements also don't appear with a blob created by Copy Blob, before version 2012-02-12.\r\nIn version 2013-08-15 and later, the EnumerationResults element contains a ServiceEndpoint attribute that specifies\r\nthe blob endpoint. This element also contains a ContainerName field that specifies the name of the container. In\r\nprevious versions, these two attributes were combined together in the ContainerName field. Also in version 2013-08-15\r\nand later, the Url element under Blob has been removed.\r\nFor version 2015-02-21 and later, List Blobs returns blobs of all types (block, page, and append blobs).\r\nFor version 2015-12-11 and later, List Blobs returns the ServerEncrypted element. This element is set to true if\r\nthe blob and application metadata are completely encrypted, and false otherwise.\r\nFor version 2016-05-31 and later, List Blobs returns the IncrementalCopy element for incremental copy blobs and\r\nsnapshots, with the value set to true .\r\nFor version 2017-04-17 and later, List Blobs returns the AccessTier element if an access tier has been explicitly set.\r\nFor a list of allowed premium page blob tiers, see High-performance premium storage and managed disks for VMs. For\r\nBlob Storage or general-purpose v2 accounts, valid values are Hot , Cool , Cold , Smart , and Archive . If the blob\r\nis in the rehydrate pending state, then ArchiveStatus element is returned with one of the valid values ( rehydrate-pending-to-hot , rehydrate-pending-to-cool , or rehydrate-pending-to-cold ). For detailed information about block\r\nblob tiering see Blob storage tiers.\r\nFor version 2017-04-17 and later, List Blobs returns the AccessTierInferred element on Blob Storage or general-purpose v2 accounts. If the block blob doesn't have the access tier set, tier information is inferred from storage account\r\nproperties, and this value is set to true . This header is present only if the tier is inferred from the account property.\r\nFor version 2017-04-17 and later, List Blobs returns the AccessTierChangeTime element on Blob Storage or general-purpose v2 accounts. This is returned only if the tier on block blob was ever set. For more information, see\r\nRepresentation of date-time values in headers.\r\nFor version 2017-07-29 and later, Deleted , DeletedTime , and RemainingRetentionDays appear when this operation\r\nincludes the include={deleted} parameter. These elements don't appear if this blob wasn't deleted. These elements\r\nappear for blobs or snapshots that are deleted with the DELETE operation, when the soft-delete feature was enabled. The\r\nDeleted element is set to true for blobs and snapshots that are soft-deleted. Deleted-Time corresponds to the time\r\nwhen the blob was deleted. RemainingRetentionDays indicates the number of days after which a soft-deleted blob is\r\npermanently deleted.\r\nFor version 2017-11-09 and later, Creation-Time returns the time at which this blob was created.\r\nFor version 2019-02-02 and later, List Blobs returns the CustomerProvidedKeySha256 element if the blob is\r\nencrypted with a customer-provided key. The value will be set to the SHA-256 hash of the key used to encrypt the blob.\r\nAdditionally, if the operation includes the include={metadata} parameter, and there is application metadata present on\r\na blob encrypted with a customer-provided key, the Metadata element will have an Encrypted=\"true\" attribute. This\r\nattribute indicates that the blob has metadata that can't be decrypted as part of the List Blobs operation. To access the\r\nmetadata for these blobs, call Get Blob Properties or Get Blob Metadata with the customer-provided key.\r\nhttps://docs.microsoft.com/en-us/rest/api/storageservices/list-blobs\r\nPage 7 of 16\n\nFor version 2019-02-02 and later, List Blobs returns the EncryptionScope element if the blob is encrypted with an\r\nencryption scope. The value will be set to the name of the encryption scope used to encrypt the blob. If the operation\r\nincludes the include={metadata} parameter, application metadata on the blob is transparently decrypted, and available\r\nin the Metadata element.\r\nFor version 2019-12-12 and later, List Blobs returns the RehydratePriority element on Blob Storage or general-purpose v2 accounts, if the object is in the rehydrate pending state. Valid values are High and Standard .\r\nFor version 2019-12-12 and later, List Blobs returns the VersionId element for blobs and generated blob versions,\r\nwhen versioning is enabled on the account.\r\nFor version 2019-12-12 and later, List Blobs returns the IsCurrentVersion element for the current version of the\r\nblob. The value is set to true . This element enables you to differentiate the current version from the read-only,\r\nautomatically generated versions.\r\nFor version 2019-12-12 and later, List Blobs returns the TagCount element for blobs with any tags. The Tags\r\nelement appears only when this operation includes the include={tags} parameter. These elements don't appear if there\r\nare no tags on the blob.\r\nFor version 2019-12-12 and later, List Blobs returns the Sealed element for append blobs. The Sealed element\r\nappears only when the append blob has been sealed. These elements don't appear if the append blob isn't sealed.\r\nFor version 2020-02-10 and later, List Blobs returns the LastAccessTime element. The element shows when the\r\nblob's data was last accessed, according to the storage account's last access time tracking policy. The element isn't\r\nreturned if the storage account doesn't have this policy, or the policy is disabled. For information about setting the\r\naccount's last access time tracking policy, see the Blob Service API. The LastAccessTime element doesn't track the last\r\ntime when the blob's metadata is accessed.\r\nFor version 2020-06-12 and later, List Blobs returns the ImmutabilityPolicyUntilDate and\r\nImmutabilityPolicyMode elements, when this operation includes the include={immutabilitypolicy} parameter.\r\nFor version 2020-06-12 and later, List Blobs returns the LegalHold element, when this operation includes the\r\ninclude={legalhold} parameter.\r\nFor version 2020-06-12 and later, for accounts with a hierarchical namespace enabled, List Blobs returns the Owner ,\r\nGroup , Permissions , and Acl elements. The request must contain the include={permissions} parameter. Note that\r\nthe Acl element is a combined list of access and default access control lists that were set on the file or directory.\r\nFor version 2020-06-12 and later, for accounts with a hierarchical namespace enabled, List Blobs with a delimiter\r\nreturns the Properties element in the BlobPrefix element. This corresponds with the properties on the directory.\r\nFor version 2020-08-04 and later, for accounts with a hierarchical namespace enabled, List Blobs returns the\r\nDeletionId element for deleted blobs. DeletionId is an unsigned, 64-bit identifier. The element uniquely identifies a\r\nsoft-deleted path, to distinguish it from other deleted blobs with the same path.\r\nFor version 2020-10-02 and later, for accounts with a hierarchical namespace enabled, List Blobs returns the\r\nResourceType property element for the path. This can be either file or directory .\r\nhttps://docs.microsoft.com/en-us/rest/api/storageservices/list-blobs\r\nPage 8 of 16\n\nFor version 2021-02-12 and later, List Blobs will percent-encode (per RFC 2396) all Blob Name or BlobPrefix\nName element values. Specifically, it will do so for those values that contain characters that aren't valid in XML\n(U+FFFE or U+FFFF). If encoded, the Name element will include an Encoded=true attribute. Note that this only\noccurs for the Name element values containing the characters invalid in XML, not the remaining Name elements in the\nresponse.\nFor version 2021-06-08 and later, for accounts with a hierarchical namespace enabled, List Blobs returns the\nPlaceholder properties element. It returns this element in the BlobPrefix element for placeholder directories, when\nlisting deleted blobs with a delimiter. These placeholder directories exist to facilitate navigation to soft-deleted blobs.\nFor version 2021-06-08 and later, for accounts with a hierarchical namespace enabled, List Blobs returns the\nEncryptionContext element. If the encryption context property value is set it will return the set value.\nFor version 2020-02-10 and later, for accounts with a hierarchical namespace enabled, List Blobs returns the Expiry-Time element for deleted blobs. Expiry-Time is the time when the file will expire, and is returned for the file if the\nexpiry is set on the same.\nFor version 2026-02-06 and later, List Blobs returns the SmartAccessTier element for blobs in Smart tier.\nSmartAccessTier is the current billing tier of a blob in the Smart tier. Valid values are Hot , Cool , and Cold . For\ndetailed information about block blob tiering see Blob storage tiers.\nNote: Smart tier is currently in public preview.\nstring-valuestring-valueint-valuestring-valueblob-namedate-time-valuedate-time-vluetruetruedate-time-valuedate-time-valueetagowner user idowning group idpermission stringaccess control listfile | directorytruesize-in-bytesblob-content-type https://docs.microsoft.com/en-us/rest/api/storageservices/list-blobs\nPage 9 of 16\n\nsequence-numberBlockBlob|PageBlob|AppendBlobtierlocked|unlockedavailable | leased | expired | breaking | brokeninfinite | fixedidpending | success | aborted | failed source urlbytes copied/bytes totaldatetimeerror stringtrueencryption-key-sha256encryption-contextencryption-scope-nametruetruedatetimedatetimeno-of-daysnumber of tags between 1 to 10rehydrate prioritydate-time-valuetiervalueTagNameTagValueblob-prefix https://docs.microsoft.com/en-us/rest/api/storageservices/list-blobs\nPage 10 of 16\n\nSee Enumerating blob resources for a sample response.\r\nAuthorization is required when calling any data access operation in Azure Storage. You can authorize the List Blobs\r\noperation as described below.\r\nImportant\r\nMicrosoft recommends using Microsoft Entra ID with managed identities to authorize requests to Azure Storage.\r\nMicrosoft Entra ID provides superior security and ease of use compared to Shared Key authorization.\r\nMicrosoft Entra ID (recommended)\r\nShared access signatures (SAS)\r\nShared key\r\nAzure Storage supports using Microsoft Entra ID to authorize requests to blob data. With Microsoft Entra ID, you can\r\nuse Azure role-based access control (Azure RBAC) to grant permissions to a security principal. The security principal\r\nmay be a user, group, application service principal, or Azure managed identity. The security principal is authenticated by\r\nMicrosoft Entra ID to return an OAuth 2.0 token. The token can then be used to authorize a request against the Blob\r\nservice.\r\nTo learn more about authorization using Microsoft Entra ID, see Authorize access to blobs using Microsoft Entra ID.\r\nListed below are the RBAC action necessary for a Microsoft Entra user, group, managed identity, or service principal to\r\ncall the List Blobs operation, and the least privileged built-in Azure RBAC role that includes this action:\r\nAzure RBAC action: Microsoft.Storage/storageAccounts/blobServices/containers/blobs/read\r\nLeast privileged built-in role: Storage Blob Data Reader\r\nIf specifying include=tags :\r\nAzure RBAC action: Microsoft.Storage/storageAccounts/blobServices/containers/blobs/tags/read\r\nLeast privileged built-in role: Storage Blob Data Owner\r\nTo learn more about assigning roles using Azure RBAC, see Assign an Azure role for access to blob data.\r\nIf you have requested that uncommitted blobs be included in the enumeration, note that some properties aren't set until\r\nthe blob is committed. Some properties might not be returned in the response.\r\nThe x-ms-blob-sequence-number element is only returned for page blobs.\r\nThe OrMetadata element is only returned for block blobs.\r\nFor page blobs, the value returned in the Content-Length element corresponds to the value of the blob's x-ms-blob-content-length header.\r\nThe Content-MD5 element appears in the response body, only if it has been set on the blob by using version 2009-09-19\r\nor later. You can set the Content-MD5 property when the blob is created, or by calling Set Blob Properties. In version\r\n2012-02-12 and later, Put Blob sets a block blob’s MD5 value, even when the Put Blob request doesn’t include an\r\nMD5 header.\r\nhttps://docs.microsoft.com/en-us/rest/api/storageservices/list-blobs\r\nPage 11 of 16\n\nThe Metadata element is present only if the include=metadata parameter was specified on the URI. Within the\r\nMetadata element, the value of each name-value pair is listed within an element corresponding to the pair's name.\r\nNote that metadata requested with this parameter must be stored in accordance with the naming restrictions imposed by\r\nthe 2009-09-19 version of Blob Storage. Beginning with this version, all metadata names must adhere to the naming\r\nconventions for C# identifiers.\r\nIf a metadata name-value pair violates these naming restrictions, the response body indicates the problematic name\r\nwithin an x-ms-invalid-name element. The following XML fragment shows this:\r\n \r\n…\r\n\u003cMetadata\u003e\r\n \u003cMyMetadata1\u003efirst value\u003c/MyMetadata1\u003e\r\n \u003cMyMetadata2\u003esecond value\u003c/MyMetadata2\u003e\r\n \u003cx-ms-invalid-name\u003einvalid-metadata-name\u003c/x-ms-invalid-name\u003e\r\n\u003c/Metadata\u003e\r\n…\r\n \r\nThe Tags element is present only if the include=tags parameter was specified on the URI, and if there are tags on the\r\nblob. Within the TagSet element, up to 10 Tag elements are returned, each containing the key and value of the\r\nuser-defined, blob index tags. The ordering of tags isn't guaranteed in the response.\r\nThe Tags and TagCount elements aren't returned if there are no tags on the blob.\r\nThe storage service maintains strong consistency between a blob and its tags, but the secondary index is eventually\r\nconsistent. Tags can be visible in a response to List Blobs before they are visible to Find Blobs by Tags operations.\r\nSnapshots are listed in the response only if the include=snapshots parameter was specified on the URI. Snapshots\r\nlisted in the response don't include the LeaseStatus element, because snapshots can't have active leases.\r\nUsing service version 2021-06-08 and above, you can call List Blobs with a delimiter and include snapshots in the\r\nenumeration. For service versions prior to 2021-06-08, a request that includes both returns an InvalidQueryParameter\r\nerror (HTTP status code 400 – Bad Request).\r\nUncommitted blobs are listed in the response only if the include=uncommittedblobs parameter was specified on the\r\nURI. Uncommitted blobs listed in the response don't include any of the following elements:\r\nLast-Modified\r\nEtag\r\nContent-Type\r\nContent-Encoding\r\nContent-Language\r\nContent-MD5\r\nhttps://docs.microsoft.com/en-us/rest/api/storageservices/list-blobs\r\nPage 12 of 16\n\nCache-Control\r\nMetadata\r\nDeleted blobs are listed in the response only if the include=deleted parameter was specified on the URI. Deleted blobs\r\nlisted in the response don't include the Lease elements, because deleted blobs can't have active leases.\r\nDeleted snapshots are included in list response if include=deleted,snapshot was specified on the URI.\r\nThe OrMetadata element is present when an object replication policy has been evaluated on a blob, and the List\r\nBlobs call was made by using version 2019-12-12 or later. Within the OrMetadata element, the value of each name-value pair is listed within an element corresponding to the pair's name. The format of the name is or-{policy-id}_{rule-id} , where {policy-id} is a GUID that represents the object replication policy identifier on the storage\r\naccount. {rule-id} is a GUID that represents the rule identifier on the storage container. Valid values are complete or\r\nfailed .\r\n \r\n…\r\n\u003cOrMetadata\u003e\r\n \u003cor-e524bba7-4323-4b93-91f8-d09d5d0b7057_d86c51de-ef02-4264-bdcf-dcd389a6c7ac\u003ecomplete\u003c/or-e524bba7-4323-4b93-91f8-d\r\n \u003cor-2b302b5d-fcd5-44d6-a5ed-455bf27e17ea_4a398ff5-2a89-4090-879b-10248f23428e\u003efailed\u003c/or-2b302b5d-fcd5-44d6-a5ed-455\r\n\u003c/OrMetadata\u003e\r\n…\r\n \r\nThe ImmutabilityPolicyUntilDate and ImmutabilityPolicyMode elements are present only if the\r\ninclude=immutabilitypolicy parameter was specified on the URI.\r\n\u003cProperties\u003e\r\n \u003cImmutabilityPolicyUntilDate\u003edate-time-value\u003c/ImmutabilityPolicyUntilDate\u003e\r\n \u003cImmutabilityPolicyMode\u003eunlocked | locked \u003c/ImmutabilityPolicyMode\u003e\r\n\u003c/Properties\u003e\r\nThe LegalHold element is present only if the include=legalhold parameter was specified on the URI.\r\n\u003cProperties\u003e\r\n \u003cLegalHold\u003etrue | false \u003c/LegalHold\u003e\r\n\u003c/Properties\u003e\r\nIf you specify a value for the maxresults parameter, and the number of blobs to return exceeds this value, or exceeds\r\nthe default value for maxresults , the response body contains a NextMarker element. This element indicates the next\r\nblob to return on a subsequent request. In certain cases, the service might return the NextMarker element even though\r\nthe number of results returned is less than the value of maxresults .\r\nTo return the next set of items, specify the value of NextMarker as the marker parameter on the URI for the subsequent\r\nrequest. Note that the value of NextMarker should be treated as opaque.\r\nhttps://docs.microsoft.com/en-us/rest/api/storageservices/list-blobs\r\nPage 13 of 16\n\nThe delimiter parameter enables the caller to traverse the blob namespace by using a user-configured delimiter. In this\r\nway, you can traverse a virtual hierarchy of blobs as though it were a file system. The delimiter can be a single character\r\nor a string.\r\nWhen the request includes this parameter, the operation returns a BlobPrefix element. The BlobPrefix element is\r\nreturned in place of all blobs with names that begin with the same substring, up to the appearance of the delimiter\r\ncharacter. The value of the BlobPrefix element is substring+delimiter, where substring is the common substring that\r\nbegins one or more blob names, and delimiter is the value of the delimiter parameter.\r\nYou can use the value of BlobPrefix to make a subsequent call to list the blobs that begin with this prefix. You do this\r\nby specifying the value of BlobPrefix for the prefix parameter on the request URI.\r\nNote that each BlobPrefix element returned counts toward the maximum result, just as each Blob element does.\r\nBlobs are listed in alphabetical order in the response body, with upper-case letters listed first. Note that for accounts with\r\na hierarchical namespace enabled, / is treated as the lowest sort order. This difference in behavior is only applicable to\r\nlisting recursively.\r\nCopyStatusDescription contains more information about the Copy Blob failure.\r\nNote\r\nThe CopySource element contains the URL of the source blob, including any request parameters used in the copy\r\noperation. If a Shared Access Signature (SAS) token was used to access the source blob, the SAS token will appear in the\r\nCopySource value, except that the signature ( sig query parameter) will be removed.\r\nWhen a copy attempt fails, CopyStatus is set to pending if Blob Storage is still retrying the operation. The\r\nCopyStatusDescription text describes the failure that might have occurred during the last copy attempt.\r\nWhen CopyStatus is set to failed , the CopyStatusDescription text describes the error that caused the copy\r\noperation to fail.\r\nThe following table describes the fields of every CopyStatusDescription value.\r\nComponent Description\r\nHTTP status\r\ncode\r\nStandard three-digit integer specifying the failure.\r\nError code\r\nKeyword that describes the error. It's provided by Azure in the \u003cErrorCode\u003e element. If no\r\n\u003cErrorCode\u003e element appears, the service returns a keyword that contains standard error text\r\nassociated with the three-digit HTTP status code in the HTTP specification. For more information,\r\nsee Common REST API error codes.\r\nInformation Detailed description of the failure, in quotes.\r\nThe following table describes the CopyStatus and CopyStatusDescription values of common failure scenarios.\r\nImportant\r\nhttps://docs.microsoft.com/en-us/rest/api/storageservices/list-blobs\r\nPage 14 of 16\n\nDescription text shown here can change without warning, even without a version change. Don't rely on matching this\r\nexact text.\r\nScenario\r\nCopy\r\nStatus\r\nvalue\r\nCopy Status Description value\r\nCopy operation completed successfully. success empty\r\nUser aborted the copy operation before\r\nit completed.\r\naborted empty\r\nA failure occurred when reading from\r\nthe source blob during a copy operation.\r\nThe operation will be retried.\r\npending\r\n502 BadGateway \"Encountered a retryable error when\r\nreading the source. Will retry. Time of failure: \u003ctime\u003e\"\r\nA failure occurred when writing to the\r\ndestination blob of a copy operation.\r\nThe operation will be retried.\r\npending\r\n500 InternalServerError \"Encountered a retryable error.\r\nWill retry. Time of failure: \u003ctime\u003e\"\r\nAn unrecoverable failure occurred when\r\nreading from the source blob of a copy\r\noperation.\r\nfailed\r\n404 ResourceNotFound \"Copy failed when reading the\r\nsource.\" When the service reports this underlying error, it\r\nreturns ResourceNotFound in the \u003cErrorCode\u003e element. If\r\nno \u003cErrorCode\u003e element appeared in the response, a\r\nstandard string representation of the HTTP status, such as\r\nNotFound , appears.\r\nThe timeout period limiting all copy\r\noperations elapsed. (Currently the\r\ntimeout period is two weeks.)\r\nfailed\r\n500 OperationCancelled \"The copy exceeded the\r\nmaximum allowed time.\"\r\nThe copy operation failed too often\r\nwhen reading from the source, and\r\ndidn’t meet a minimum ratio of attempts\r\nto successes. (This timeout prevents\r\nretrying a very poor source over two\r\nweeks before failing).\r\nfailed\r\n500 OperationCancelled \"The copy failed when reading the\r\nsource.\"\r\nPricing requests can originate from clients that use Blob Storage APIs, either directly through the Blob Storage REST\r\nAPI, or from an Azure Storage client library. These requests accrue charges per transaction. The type of transaction\r\naffects how the account is charged. For example, read transactions accrue to a different billing category than write\r\ntransactions. The following table shows the billing category for List Blobs requests based on the storage account type:\r\nOperation Storage account type Billing category\r\nList Blobs\r\nPremium block blob\r\nStandard general-purpose v2\r\nStandard general-purpose v1\r\nList and Create Container operations\r\nhttps://docs.microsoft.com/en-us/rest/api/storageservices/list-blobs\r\nPage 15 of 16\n\nTo learn about pricing for the specified billing category, see Azure Blob Storage Pricing.\r\nStatus and error codes\r\nBlob Storage error codes\r\nSource: https://docs.microsoft.com/en-us/rest/api/storageservices/list-blobs\r\nhttps://docs.microsoft.com/en-us/rest/api/storageservices/list-blobs\r\nPage 16 of 16",
	"extraction_quality": 1,
	"language": "EN",
	"sources": [
		"MITRE"
	],
	"references": [
		"https://docs.microsoft.com/en-us/rest/api/storageservices/list-blobs"
	],
	"report_names": [
		"list-blobs"
	],
	"threat_actors": [],
	"ts_created_at": 1775438970,
	"ts_updated_at": 1775791247,
	"ts_creation_date": 0,
	"ts_modification_date": 0,
	"files": {
		"pdf": "https://archive.orkl.eu/15e7c61518bfc8569da4cbc7e287b87faffdd70c.pdf",
		"text": "https://archive.orkl.eu/15e7c61518bfc8569da4cbc7e287b87faffdd70c.txt",
		"img": "https://archive.orkl.eu/15e7c61518bfc8569da4cbc7e287b87faffdd70c.jpg"
	}
}