Azure Storage

Create a local storage account, then store and read blobs, queue messages, table entities and files over REST, and with Pro, Data Lake files.

Plan: Free298 of 310 operations implemented across 6 APIs, 12 failed in testing6Known differences

Free: Storage accounts, Blob, Queue, Table and Files.Pro: Data Lake.

Files works through its REST API only: mounting a share over SMB or NFS wasn't established. Data Lake lists paths as XML.

Example checked on Vera 1.2.2, 8 November 2026. Each coverage note names its own evidence and date.

Connect

Start Vera as in Get started, with your license key activated and the emulator started by the Vera launcher (Activate Pro). Then open Bash in a terminal of its own (on macOS, whose terminal starts zsh, type bash first), go to an empty scratch directory and run this; it needs curl and Python 3, and jq. It fetches the emulator's own certificate, so every request checks TLS, and defines data_request and data_arm, which this page's commands use. The bearer token vera-local is a dummy local credential, not your license key.

export VERA_CA_CERT="$PWD/vera-ca.pem"
curl --fail --silent --show-error --noproxy '*' --insecure \
  https://localhost:8543/_vera/ca.pem --output "$VERA_CA_CERT"
curl --fail --silent --show-error --noproxy '*' \
  --cacert "$VERA_CA_CERT" https://localhost:8543/_vera/health; echo

export VERA_CA="$VERA_CA_CERT"
export ARM='https://localhost:8543'
export SUB='00000000-0000-0000-0000-000000000001'
export TENANT='00000000-0000-0000-0000-0000000000a1'
export RG='azdata-rg'
export ROOT="/subscriptions/$SUB/resourceGroups/$RG"
export AUDIT_TMP="$(mktemp -d)"

56 more lines: show the full setup
# Every .localhost host name is connected to loopback, and TLS is verified.
# DATA_RESPONSE is replaced after each call: copy any IDs before the next one.
data_request() {
  local method="$1" url="$2" host status
  shift 2
  case "$url" in
    https://localhost:8543/*|https://*.localhost:8543/*) ;;
    *) printf 'Refusing non-local URL: %s\n' "$url" >&2; return 1 ;;
  esac
  host="${url#https://}"
  host="${host%%/*}"
  host="${host%:8543}"
  status=$(curl --noproxy '*' --silent --show-error \
    --cacert "$VERA_CA" --resolve "$host:8543:127.0.0.1" \
    -H 'Authorization: Bearer vera-local' \
    -X "$method" "$url" "$@" \
    -D "$AUDIT_TMP/headers" -o "$AUDIT_TMP/body" -w '%{http_code}') || return
  DATA_RESPONSE=$(cat "$AUDIT_TMP/body")
  printf 'HTTP %s\n%s\n' "$status" "$DATA_RESPONSE"
  case "$status" in 2??) ;; *) return 1 ;; esac
}

# Polls the operation URL from the last successful management change, even
# after HTTP 200 or 201. Don't replace it with a fixed sleep.
data_wait_arm() {
  local operation attempt status state delay
  operation=$(awk 'BEGIN {IGNORECASE=1} tolower($1)=="azure-asyncoperation:" {gsub("\r", "", $2); print $2; exit}' "$AUDIT_TMP/headers")
  if [ -z "$operation" ]; then
    operation=$(awk 'tolower($1)=="location:" {gsub("\r", "", $2); print $2; exit}' "$AUDIT_TMP/headers")
  fi
  [ -z "$operation" ] && return 0
  case "$operation" in "$ARM"/_vera/operations/*) ;; *) printf 'Inspect unexpected operation URL: %s\n' "$operation" >&2; return 1 ;; esac
  for attempt in $(seq 1 60); do
    data_request GET "$operation" || return
    status=$(awk '/^HTTP\// {code=$2} END {print code}' "$AUDIT_TMP/headers")
    state=$(printf '%s' "$DATA_RESPONSE" | jq -r '.status // empty' 2>/dev/null) || state=''
    case "$state" in
      Failed|Canceled|Cancelled) return 1 ;;
      Succeeded) return 0 ;;
      InProgress|Running|Accepted) ;;
      *) [ "$status" != '202' ] && return 0 ;;
    esac
    delay=$(awk 'tolower($1)=="retry-after:" {gsub("\r", "", $2); print $2; exit}' "$AUDIT_TMP/headers")
    case "$delay" in ''|*[!0-9]*) delay=1 ;; esac
    sleep "$delay"
  done
  printf 'Operation did not finish within the polling limit\n' >&2
  return 1
}

data_arm() {
  local method="$1" path="$2"
  shift 2
  data_request "$method" "$ARM$path" "$@" || return
  case "$method" in PUT|PATCH|POST|DELETE) data_wait_arm ;; esac
}

The health check answers {"cloud": "azure", "generation_status": "generated", "status": "ok"}. Requests go only to the emulator at https://localhost:8543: the helper refuses any other address, including the Azure-looking URLs some responses hold. When you've finished, close the terminal and delete the scratch directory; that removes only these local files, not what you created in the emulator.

The examples use these API versions, tested with this build. Keep them as shown rather than the versions an SDK picks: other versions weren’t checked.

API	Version	Sent as
Resource groups	`2025-04-01`	`api-version` parameter
Storage accounts	`2026-09-01`	`api-version` parameter
Blob	`2026-12-06`	`x-ms-version` header
Queue	`2026-04-06`	`x-ms-version` header
Table	`2019-02-02`	`x-ms-version` header
Files	`2026-12-06`	`x-ms-version` header
Data Lake (Pro)	`2026-06-06`	`x-ms-version` header

Account management goes to https://localhost:8543. Each data API has the account’s own host name, on the same port: azdatastore.blob.core.localhost, azdatastore.queue.core.localhost, azdatastore.table.core.localhost, azdatastore.file.core.localhost and azdatastore.dfs.core.localhost. The emulator finds the account by that name, so keep it in the URL. data_request gives curl a --resolve for it, which connects to 127.0.0.1 while keeping the name for routing and TLS, so the names don’t need to resolve on your machine. See data host names.

Example

Create a storage account, then upload a blob, read it back and list its container. The sections after this one use the same account for queues, tables, files and Data Lake, and Clean up deletes it at the end.

Create the resource group the examples share, then the account. data_arm prints each response, then polls the request’s operation until it has finished (long-running operations), so the account exists before the next command:

data_arm PUT "$ROOT?api-version=2025-04-01" \
  -H 'Content-Type: application/json' --data '{"location":"eastus"}'
STORAGE="$ROOT/providers/Microsoft.Storage/storageAccounts/azdatastore"
data_arm PUT "$STORAGE?api-version=2026-09-01" \
  -H 'Content-Type: application/json' \
  --data '{"location":"eastus","sku":{"name":"Standard_LRS"},"kind":"StorageV2"}'
data_arm GET "$STORAGE?api-version=2026-09-01"

Creating the account answers HTTP 202. The GET answers HTTP 200 with the account; these are selected fields:

{
  "name": "azdatastore",
  "kind": "StorageV2"
}

Create a container, upload hello vera to it as a block blob, read the blob and list the container:

BLOB='https://azdatastore.blob.core.localhost:8543'
data_request PUT "$BLOB/azdata?restype=container" -H 'x-ms-version: 2026-12-06'
data_request PUT "$BLOB/azdata/hello.txt" -H 'x-ms-version: 2026-12-06' \
  -H 'x-ms-blob-type: BlockBlob' -H 'Content-Type: text/plain' \
  --data-binary 'hello vera'
data_request GET "$BLOB/azdata/hello.txt" -H 'x-ms-version: 2026-12-06'
data_request GET "$BLOB/azdata?restype=container&comp=list" -H 'x-ms-version: 2026-12-06'

The container and the upload answer HTTP 201. The read returns the ten bytes you uploaded:

HTTP 200
hello vera

The list answers HTTP 200 with XML that names hello.txt. Its ServiceEndpoint is a name, not an address: keep sending requests to the host above.

Delete the blob, then the container. Both answer HTTP 202:

data_request DELETE "$BLOB/azdata/hello.txt" -H 'x-ms-version: 2026-12-06'
data_request DELETE "$BLOB/azdata?restype=container" -H 'x-ms-version: 2026-12-06'

Queue messages

Create a queue, send a message, receive it, then delete the queue. This example base64-encodes the message: aGVsbG8gdmVyYQ== is hello vera.

QUEUE='https://azdatastore.queue.core.localhost:8543'
data_request PUT "$QUEUE/azdataqueue" -H 'x-ms-version: 2026-04-06'
data_request POST "$QUEUE/azdataqueue/messages" -H 'x-ms-version: 2026-04-06' \
  -H 'Content-Type: application/xml' \
  --data '<QueueMessage><MessageText>aGVsbG8gdmVyYQ==</MessageText></QueueMessage>'
data_request GET "$QUEUE/azdataqueue/messages?numofmessages=1&visibilitytimeout=1" \
  -H 'x-ms-version: 2026-04-06'
data_request DELETE "$QUEUE/azdataqueue" -H 'x-ms-version: 2026-04-06'

Creating the queue and sending answer HTTP 201. The receive answers HTTP 200 with XML holding the message’s ID, its pop receipt and its text, aGVsbG8gdmVyYQ==. Deleting the queue answers HTTP 204.

Table entities

Create a table, insert an entity, read it back by its keys, then delete the table. Send Accept: application/json;odata=nometadata with every request, the delete too: without it, the delete answers HTTP 415 with AtomFormatNotSupported.

TABLE='https://azdatastore.table.core.localhost:8543'
data_request POST "$TABLE/Tables" -H 'x-ms-version: 2019-02-02' \
  -H 'Accept: application/json;odata=nometadata' -H 'Content-Type: application/json' \
  --data '{"TableName":"AzdataTable"}'
data_request POST "$TABLE/AzdataTable" -H 'x-ms-version: 2019-02-02' \
  -H 'Accept: application/json;odata=nometadata' -H 'Content-Type: application/json' \
  --data '{"PartitionKey":"docs","RowKey":"1","message":"hello vera"}'
data_request GET "$TABLE/AzdataTable(PartitionKey='docs',RowKey='1')" \
  -H 'x-ms-version: 2019-02-02' -H 'Accept: application/json;odata=nometadata'

Creating the table and inserting the entity answer HTTP 201. The read answers HTTP 200 with the entity and a Timestamp the emulator adds; these are selected fields:

{
  "PartitionKey": "docs",
  "RowKey": "1",
  "message": "hello vera"
}

Inserting the same keys again answers HTTP 409 with EntityAlreadyExists. Delete the table, which answers HTTP 204:

data_request DELETE "$TABLE/Tables('AzdataTable')" -H 'x-ms-version: 2019-02-02' \
  -H 'Accept: application/json;odata=nometadata'

Files

Create a share and a ten-byte file in it, write the file’s bytes as a range, read the file, then delete the file and the share. This is the Files REST API: it doesn’t mount the share.

FILE='https://azdatastore.file.core.localhost:8543'
data_request PUT "$FILE/azdatashare?restype=share" -H 'x-ms-version: 2026-12-06'
data_request PUT "$FILE/azdatashare/hello.txt" -H 'x-ms-version: 2026-12-06' \
  -H 'x-ms-type: file' -H 'x-ms-content-length: 10'
data_request PUT "$FILE/azdatashare/hello.txt?comp=range" -H 'x-ms-version: 2026-12-06' \
  -H 'Range: bytes=0-9' -H 'x-ms-write: update' \
  -H 'Content-Type: application/octet-stream' --data-binary 'hello vera'
data_request GET "$FILE/azdatashare/hello.txt" -H 'x-ms-version: 2026-12-06'
data_request DELETE "$FILE/azdatashare/hello.txt" -H 'x-ms-version: 2026-12-06'
data_request DELETE "$FILE/azdatashare?restype=share" -H 'x-ms-version: 2026-12-06'

Creating the share and the file and writing the range answer HTTP 201. The read answers HTTP 200 with hello vera, and both deletes answer HTTP 202. A range outside the file, such as bytes 20 to 22, answers HTTP 416 with InvalidRange. Send the range’s bytes as application/octet-stream: without that header, the write answered HTTP 400 with InvalidHeaderValue.

Data Lake

Data Lake needs Pro. Create a file system and a file, append ten bytes and flush them, read the file and list the file system, then delete the file and the file system.

DFS='https://azdatastore.dfs.core.localhost:8543'
data_request PUT "$DFS/azdatafs?resource=filesystem" -H 'x-ms-version: 2026-06-06'
data_request PUT "$DFS/azdatafs/hello.txt?resource=file" -H 'x-ms-version: 2026-06-06'
data_request PATCH "$DFS/azdatafs/hello.txt?action=append&position=0" \
  -H 'x-ms-version: 2026-06-06' \
  -H 'Content-Type: application/octet-stream' --data-binary 'hello vera'
data_request PATCH "$DFS/azdatafs/hello.txt?action=flush&position=10" \
  -H 'x-ms-version: 2026-06-06' --data-binary ''
data_request GET "$DFS/azdatafs/hello.txt" -H 'x-ms-version: 2026-06-06'
data_request GET "$DFS/azdatafs?resource=filesystem&recursive=true" \
  -H 'x-ms-version: 2026-06-06'
data_request DELETE "$DFS/azdatafs/hello.txt" -H 'x-ms-version: 2026-06-06'
data_request DELETE "$DFS/azdatafs?resource=filesystem" -H 'x-ms-version: 2026-06-06'

Both creates answer HTTP 201, the append HTTP 202 and the flush HTTP 200. The read returns hello vera. The listing answers HTTP 200 with an XML PathList in which hello.txt has a content length of 10. Deleting the file answers HTTP 200, and the file system HTTP 202. Flushing at a position past the appended data, such as 100, answers HTTP 400 with InvalidFlushPosition. Send the appended bytes as application/octet-stream, and give the flush an empty body so curl sends a zero Content-Length: without them, the append and the flush each answered HTTP 400.

Clean up

Delete the account. Delete its data first, as the sections above do: deleting the account wasn’t shown to erase data left in it.

data_arm DELETE "$STORAGE?api-version=2026-09-01"

The delete answers HTTP 200, and a GET of the account then answers HTTP 404. The resource group azdata-rg stays, since deleting a group fails in Vera 1.2.2: see deleting resource groups. Other pages’ examples reuse it. To remove it and anything else left over, start a fresh emulator: see Stop and start again.

Supported features

Storage accounts: a StorageV2 account created, read, listed in its resource group and deleted. A missing account answers HTTP 404.
Blob (Free): containers created, listed and deleted, and block blobs uploaded, read back byte for byte and deleted. A missing blob answers HTTP 404 with BlobNotFound.
Queue (Free): queues created and deleted, and a message sent and received with its ID, pop receipt and text.
Table (Free): tables created and deleted, and an entity inserted and read by its partition and row keys, with a generated Timestamp. Duplicate keys answer HTTP 409 with EntityAlreadyExists.
Files (Free): shares and files created and deleted, and a range written and read back through REST. A range outside the file answers HTTP 416 with InvalidRange.
Data Lake (Pro): file systems and files created and deleted, data appended, flushed and read back, and paths listed recursively. A flush at the wrong position answers HTTP 400 with InvalidFlushPosition.
Not run as examples: blob leases, snapshots, copies, tags and tiers, append and page blobs, peeking, updating and deleting queue messages, table queries, updates and merges, file directories, and Data Lake access control, renames and leases. The API coverage marks these from a review of Vera 1.2.0’s source, with their limits in the notes.

Limitations

The main limits are below. A few more apply to every service, and the API coverage notes cover smaller differences.

Files is REST only. The Files API stored and returned the bytes, but mounting a share over SMB or NFS wasn’t established, and no mount command was tested.
Data Lake path lists are XML. Listing a file system returned an XML PathList. Whether Azure’s SDKs read it wasn’t tested. Access control, renames, hierarchical namespace settings and whether the Blob and Data Lake APIs see the same data weren’t tested either. Path_Update serves action=setProperties; an append, a flush or an access-control change goes to that action’s own operation, whose status codes can differ.
Use the host names, versions and headers shown. Each data API is routed by its account’s host name, and other versions and request forms weren’t checked. The Table API’s JSON Accept header is needed on deletes too. Vera echoes back the x-ms-version you send, so the version in a response doesn’t show that version’s behavior.
SAS and access-policy enforcement isn’t established. Vera replaces a request’s credentials before its bundled storage engine sees the request, and drops the SAS parameters when a signature is present. Access policies can be stored and read back, but SAS, access policy and role-based enforcement isn’t established.
Twelve operations aren’t available. The bundled storage engine doesn’t implement copying from a URL (AppendBlob_AppendBlockFromUrl, BlockBlob_UploadBlobFromUrl, PageBlob_UploadPagesFromUrl), incremental page blob copies (PageBlob_CopyIncremental), blob queries (BlockBlob_Query), expiry (Blob_SetExpiry), immutability policies and legal holds (Blob_SetImmutabilityPolicy, Blob_DeleteImmutabilityPolicy, Blob_SetLegalHold), undelete (Blob_Undelete) or container restore (Container_Restore). On Vera 1.2.0-rc.3, each answered HTTP 501 with APINotImplemented. Queue’s Service_GetUserDelegationKey has no operation in the engine and answered HTTP 400. Blob’s user delegation key is a separate operation.
Renaming a container doesn’t rename it. Container_Rename answers HTTP 201 because the request creates the destination container instead. On Vera 1.2.0-rc.3, the source container stayed in place and its blob wasn’t in the destination, so the success status doesn’t mean anything moved.
Page range diffs return every range. A page range list with prevsnapshot (PageBlob_GetPageRangesDiff) is answered as an ordinary list: on Vera 1.2.0-rc.3, it returned a range written before the snapshot as well as the one written after it.
File range lists ignore paging. File_ListAllRanges is answered by the plain range list: with maxresults=1, Vera 1.2.0-rc.3 returned both of a file’s ranges and no continuation marker.
Apache Arrow listings return XML. A container listing that asks for Apache Arrow gets the XML fallback that the API allows. No Arrow stream is produced.
Connection tests don’t connect. Connectors_TestExistingConnection and the Blob access point connection tests return local failure diagnostics without contacting the external service, so they don’t show an S3 or Azure network connection.
Storage task assignments don’t run tasks. Creating an assignment records it and doesn’t run its task. Its reports list only task runs that were recorded.
One message was received. Deleting a message by its pop receipt, visibility timeouts beyond that one receive, ordering and repeated delivery of failed messages weren’t tested.
Deleting an account isn’t shown to erase its data. The examples delete their blobs, queues, tables, files and file systems before the account.

API coverage

Every operation of the APIs on this page, from their pinned public definitions, and whether Vera 1.2.0 implements it. Only the API surfaces in this release are listed, and each operation once. Implementation availability was reviewed against the Vera 1.2.0 source on 6 November 2026. Source inspection identifies a local implementation and its known limits; it doesn't mean every operation or API version was tested with a request. Each note names its evidence: a Local observation without a build or date is from Vera 1.2.0 preview, on 5 November 2026, and one from a later build, such as Vera 1.2.0-rc.3 or Vera 1.2.2, names that build and its date. No response was compared with Azure's. What the statuses mean

Blob 2026-12-06Plan: Free

58 of 69 implemented · 2 known differences · 11 failed in testing

Version 2026-12-06, from the Azure REST API specifications at commit 21bbf1b.

AppendBlob

3 of 4 implemented · 1 failed in testing

Operation	Status	Notes
AppendBlob_AppendBlock	Implemented	Source inspection: The bundled storage engine handles it locally. Vera replaces the request's credentials and drops its SAS parameters, so SAS and RBAC enforcement aren't established, and the requested `x-ms-version` is echoed back.
AppendBlob_AppendBlockFromUrl	Failed in testing	Source inspection: The bundled storage engine doesn't implement this operation: it answers HTTP 501 `APINotImplemented`. Local observation: Vera 1.2.0-rc.3, 6 November 2026 — this operation, sent to a newly created account and container, returned HTTP 501 `APINotImplemented`.
AppendBlob_Create	Implemented	Source inspection: The bundled storage engine handles it locally. Vera replaces the request's credentials and drops its SAS parameters, so SAS and RBAC enforcement aren't established, and the requested `x-ms-version` is echoed back.
AppendBlob_Seal	Implemented	Source inspection: The bundled storage engine handles it locally. Vera replaces the request's credentials and drops its SAS parameters, so SAS and RBAC enforcement aren't established, and the requested `x-ms-version` is echoed back.

Blob

18 of 23 implemented · 5 failed in testing

Operation	Status	Notes
Blob_AbortCopyFromUrl	Implemented	Source inspection: The bundled storage engine handles it locally. Vera replaces the request's credentials and drops its SAS parameters, so SAS and RBAC enforcement aren't established, and the requested `x-ms-version` is echoed back.
Blob_AcquireLease	Implemented	Source inspection: The bundled storage engine handles it locally. Vera replaces the request's credentials and drops its SAS parameters, so SAS and RBAC enforcement aren't established, and the requested `x-ms-version` is echoed back.
Blob_BreakLease	Implemented	Source inspection: The bundled storage engine handles it locally. Vera replaces the request's credentials and drops its SAS parameters, so SAS and RBAC enforcement aren't established, and the requested `x-ms-version` is echoed back.
Blob_ChangeLease	Implemented	Source inspection: The bundled storage engine handles it locally. Vera replaces the request's credentials and drops its SAS parameters, so SAS and RBAC enforcement aren't established, and the requested `x-ms-version` is echoed back.
Blob_CopyFromUrl	Implemented	Source inspection: The bundled storage engine handles it locally. Vera replaces the request's credentials and drops its SAS parameters, so SAS and RBAC enforcement aren't established, and the requested `x-ms-version` is echoed back.
Blob_CreateSnapshot	Implemented	Source inspection: The bundled storage engine handles it locally. Vera replaces the request's credentials and drops its SAS parameters, so SAS and RBAC enforcement aren't established, and the requested `x-ms-version` is echoed back.
Blob_Delete	Implemented	Local observation: Deleted the example's block blob (HTTP 202).
Blob_DeleteImmutabilityPolicy	Failed in testing	Source inspection: The bundled storage engine doesn't implement this operation: it answers HTTP 501 `APINotImplemented`. Local observation: Vera 1.2.0-rc.3, 6 November 2026 — this operation, sent to a newly created account and container, returned HTTP 501 `APINotImplemented`.
Blob_Download	Implemented	Local observation: Returned the uploaded 10 bytes, `hello vera` (HTTP 200). A blob that doesn't exist answered HTTP 404 `BlobNotFound`.
Blob_GetAccountInfo	Implemented	Source inspection: The bundled storage engine handles it locally. Vera replaces the request's credentials and drops its SAS parameters, so SAS and RBAC enforcement aren't established, and the requested `x-ms-version` is echoed back.
Blob_GetProperties	Implemented	Source inspection: The bundled storage engine handles it locally. Vera replaces the request's credentials and drops its SAS parameters, so SAS and RBAC enforcement aren't established, and the requested `x-ms-version` is echoed back.
Blob_GetTags	Implemented	Source inspection: The bundled storage engine handles it locally. Vera replaces the request's credentials and drops its SAS parameters, so SAS and RBAC enforcement aren't established, and the requested `x-ms-version` is echoed back.
Blob_ReleaseLease	Implemented	Source inspection: The bundled storage engine handles it locally. Vera replaces the request's credentials and drops its SAS parameters, so SAS and RBAC enforcement aren't established, and the requested `x-ms-version` is echoed back.
Blob_RenewLease	Implemented	Source inspection: The bundled storage engine handles it locally. Vera replaces the request's credentials and drops its SAS parameters, so SAS and RBAC enforcement aren't established, and the requested `x-ms-version` is echoed back.
Blob_SetExpiry	Failed in testing	Source inspection: The bundled storage engine doesn't implement this operation: it answers HTTP 501 `APINotImplemented`. Local observation: Vera 1.2.0-rc.3, 6 November 2026 — this operation, sent to a newly created account and container, returned HTTP 501 `APINotImplemented`.
Blob_SetImmutabilityPolicy	Failed in testing	Source inspection: The bundled storage engine doesn't implement this operation: it answers HTTP 501 `APINotImplemented`. Local observation: Vera 1.2.0-rc.3, 6 November 2026 — this operation, sent to a newly created account and container, returned HTTP 501 `APINotImplemented`.
Blob_SetLegalHold	Failed in testing	Source inspection: The bundled storage engine doesn't implement this operation: it answers HTTP 501 `APINotImplemented`. Local observation: Vera 1.2.0-rc.3, 6 November 2026 — this operation, sent to a newly created account and container, returned HTTP 501 `APINotImplemented`.
Blob_SetMetadata	Implemented	Source inspection: The bundled storage engine handles it locally. Vera replaces the request's credentials and drops its SAS parameters, so SAS and RBAC enforcement aren't established, and the requested `x-ms-version` is echoed back.
Blob_SetProperties	Implemented	Source inspection: The bundled storage engine handles it locally. Vera replaces the request's credentials and drops its SAS parameters, so SAS and RBAC enforcement aren't established, and the requested `x-ms-version` is echoed back.
Blob_SetTags	Implemented	Source inspection: The bundled storage engine handles it locally. Vera replaces the request's credentials and drops its SAS parameters, so SAS and RBAC enforcement aren't established, and the requested `x-ms-version` is echoed back.
Blob_SetTier	Implemented	Source inspection: The bundled storage engine handles it locally. Vera replaces the request's credentials and drops its SAS parameters, so SAS and RBAC enforcement aren't established, and the requested `x-ms-version` is echoed back.
Blob_StartCopyFromUrl	Implemented	Source inspection: The bundled storage engine handles it locally. Vera replaces the request's credentials and drops its SAS parameters, so SAS and RBAC enforcement aren't established, and the requested `x-ms-version` is echoed back.
Blob_Undelete	Failed in testing	Source inspection: The bundled storage engine doesn't implement this operation: it answers HTTP 501 `APINotImplemented`. Local observation: Vera 1.2.0-rc.3, 6 November 2026 — this operation, sent to a newly created account and container, returned HTTP 501 `APINotImplemented`.

BlockBlob

5 of 7 implemented · 2 failed in testing

Operation	Status	Notes
BlockBlob_CommitBlockList	Implemented	Source inspection: The bundled storage engine handles it locally. Vera replaces the request's credentials and drops its SAS parameters, so SAS and RBAC enforcement aren't established, and the requested `x-ms-version` is echoed back.
BlockBlob_GetBlockList	Implemented	Source inspection: The bundled storage engine handles it locally. Vera replaces the request's credentials and drops its SAS parameters, so SAS and RBAC enforcement aren't established, and the requested `x-ms-version` is echoed back.
BlockBlob_Query	Failed in testing	Source inspection: The bundled storage engine doesn't implement this operation: it answers HTTP 501 `APINotImplemented`. Local observation: Vera 1.2.0-rc.3, 6 November 2026 — this operation, sent to a newly created account and container, returned HTTP 501 `APINotImplemented`.
BlockBlob_StageBlock	Implemented	Source inspection: The bundled storage engine handles it locally. Vera replaces the request's credentials and drops its SAS parameters, so SAS and RBAC enforcement aren't established, and the requested `x-ms-version` is echoed back.
BlockBlob_StageBlockFromUrl	Implemented	Source inspection: The bundled storage engine handles it locally. Vera replaces the request's credentials and drops its SAS parameters, so SAS and RBAC enforcement aren't established, and the requested `x-ms-version` is echoed back.
BlockBlob_Upload	Implemented	Local observation: Uploaded a 10-byte block blob (HTTP 201).
BlockBlob_UploadBlobFromUrl	Failed in testing	Source inspection: The bundled storage engine doesn't implement this operation: it answers HTTP 501 `APINotImplemented`. Local observation: Vera 1.2.0-rc.3, 6 November 2026 — this operation, sent to a newly created account and container, returned HTTP 501 `APINotImplemented`.

Container

18 of 19 implemented · 1 known difference · 1 failed in testing

Operation	Status	Notes
Container_AcquireLease	Implemented	Source inspection: The bundled storage engine handles it locally. Vera replaces the request's credentials and drops its SAS parameters, so SAS and RBAC enforcement aren't established, and the requested `x-ms-version` is echoed back.
Container_BreakLease	Implemented	Source inspection: The bundled storage engine handles it locally. Vera replaces the request's credentials and drops its SAS parameters, so SAS and RBAC enforcement aren't established, and the requested `x-ms-version` is echoed back.
Container_ChangeLease	Implemented	Source inspection: The bundled storage engine handles it locally. Vera replaces the request's credentials and drops its SAS parameters, so SAS and RBAC enforcement aren't established, and the requested `x-ms-version` is echoed back.
Container_Create	Implemented	Local observation: Created a container (HTTP 201).
Container_Delete	Implemented	Local observation: Deleted the emptied container (HTTP 202).
Container_FindBlobsByTags	Implemented	Source inspection: The bundled storage engine handles it locally. Vera replaces the request's credentials and drops its SAS parameters, so SAS and RBAC enforcement aren't established, and the requested `x-ms-version` is echoed back.
Container_GetAccessPolicy	Implemented	Source inspection: Returns the stored access policies. Reading and writing them doesn't establish that they're enforced. The bundled storage engine handles it locally. Vera replaces the request's credentials and drops its SAS parameters, so SAS and RBAC enforcement aren't established, and the requested `x-ms-version` is echoed back.
Container_GetProperties	Implemented	Source inspection: The bundled storage engine handles it locally. Vera replaces the request's credentials and drops its SAS parameters, so SAS and RBAC enforcement aren't established, and the requested `x-ms-version` is echoed back.
Container_ListBlobFlatSegmentApacheArrow	Implemented	Source inspection: Lists the container's blobs, answering an Apache Arrow `Accept` preference with the XML fallback that the API allows. No Arrow stream is produced, and Arrow-specific `endBefore` behavior isn't established. The bundled storage engine handles it locally. Vera replaces the request's credentials and drops its SAS parameters, so SAS and RBAC enforcement aren't established, and the requested `x-ms-version` is echoed back. Local observation: Vera 1.2.0-rc.3, 6 November 2026 — a flat container listing that asked for Apache Arrow returned the XML fallback.
Container_ListBlobHierarchySegment	Implemented	Source inspection: The bundled storage engine handles it locally. Vera replaces the request's credentials and drops its SAS parameters, so SAS and RBAC enforcement aren't established, and the requested `x-ms-version` is echoed back.
Container_ListBlobHierarchySegmentApacheArrow	Implemented	Source inspection: Lists the container's blobs, answering an Apache Arrow `Accept` preference with the XML fallback that the API allows. No Arrow stream is produced, and Arrow-specific `endBefore` behavior isn't established. The bundled storage engine handles it locally. Vera replaces the request's credentials and drops its SAS parameters, so SAS and RBAC enforcement aren't established, and the requested `x-ms-version` is echoed back. Local observation: Vera 1.2.0-rc.3, 6 November 2026 — a hierarchical container listing that asked for Apache Arrow returned the XML fallback.
Container_ListBlobs	Implemented	Local observation: Listed the container's blobs as XML naming `hello.txt` (HTTP 200). The response's `ServiceEndpoint` is a name, not an address to send requests to.
Container_ReleaseLease	Implemented	Source inspection: The bundled storage engine handles it locally. Vera replaces the request's credentials and drops its SAS parameters, so SAS and RBAC enforcement aren't established, and the requested `x-ms-version` is echoed back.
Container_Rename	Known difference	Source inspection: The bundled storage engine has no rename operation, so the request creates the destination container and answers HTTP 201. The source isn't renamed or moved, and its blobs aren't copied: the success status doesn't mean the rename happened. Vera replaces the request's credentials and drops its SAS parameters, so SAS and RBAC enforcement aren't established, and the requested `x-ms-version` is echoed back. Local observation: Vera 1.2.0-rc.3, 6 November 2026 — a rename request, `comp=rename` with `x-ms-source-container-name`, returned HTTP 201; the source container still answered HEAD with HTTP 200, and a GET for its blob in the destination returned HTTP 404.
Container_RenewLease	Implemented	Source inspection: The bundled storage engine handles it locally. Vera replaces the request's credentials and drops its SAS parameters, so SAS and RBAC enforcement aren't established, and the requested `x-ms-version` is echoed back.
Container_Restore	Failed in testing	Source inspection: The bundled storage engine doesn't implement this operation: it answers HTTP 501 `APINotImplemented`. Local observation: Vera 1.2.0-rc.3, 6 November 2026 — this operation, sent to a newly created account and container, returned HTTP 501 `APINotImplemented`.
Container_SetAccessPolicy	Implemented	Source inspection: Stores the access policies. Reading and writing them doesn't establish that they're enforced. The bundled storage engine handles it locally. Vera replaces the request's credentials and drops its SAS parameters, so SAS and RBAC enforcement aren't established, and the requested `x-ms-version` is echoed back.
Container_SetMetadata	Implemented	Source inspection: The bundled storage engine handles it locally. Vera replaces the request's credentials and drops its SAS parameters, so SAS and RBAC enforcement aren't established, and the requested `x-ms-version` is echoed back.
Container_SubmitBatch	Implemented	Source inspection: The bundled storage engine handles it locally. Vera replaces the request's credentials and drops its SAS parameters, so SAS and RBAC enforcement aren't established, and the requested `x-ms-version` is echoed back.

PageBlob

6 of 8 implemented · 1 known difference · 2 failed in testing

Operation	Status	Notes
PageBlob_ClearPages	Implemented	Source inspection: The bundled storage engine handles it locally. Vera replaces the request's credentials and drops its SAS parameters, so SAS and RBAC enforcement aren't established, and the requested `x-ms-version` is echoed back.
PageBlob_CopyIncremental	Failed in testing	Source inspection: The bundled storage engine doesn't implement this operation: it answers HTTP 501 `APINotImplemented`. Local observation: Vera 1.2.0-rc.3, 6 November 2026 — this operation, sent to a newly created account and container, returned HTTP 501 `APINotImplemented`.
PageBlob_GetPageRanges	Implemented	Source inspection: The bundled storage engine handles it locally. Vera replaces the request's credentials and drops its SAS parameters, so SAS and RBAC enforcement aren't established, and the requested `x-ms-version` is echoed back.
PageBlob_GetPageRangesDiff	Known difference	Source inspection: A `prevsnapshot` request is answered as an ordinary page range list: it returns every written range, not only the ranges changed since the snapshot. The bundled storage engine's own diff operation isn't implemented either. Vera replaces the request's credentials and drops its SAS parameters, so SAS and RBAC enforcement aren't established, and the requested `x-ms-version` is echoed back. Local observation: Vera 1.2.0-rc.3, 6 November 2026 — after writing bytes 0–511 of a page blob, taking a snapshot and writing bytes 1024–1535, `comp=pagelist&prevsnapshot=<snapshot>` returned HTTP 200 with both ranges.
PageBlob_Resize	Implemented	Source inspection: The bundled storage engine handles it locally. Vera replaces the request's credentials and drops its SAS parameters, so SAS and RBAC enforcement aren't established, and the requested `x-ms-version` is echoed back.
PageBlob_SetSequenceNumber	Implemented	Source inspection: The bundled storage engine handles it locally. Vera replaces the request's credentials and drops its SAS parameters, so SAS and RBAC enforcement aren't established, and the requested `x-ms-version` is echoed back.
PageBlob_UploadPages	Implemented	Source inspection: The bundled storage engine handles it locally. Vera replaces the request's credentials and drops its SAS parameters, so SAS and RBAC enforcement aren't established, and the requested `x-ms-version` is echoed back.
PageBlob_UploadPagesFromUrl	Failed in testing	Source inspection: The bundled storage engine doesn't implement this operation: it answers HTTP 501 `APINotImplemented`. Local observation: Vera 1.2.0-rc.3, 6 November 2026 — this operation, sent to a newly created account and container, returned HTTP 501 `APINotImplemented`.

Service

8 of 8 implemented

Operation	Status	Notes
Service_FindBlobsByTags	Implemented	Source inspection: The bundled storage engine handles it locally. Vera replaces the request's credentials and drops its SAS parameters, so SAS and RBAC enforcement aren't established, and the requested `x-ms-version` is echoed back.
Service_GetAccountInfo	Implemented	Source inspection: The bundled storage engine handles it locally. Vera replaces the request's credentials and drops its SAS parameters, so SAS and RBAC enforcement aren't established, and the requested `x-ms-version` is echoed back.
Service_GetProperties	Implemented	Source inspection: The bundled storage engine handles it locally. Vera replaces the request's credentials and drops its SAS parameters, so SAS and RBAC enforcement aren't established, and the requested `x-ms-version` is echoed back.
Service_GetStatistics	Implemented	Source inspection: Returns local service statistics; they don't describe Azure geo-replication. The bundled storage engine handles it locally. Vera replaces the request's credentials and drops its SAS parameters, so SAS and RBAC enforcement aren't established, and the requested `x-ms-version` is echoed back.
Service_GetUserDelegationKey	Implemented	Source inspection: The bundled storage engine handles it locally. Vera replaces the request's credentials and drops its SAS parameters, so SAS and RBAC enforcement aren't established, and the requested `x-ms-version` is echoed back.
Service_ListContainers	Implemented	Source inspection: The bundled storage engine handles it locally. Vera replaces the request's credentials and drops its SAS parameters, so SAS and RBAC enforcement aren't established, and the requested `x-ms-version` is echoed back.
Service_SetProperties	Implemented	Source inspection: The bundled storage engine handles it locally. Vera replaces the request's credentials and drops its SAS parameters, so SAS and RBAC enforcement aren't established, and the requested `x-ms-version` is echoed back.
Service_SubmitBatch	Implemented	Source inspection: The bundled storage engine handles it locally. Vera replaces the request's credentials and drops its SAS parameters, so SAS and RBAC enforcement aren't established, and the requested `x-ms-version` is echoed back.

Data Lake 2026-06-06Plan: Pro

19 of 19 implemented

Version 2026-06-06, from the Azure REST API specifications at commit 21bbf1b.

FileSystem

6 of 6 implemented

Operation	Status	Notes
FileSystem_Create	Implemented	Local observation: Created a file system (HTTP 201).
FileSystem_Delete	Implemented	Local observation: Deleted the file system (HTTP 202).
FileSystem_GetProperties	Implemented	Source inspection: Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
FileSystem_ListBlobHierarchySegment	Implemented	Source inspection: Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
FileSystem_ListPaths	Implemented	Local observation: Listed the file system recursively (HTTP 200) as an XML `PathList`, in which `hello.txt` has a content length of 10. Whether Azure's SDKs read this XML wasn't tested.
FileSystem_SetProperties	Implemented	Source inspection: Files and Data Lake are implemented over REST; SMB and NFS weren't verified.

Path

12 of 12 implemented

Operation	Status	Notes
Path_AppendData	Implemented	Local observation: Appended 10 bytes at position 0 (HTTP 202).
Path_Create	Implemented	Local observation: Created a file (HTTP 201).
Path_Delete	Implemented	Local observation: Deleted the file (HTTP 200).
Path_FlushData	Implemented	Local observation: Flushed the 10 appended bytes at position 10 (HTTP 200). Flushing at position 100 answered HTTP 400 `InvalidFlushPosition`.
Path_GetProperties	Implemented	Source inspection: Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
Path_Lease	Implemented	Source inspection: Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
Path_Read	Implemented	Local observation: Returned the flushed bytes, `hello vera` (HTTP 200).
Path_SetAccessControl	Implemented	Source inspection: Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
Path_SetAccessControlRecursive	Implemented	Source inspection: Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
Path_SetExpiry	Implemented	Source inspection: Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
Path_Undelete	Implemented	Source inspection: Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
Path_Update	Implemented	Source inspection: Updates a path's properties with `action=setProperties`. Requests with `action=append`, `action=flush` or an access-control action go to those dedicated operations instead, which can answer with their own status codes. Files and Data Lake are implemented over REST; SMB and NFS weren't verified.

Service

1 of 1 implemented

Operation	Status	Notes
Service_ListFileSystems	Implemented	Source inspection: Files and Data Lake are implemented over REST; SMB and NFS weren't verified.

Files 2026-12-06Plan: Free

52 of 52 implemented · 1 known difference

Version 2026-12-06, from the Azure REST API specifications at commit 21bbf1b.

Operation	Status	Notes
Directory_Create	Implemented	Source inspection: Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
Directory_Delete	Implemented	Source inspection: Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
Directory_ForceCloseHandles	Implemented	Source inspection: Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
Directory_GetProperties	Implemented	Source inspection: Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
Directory_ListFilesAndDirectoriesSegment	Implemented	Source inspection: Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
Directory_ListHandles	Implemented	Source inspection: Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
Directory_Rename	Implemented	Source inspection: Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
Directory_SetMetadata	Implemented	Source inspection: Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
Directory_SetProperties	Implemented	Source inspection: Files and Data Lake are implemented over REST; SMB and NFS weren't verified.

File

22 of 22 implemented · 1 known difference

Operation	Status	Notes
File_AbortCopy	Implemented	Source inspection: Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
File_AcquireLease	Implemented	Source inspection: Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
File_BreakLease	Implemented	Source inspection: Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
File_ChangeLease	Implemented	Source inspection: Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
File_Create	Implemented	Local observation: Created a 10-byte file (HTTP 201).
File_CreateHardLink	Implemented	Source inspection: Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
File_CreateSymbolicLink	Implemented	Source inspection: Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
File_Delete	Implemented	Local observation: Deleted the file (HTTP 202).
File_Download	Implemented	Local observation: Returned the file's 10 bytes, `hello vera` (HTTP 200).
File_ForceCloseHandles	Implemented	Source inspection: Lists or closes a file's handles. Files and directories share this URL, and the request is routed to the file operation by the stored item's type. Files and Data Lake are implemented over REST; SMB and NFS weren't verified. Local observation: Vera 1.2.0-rc.3, 6 November 2026 — list-handles and force-close-handles requests on a file each returned HTTP 200.
File_GetProperties	Implemented	Source inspection: Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
File_GetRangeList	Implemented	Source inspection: Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
File_GetSymbolicLink	Implemented	Source inspection: Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
File_ListAllRanges	Known difference	Source inspection: Requests are answered by `File_GetRangeList`, which returns every range in one response: `maxresults` and continuation markers are ignored. Files and Data Lake are implemented over REST; SMB and NFS weren't verified. Local observation: Vera 1.2.0-rc.3, 6 November 2026 — after writing ranges 0–1 and 4–5, `comp=rangelist&maxresults=1` returned both ranges and no continuation marker.
File_ListHandles	Implemented	Source inspection: Lists or closes a file's handles. Files and directories share this URL, and the request is routed to the file operation by the stored item's type. Files and Data Lake are implemented over REST; SMB and NFS weren't verified. Local observation: Vera 1.2.0-rc.3, 6 November 2026 — list-handles and force-close-handles requests on a file each returned HTTP 200.
File_ReleaseLease	Implemented	Source inspection: Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
File_Rename	Implemented	Source inspection: Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
File_SetHttpHeaders	Implemented	Source inspection: Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
File_SetMetadata	Implemented	Source inspection: Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
File_StartCopy	Implemented	Source inspection: Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
File_UploadRange	Implemented	Local observation: Wrote bytes 0 to 9 of the file (HTTP 201). A range outside the 10-byte file, bytes 20 to 22, answered HTTP 416 `InvalidRange`.
File_UploadRangeFromUrl	Implemented	Source inspection: Files and Data Lake are implemented over REST; SMB and NFS weren't verified.

Service

4 of 4 implemented

Operation	Status	Notes
Service_GetProperties	Implemented	Source inspection: Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
Service_GetUserDelegationKey	Implemented	Source inspection: Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
Service_ListSharesSegment	Implemented	Source inspection: Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
Service_SetProperties	Implemented	Source inspection: Files and Data Lake are implemented over REST; SMB and NFS weren't verified.

17 of 17 implemented

Operation	Status	Notes
Share_AcquireLease	Implemented	Source inspection: Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
Share_BreakLease	Implemented	Source inspection: Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
Share_ChangeLease	Implemented	Source inspection: Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
Share_Create	Implemented	Local observation: Created a share through the REST API (HTTP 201). Mounting a share over SMB or NFS wasn't tested.
Share_CreatePermission	Implemented	Source inspection: Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
Share_CreateSnapshot	Implemented	Source inspection: Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
Share_Delete	Implemented	Local observation: Deleted the share (HTTP 202).
Share_GetAccessPolicy	Implemented	Source inspection: Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
Share_GetPermission	Implemented	Source inspection: Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
Share_GetProperties	Implemented	Source inspection: Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
Share_GetStatistics	Implemented	Source inspection: Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
Share_ReleaseLease	Implemented	Source inspection: Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
Share_RenewLease	Implemented	Source inspection: Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
Share_Restore	Implemented	Source inspection: Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
Share_SetAccessPolicy	Implemented	Source inspection: Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
Share_SetMetadata	Implemented	Source inspection: Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
Share_SetProperties	Implemented	Source inspection: Files and Data Lake are implemented over REST; SMB and NFS weren't verified.

Queue 2026-04-06Plan: Free

16 of 17 implemented · 1 failed in testing

Version 2026-04-06, from the Azure REST API specifications at commit 21bbf1b.

Queue

12 of 12 implemented

Operation	Status	Notes
Queue_Clear	Implemented	Source inspection: The bundled storage engine handles it locally. Vera replaces the request's credentials and drops its SAS parameters, so SAS and RBAC enforcement aren't established, and the requested `x-ms-version` is echoed back.
Queue_Create	Implemented	Local observation: Created a queue (HTTP 201).
Queue_Delete	Implemented	Local observation: Deleted the queue (HTTP 204).
Queue_DeleteMessage	Implemented	Source inspection: The bundled storage engine handles it locally. Vera replaces the request's credentials and drops its SAS parameters, so SAS and RBAC enforcement aren't established, and the requested `x-ms-version` is echoed back.
Queue_GetAccessPolicy	Implemented	Source inspection: Returns the stored access policies. Reading and writing them doesn't establish that they're enforced. The bundled storage engine handles it locally. Vera replaces the request's credentials and drops its SAS parameters, so SAS and RBAC enforcement aren't established, and the requested `x-ms-version` is echoed back.
Queue_GetProperties	Implemented	Source inspection: The bundled storage engine handles it locally. Vera replaces the request's credentials and drops its SAS parameters, so SAS and RBAC enforcement aren't established, and the requested `x-ms-version` is echoed back.
Queue_PeekMessages	Implemented	Source inspection: The bundled storage engine handles it locally. Vera replaces the request's credentials and drops its SAS parameters, so SAS and RBAC enforcement aren't established, and the requested `x-ms-version` is echoed back.
Queue_ReceiveMessages	Implemented	Local observation: Received one message as XML with its ID, pop receipt and base64 text (HTTP 200). Visibility timing beyond this receive wasn't tested.
Queue_SendMessage	Implemented	Local observation: Sent a message with base64 text (HTTP 201).
Queue_SetAccessPolicy	Implemented	Source inspection: Stores the access policies. Reading and writing them doesn't establish that they're enforced. The bundled storage engine handles it locally. Vera replaces the request's credentials and drops its SAS parameters, so SAS and RBAC enforcement aren't established, and the requested `x-ms-version` is echoed back.
Queue_SetMetadata	Implemented	Source inspection: The bundled storage engine handles it locally. Vera replaces the request's credentials and drops its SAS parameters, so SAS and RBAC enforcement aren't established, and the requested `x-ms-version` is echoed back.
Queue_UpdateMessage	Implemented	Source inspection: The bundled storage engine handles it locally. Vera replaces the request's credentials and drops its SAS parameters, so SAS and RBAC enforcement aren't established, and the requested `x-ms-version` is echoed back.

Service

4 of 5 implemented · 1 failed in testing

Operation	Status	Notes
Service_GetProperties	Implemented	Source inspection: The bundled storage engine handles it locally. Vera replaces the request's credentials and drops its SAS parameters, so SAS and RBAC enforcement aren't established, and the requested `x-ms-version` is echoed back.
Service_GetQueues	Implemented	Source inspection: The bundled storage engine handles it locally. Vera replaces the request's credentials and drops its SAS parameters, so SAS and RBAC enforcement aren't established, and the requested `x-ms-version` is echoed back.
Service_GetStatistics	Implemented	Source inspection: Returns local service statistics; they don't describe Azure geo-replication. The bundled storage engine handles it locally. Vera replaces the request's credentials and drops its SAS parameters, so SAS and RBAC enforcement aren't established, and the requested `x-ms-version` is echoed back.
Service_GetUserDelegationKey	Failed in testing	Source inspection: Not available: the bundled storage engine has no Queue user delegation key operation. Blob's user delegation key is a separate, implemented operation. Local observation: Vera 1.2.0-rc.3, 6 November 2026 — a Queue user delegation key request returned HTTP 400.
Service_SetProperties	Implemented	Source inspection: The bundled storage engine handles it locally. Vera replaces the request's credentials and drops its SAS parameters, so SAS and RBAC enforcement aren't established, and the requested `x-ms-version` is echoed back.

Storage accounts 2026-09-01Plan: Free

139 of 139 implemented · 3 known differences

Version 2026-09-01, from the Azure REST API specifications at commit 21bbf1b.

AdvancedPlatformMetrics

4 of 4 implemented

Operation	Status	Notes
AdvancedPlatformMetrics_CreateOrUpdate	Implemented	Source inspection: Local account settings; access policies, network rules, quotas and failover aren't established as enforced. Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
AdvancedPlatformMetrics_Delete	Implemented	Source inspection: Local account settings; access policies, network rules, quotas and failover aren't established as enforced. Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
AdvancedPlatformMetrics_Get	Implemented	Source inspection: Local account settings; access policies, network rules, quotas and failover aren't established as enforced. Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
AdvancedPlatformMetrics_List	Implemented	Source inspection: Local account settings; access policies, network rules, quotas and failover aren't established as enforced. Files and Data Lake are implemented over REST; SMB and NFS weren't verified.

BlobAccessPointConfigurations

6 of 6 implemented · 1 known difference

Operation	Status	Notes
BlobAccessPointConfigurations_Create	Implemented	Source inspection: Local account settings; access policies, network rules, quotas and failover aren't established as enforced. Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
BlobAccessPointConfigurations_Delete	Implemented	Source inspection: Local account settings; access policies, network rules, quotas and failover aren't established as enforced. Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
BlobAccessPointConfigurations_Get	Implemented	Source inspection: Local account settings; access policies, network rules, quotas and failover aren't established as enforced. Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
BlobAccessPointConfigurations_ListByStorageAccount	Implemented	Source inspection: Local account settings; access policies, network rules, quotas and failover aren't established as enforced. Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
BlobAccessPointConfigurations_TestExistingConnection	Known difference	Source inspection: Returns local failure diagnostics without connecting to the external service, so no S3 or Azure network connection is shown. Local account settings; access policies, network rules, quotas and failover aren't established as enforced.
BlobAccessPointConfigurations_Update	Implemented	Source inspection: Local account settings; access policies, network rules, quotas and failover aren't established as enforced. Files and Data Lake are implemented over REST; SMB and NFS weren't verified.

BlobAccessPointConnectionTests

1 of 1 implemented · 1 known difference

Operation	Status	Notes
BlobAccessPointConnectionTests_TestProposedConnection	Known difference	Source inspection: Returns local failure diagnostics without connecting to the external service, so no S3 or Azure network connection is shown. Local account settings; access policies, network rules, quotas and failover aren't established as enforced.

BlobContainers

14 of 14 implemented

Operation	Status	Notes
BlobContainers_ClearLegalHold	Implemented	Source inspection: Local account settings; access policies, network rules, quotas and failover aren't established as enforced. Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
BlobContainers_Create	Implemented	Source inspection: Local account settings; access policies, network rules, quotas and failover aren't established as enforced. Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
BlobContainers_CreateOrUpdateImmutabilityPolicy	Implemented	Source inspection: Local account settings; access policies, network rules, quotas and failover aren't established as enforced. Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
BlobContainers_Delete	Implemented	Source inspection: Local account settings; access policies, network rules, quotas and failover aren't established as enforced. Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
BlobContainers_DeleteImmutabilityPolicy	Implemented	Source inspection: Local account settings; access policies, network rules, quotas and failover aren't established as enforced. Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
BlobContainers_ExtendImmutabilityPolicy	Implemented	Source inspection: Local account settings; access policies, network rules, quotas and failover aren't established as enforced. Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
BlobContainers_Get	Implemented	Source inspection: Local account settings; access policies, network rules, quotas and failover aren't established as enforced. Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
BlobContainers_GetImmutabilityPolicy	Implemented	Source inspection: Local account settings; access policies, network rules, quotas and failover aren't established as enforced. Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
BlobContainers_Lease	Implemented	Source inspection: Local account settings; access policies, network rules, quotas and failover aren't established as enforced. Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
BlobContainers_List	Implemented	Source inspection: Local account settings; access policies, network rules, quotas and failover aren't established as enforced. Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
BlobContainers_LockImmutabilityPolicy	Implemented	Source inspection: Local account settings; access policies, network rules, quotas and failover aren't established as enforced. Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
BlobContainers_ObjectLevelWorm	Implemented	Source inspection: Local account settings; access policies, network rules, quotas and failover aren't established as enforced. Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
BlobContainers_SetLegalHold	Implemented	Source inspection: Local account settings; access policies, network rules, quotas and failover aren't established as enforced. Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
BlobContainers_Update	Implemented	Source inspection: Local account settings; access policies, network rules, quotas and failover aren't established as enforced. Files and Data Lake are implemented over REST; SMB and NFS weren't verified.

BlobInventoryPolicies

4 of 4 implemented

Operation	Status	Notes
BlobInventoryPolicies_CreateOrUpdate	Implemented	Source inspection: Local account settings; access policies, network rules, quotas and failover aren't established as enforced. Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
BlobInventoryPolicies_Delete	Implemented	Source inspection: Local account settings; access policies, network rules, quotas and failover aren't established as enforced. Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
BlobInventoryPolicies_Get	Implemented	Source inspection: Local account settings; access policies, network rules, quotas and failover aren't established as enforced. Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
BlobInventoryPolicies_List	Implemented	Source inspection: Local account settings; access policies, network rules, quotas and failover aren't established as enforced. Files and Data Lake are implemented over REST; SMB and NFS weren't verified.

BlobServices

3 of 3 implemented

Operation	Status	Notes
BlobServices_GetServiceProperties	Implemented	Source inspection: Local account settings; access policies, network rules, quotas and failover aren't established as enforced. Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
BlobServices_List	Implemented	Source inspection: Local account settings; access policies, network rules, quotas and failover aren't established as enforced. Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
BlobServices_SetServiceProperties	Implemented	Source inspection: Local account settings; access policies, network rules, quotas and failover aren't established as enforced. Files and Data Lake are implemented over REST; SMB and NFS weren't verified.

Connectors

6 of 6 implemented · 1 known difference

Operation	Status	Notes
Connectors_Create	Implemented	Source inspection: Local account settings; access policies, network rules, quotas and failover aren't established as enforced.
Connectors_Delete	Implemented	Source inspection: Local account settings; access policies, network rules, quotas and failover aren't established as enforced.
Connectors_Get	Implemented	Source inspection: Local account settings; access policies, network rules, quotas and failover aren't established as enforced.
Connectors_ListByStorageAccount	Implemented	Source inspection: Local account settings; access policies, network rules, quotas and failover aren't established as enforced.
Connectors_TestExistingConnection	Known difference	Source inspection: Returns local failure diagnostics without connecting to the external service, so no S3 or Azure network connection is shown. Local account settings; access policies, network rules, quotas and failover aren't established as enforced.
Connectors_Update	Implemented	Source inspection: Local account settings; access policies, network rules, quotas and failover aren't established as enforced.

ContextCacheContainers

5 of 5 implemented

Operation	Status	Notes
ContextCacheContainers_CreateOrUpdate	Implemented	Source inspection: Local account settings; access policies, network rules, quotas and failover aren't established as enforced. Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
ContextCacheContainers_Delete	Implemented	Source inspection: Local account settings; access policies, network rules, quotas and failover aren't established as enforced. Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
ContextCacheContainers_Get	Implemented	Source inspection: Local account settings; access policies, network rules, quotas and failover aren't established as enforced. Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
ContextCacheContainers_ListByContextCache	Implemented	Source inspection: Local account settings; access policies, network rules, quotas and failover aren't established as enforced. Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
ContextCacheContainers_Update	Implemented	Source inspection: Local account settings; access policies, network rules, quotas and failover aren't established as enforced. Files and Data Lake are implemented over REST; SMB and NFS weren't verified.

ContextCaches

7 of 7 implemented

Operation	Status	Notes
ContextCaches_CheckNameAvailability	Implemented	Source inspection: Local account settings; access policies, network rules, quotas and failover aren't established as enforced. Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
ContextCaches_CreateOrUpdate	Implemented	Source inspection: Local account settings; access policies, network rules, quotas and failover aren't established as enforced. Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
ContextCaches_Delete	Implemented	Source inspection: Local account settings; access policies, network rules, quotas and failover aren't established as enforced. Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
ContextCaches_Get	Implemented	Source inspection: Local account settings; access policies, network rules, quotas and failover aren't established as enforced. Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
ContextCaches_ListByResourceGroup	Implemented	Source inspection: Local account settings; access policies, network rules, quotas and failover aren't established as enforced. Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
ContextCaches_ListBySubscription	Implemented	Source inspection: Local account settings; access policies, network rules, quotas and failover aren't established as enforced. Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
ContextCaches_Update	Implemented	Source inspection: Local account settings; access policies, network rules, quotas and failover aren't established as enforced. Files and Data Lake are implemented over REST; SMB and NFS weren't verified.

DataShares

5 of 5 implemented

Operation	Status	Notes
DataShares_Create	Implemented	Source inspection: Local account settings; access policies, network rules, quotas and failover aren't established as enforced. Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
DataShares_Delete	Implemented	Source inspection: Local account settings; access policies, network rules, quotas and failover aren't established as enforced. Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
DataShares_Get	Implemented	Source inspection: Local account settings; access policies, network rules, quotas and failover aren't established as enforced. Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
DataShares_ListByStorageAccount	Implemented	Source inspection: Local account settings; access policies, network rules, quotas and failover aren't established as enforced. Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
DataShares_Update	Implemented	Source inspection: Local account settings; access policies, network rules, quotas and failover aren't established as enforced. Files and Data Lake are implemented over REST; SMB and NFS weren't verified.

DeletedAccounts

2 of 2 implemented

Operation	Status	Notes
DeletedAccounts_Get	Implemented	Source inspection: Local account settings; access policies, network rules, quotas and failover aren't established as enforced. Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
DeletedAccounts_List	Implemented	Source inspection: Local account settings; access policies, network rules, quotas and failover aren't established as enforced. Files and Data Lake are implemented over REST; SMB and NFS weren't verified.

EncryptionScopes

4 of 4 implemented

Operation	Status	Notes
EncryptionScopes_Get	Implemented	Source inspection: Local account settings; access policies, network rules, quotas and failover aren't established as enforced. Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
EncryptionScopes_List	Implemented	Source inspection: Local account settings; access policies, network rules, quotas and failover aren't established as enforced. Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
EncryptionScopes_Patch	Implemented	Source inspection: Local account settings; access policies, network rules, quotas and failover aren't established as enforced. Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
EncryptionScopes_Put	Implemented	Source inspection: Local account settings; access policies, network rules, quotas and failover aren't established as enforced. Files and Data Lake are implemented over REST; SMB and NFS weren't verified.

FileServices

5 of 5 implemented

Operation	Status	Notes
FileServices_GetServiceProperties	Implemented	Source inspection: Local account settings; access policies, network rules, quotas and failover aren't established as enforced. Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
FileServices_GetServiceUsage	Implemented	Source inspection: Local account settings; access policies, network rules, quotas and failover aren't established as enforced. Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
FileServices_List	Implemented	Source inspection: Local account settings; access policies, network rules, quotas and failover aren't established as enforced. Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
FileServices_ListServiceUsages	Implemented	Source inspection: Local account settings; access policies, network rules, quotas and failover aren't established as enforced. Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
FileServices_SetServiceProperties	Implemented	Source inspection: Local account settings; access policies, network rules, quotas and failover aren't established as enforced. Files and Data Lake are implemented over REST; SMB and NFS weren't verified.

FileShares

7 of 7 implemented

Operation	Status	Notes
FileShares_Create	Implemented	Source inspection: Local account settings; access policies, network rules, quotas and failover aren't established as enforced. Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
FileShares_Delete	Implemented	Source inspection: Local account settings; access policies, network rules, quotas and failover aren't established as enforced. Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
FileShares_Get	Implemented	Source inspection: Local account settings; access policies, network rules, quotas and failover aren't established as enforced. Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
FileShares_Lease	Implemented	Source inspection: Local account settings; access policies, network rules, quotas and failover aren't established as enforced. Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
FileShares_List	Implemented	Source inspection: Local account settings; access policies, network rules, quotas and failover aren't established as enforced. Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
FileShares_Restore	Implemented	Source inspection: Local account settings; access policies, network rules, quotas and failover aren't established as enforced. Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
FileShares_Update	Implemented	Source inspection: Local account settings; access policies, network rules, quotas and failover aren't established as enforced. Files and Data Lake are implemented over REST; SMB and NFS weren't verified.

LocalUsers

6 of 6 implemented

Operation	Status	Notes
LocalUsers_CreateOrUpdate	Implemented	Source inspection: Local account settings; access policies, network rules, quotas and failover aren't established as enforced. Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
LocalUsers_Delete	Implemented	Source inspection: Local account settings; access policies, network rules, quotas and failover aren't established as enforced. Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
LocalUsers_Get	Implemented	Source inspection: Local account settings; access policies, network rules, quotas and failover aren't established as enforced. Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
LocalUsers_List	Implemented	Source inspection: Local account settings; access policies, network rules, quotas and failover aren't established as enforced. Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
LocalUsers_ListKeys	Implemented	Source inspection: Local account settings; access policies, network rules, quotas and failover aren't established as enforced. Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
LocalUsers_RegeneratePassword	Implemented	Source inspection: Local account settings; access policies, network rules, quotas and failover aren't established as enforced. Files and Data Lake are implemented over REST; SMB and NFS weren't verified.

ManagementPolicies

3 of 3 implemented

Operation	Status	Notes
ManagementPolicies_CreateOrUpdate	Implemented	Source inspection: Local account settings; access policies, network rules, quotas and failover aren't established as enforced. Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
ManagementPolicies_Delete	Implemented	Source inspection: Local account settings; access policies, network rules, quotas and failover aren't established as enforced. Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
ManagementPolicies_Get	Implemented	Source inspection: Local account settings; access policies, network rules, quotas and failover aren't established as enforced. Files and Data Lake are implemented over REST; SMB and NFS weren't verified.

NetworkSecurityPerimeterConfigurations

3 of 3 implemented

Operation	Status	Notes
NetworkSecurityPerimeterConfigurations_Get	Implemented	Source inspection: Local account settings; access policies, network rules, quotas and failover aren't established as enforced. Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
NetworkSecurityPerimeterConfigurations_List	Implemented	Source inspection: Local account settings; access policies, network rules, quotas and failover aren't established as enforced. Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
NetworkSecurityPerimeterConfigurations_Reconcile	Implemented	Source inspection: Local account settings; access policies, network rules, quotas and failover aren't established as enforced. Files and Data Lake are implemented over REST; SMB and NFS weren't verified.

ObjectReplicationPolicies

4 of 4 implemented

Operation	Status	Notes
ObjectReplicationPolicies_CreateOrUpdate	Implemented	Source inspection: Local account settings; access policies, network rules, quotas and failover aren't established as enforced. Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
ObjectReplicationPolicies_Delete	Implemented	Source inspection: Local account settings; access policies, network rules, quotas and failover aren't established as enforced. Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
ObjectReplicationPolicies_Get	Implemented	Source inspection: Local account settings; access policies, network rules, quotas and failover aren't established as enforced. Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
ObjectReplicationPolicies_List	Implemented	Source inspection: Local account settings; access policies, network rules, quotas and failover aren't established as enforced. Files and Data Lake are implemented over REST; SMB and NFS weren't verified.

Operations

1 of 1 implemented

Operation	Status	Notes
Operations_List	Implemented	Source inspection: Local account settings; access policies, network rules, quotas and failover aren't established as enforced. Files and Data Lake are implemented over REST; SMB and NFS weren't verified.

PrivateEndpointConnections

4 of 4 implemented

Operation	Status	Notes
PrivateEndpointConnections_Delete	Implemented	Source inspection: Local account settings; access policies, network rules, quotas and failover aren't established as enforced. Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
PrivateEndpointConnections_Get	Implemented	Source inspection: Local account settings; access policies, network rules, quotas and failover aren't established as enforced. Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
PrivateEndpointConnections_List	Implemented	Source inspection: Local account settings; access policies, network rules, quotas and failover aren't established as enforced. Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
PrivateEndpointConnections_Put	Implemented	Source inspection: Local account settings; access policies, network rules, quotas and failover aren't established as enforced. Files and Data Lake are implemented over REST; SMB and NFS weren't verified.

PrivateLinkResources

1 of 1 implemented

Operation	Status	Notes
PrivateLinkResources_ListByStorageAccount	Implemented	Source inspection: Local account settings; access policies, network rules, quotas and failover aren't established as enforced. Files and Data Lake are implemented over REST; SMB and NFS weren't verified.

Queue

5 of 5 implemented

Operation	Status	Notes
Queue_Create	Implemented	Source inspection: Local account settings; access policies, network rules, quotas and failover aren't established as enforced. Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
Queue_Delete	Implemented	Source inspection: Local account settings; access policies, network rules, quotas and failover aren't established as enforced. Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
Queue_Get	Implemented	Source inspection: Local account settings; access policies, network rules, quotas and failover aren't established as enforced. Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
Queue_List	Implemented	Source inspection: Local account settings; access policies, network rules, quotas and failover aren't established as enforced. Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
Queue_Update	Implemented	Source inspection: Local account settings; access policies, network rules, quotas and failover aren't established as enforced. Files and Data Lake are implemented over REST; SMB and NFS weren't verified.

QueueServices

3 of 3 implemented

Operation	Status	Notes
QueueServices_GetServiceProperties	Implemented	Source inspection: Local account settings; access policies, network rules, quotas and failover aren't established as enforced. Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
QueueServices_List	Implemented	Source inspection: Local account settings; access policies, network rules, quotas and failover aren't established as enforced. Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
QueueServices_SetServiceProperties	Implemented	Source inspection: Local account settings; access policies, network rules, quotas and failover aren't established as enforced. Files and Data Lake are implemented over REST; SMB and NFS weren't verified.

Skus

1 of 1 implemented

Operation	Status	Notes
Skus_List	Implemented	Source inspection: Local account settings; access policies, network rules, quotas and failover aren't established as enforced. Files and Data Lake are implemented over REST; SMB and NFS weren't verified.

StorageAccounts

18 of 18 implemented

Operation	Status	Notes
StorageAccounts_AbortHierarchicalNamespaceMigration	Implemented	Source inspection: Local account settings; access policies, network rules, quotas and failover aren't established as enforced. Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
StorageAccounts_CheckNameAvailability	Implemented	Source inspection: Local account settings; access policies, network rules, quotas and failover aren't established as enforced. Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
StorageAccounts_Create	Implemented	Local observation: Created a `StorageV2` account with `Standard_LRS` (HTTP 202), readable once its operation had finished.
StorageAccounts_CustomerInitiatedMigration	Implemented	Source inspection: Local account settings; access policies, network rules, quotas and failover aren't established as enforced. Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
StorageAccounts_Delete	Implemented	Local observation: Deleted the account (HTTP 200); a GET then answered HTTP 404.
StorageAccounts_Failover	Implemented	Source inspection: Local account settings; access policies, network rules, quotas and failover aren't established as enforced. Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
StorageAccounts_GetCustomerInitiatedMigration	Implemented	Source inspection: Local account settings; access policies, network rules, quotas and failover aren't established as enforced. Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
StorageAccounts_GetProperties	Implemented	Local observation: Returned the account with `name` `azdatastore` and `kind` `StorageV2` (HTTP 200). A missing account, and the account after deletion, answered HTTP 404.
StorageAccounts_HierarchicalNamespaceMigration	Implemented	Source inspection: Local account settings; access policies, network rules, quotas and failover aren't established as enforced. Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
StorageAccounts_List	Implemented	Source inspection: Local account settings; access policies, network rules, quotas and failover aren't established as enforced. Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
StorageAccounts_ListAccountSAS	Implemented	Source inspection: Local account settings; access policies, network rules, quotas and failover aren't established as enforced. Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
StorageAccounts_ListByResourceGroup	Implemented	Local observation: Listed the resource group's accounts (HTTP 200).
StorageAccounts_ListKeys	Implemented	Source inspection: Local account settings; access policies, network rules, quotas and failover aren't established as enforced. Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
StorageAccounts_ListServiceSAS	Implemented	Source inspection: Local account settings; access policies, network rules, quotas and failover aren't established as enforced. Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
StorageAccounts_RegenerateKey	Implemented	Source inspection: Local account settings; access policies, network rules, quotas and failover aren't established as enforced. Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
StorageAccounts_RestoreBlobRanges	Implemented	Source inspection: Local account settings; access policies, network rules, quotas and failover aren't established as enforced. Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
StorageAccounts_RevokeUserDelegationKeys	Implemented	Source inspection: Local account settings; access policies, network rules, quotas and failover aren't established as enforced. Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
StorageAccounts_Update	Implemented	Source inspection: Local account settings; access policies, network rules, quotas and failover aren't established as enforced. Files and Data Lake are implemented over REST; SMB and NFS weren't verified.

StorageTaskAssignmentInstancesReport

1 of 1 implemented

Operation	Status	Notes
StorageTaskAssignmentInstancesReport_List	Implemented	Source inspection: Lists task run reports kept locally. A report exists only for a recorded task run: provisioning an assignment doesn't run the task. Local account settings; access policies, network rules, quotas and failover aren't established as enforced.

StorageTaskAssignments

6 of 6 implemented

Operation	Status	Notes
StorageTaskAssignments_Create	Implemented	Source inspection: Manages task assignments as local records. Provisioning an assignment doesn't run the task, and a report exists only for a recorded task run. Local account settings; access policies, network rules, quotas and failover aren't established as enforced.
StorageTaskAssignments_Delete	Implemented	Source inspection: Manages task assignments as local records. Provisioning an assignment doesn't run the task, and a report exists only for a recorded task run. Local account settings; access policies, network rules, quotas and failover aren't established as enforced.
StorageTaskAssignments_Get	Implemented	Source inspection: Manages task assignments as local records. Provisioning an assignment doesn't run the task, and a report exists only for a recorded task run. Local account settings; access policies, network rules, quotas and failover aren't established as enforced.
StorageTaskAssignments_List	Implemented	Source inspection: Manages task assignments as local records. Provisioning an assignment doesn't run the task, and a report exists only for a recorded task run. Local account settings; access policies, network rules, quotas and failover aren't established as enforced.
StorageTaskAssignments_StopAssignment	Implemented	Source inspection: Manages task assignments as local records. Provisioning an assignment doesn't run the task, and a report exists only for a recorded task run. Local account settings; access policies, network rules, quotas and failover aren't established as enforced.
StorageTaskAssignments_Update	Implemented	Source inspection: Manages task assignments as local records. Provisioning an assignment doesn't run the task, and a report exists only for a recorded task run. Local account settings; access policies, network rules, quotas and failover aren't established as enforced.

StorageTaskAssignmentsInstancesReport

1 of 1 implemented

Operation	Status	Notes
StorageTaskAssignmentsInstancesReport_List	Implemented	Source inspection: Lists task run reports kept locally. A report exists only for a recorded task run: provisioning an assignment doesn't run the task. Local account settings; access policies, network rules, quotas and failover aren't established as enforced.

Table

5 of 5 implemented

Operation	Status	Notes
Table_Create	Implemented	Source inspection: Local account settings; access policies, network rules, quotas and failover aren't established as enforced. Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
Table_Delete	Implemented	Source inspection: Local account settings; access policies, network rules, quotas and failover aren't established as enforced. Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
Table_Get	Implemented	Source inspection: Local account settings; access policies, network rules, quotas and failover aren't established as enforced. Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
Table_List	Implemented	Source inspection: Local account settings; access policies, network rules, quotas and failover aren't established as enforced. Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
Table_Update	Implemented	Source inspection: Local account settings; access policies, network rules, quotas and failover aren't established as enforced. Files and Data Lake are implemented over REST; SMB and NFS weren't verified.

TableServices

3 of 3 implemented

Operation	Status	Notes
TableServices_GetServiceProperties	Implemented	Source inspection: Local account settings; access policies, network rules, quotas and failover aren't established as enforced. Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
TableServices_List	Implemented	Source inspection: Local account settings; access policies, network rules, quotas and failover aren't established as enforced. Files and Data Lake are implemented over REST; SMB and NFS weren't verified.
TableServices_SetServiceProperties	Implemented	Source inspection: Local account settings; access policies, network rules, quotas and failover aren't established as enforced. Files and Data Lake are implemented over REST; SMB and NFS weren't verified.

Usages

1 of 1 implemented

Operation	Status	Notes
Usages_ListByLocation	Implemented	Source inspection: Local account settings; access policies, network rules, quotas and failover aren't established as enforced. Files and Data Lake are implemented over REST; SMB and NFS weren't verified.

Table 2019-02-02Plan: Free

14 of 14 implemented

Version 2019-02-02, from the Azure REST API specifications at commit 21bbf1b.

Service

3 of 3 implemented

Operation	Status	Notes
Service_GetProperties	Implemented	Source inspection: The bundled storage engine handles it locally. Vera replaces the request's credentials and drops its SAS parameters, so SAS and RBAC enforcement aren't established, and the requested `x-ms-version` is echoed back.
Service_GetStatistics	Implemented	Source inspection: Returns local service statistics; they don't describe Azure geo-replication. The bundled storage engine handles it locally. Vera replaces the request's credentials and drops its SAS parameters, so SAS and RBAC enforcement aren't established, and the requested `x-ms-version` is echoed back.
Service_SetProperties	Implemented	Source inspection: The bundled storage engine handles it locally. Vera replaces the request's credentials and drops its SAS parameters, so SAS and RBAC enforcement aren't established, and the requested `x-ms-version` is echoed back.

Table

11 of 11 implemented

Operation	Status	Notes
Table_Create	Implemented	Local observation: Created a table (HTTP 201).
Table_Delete	Implemented	Local observation: Deleted the table (HTTP 204) when the request had `Accept: application/json;odata=nometadata`. Without that header it answered HTTP 415 `AtomFormatNotSupported`.
Table_DeleteEntity	Implemented	Source inspection: The bundled storage engine handles it locally. Vera replaces the request's credentials and drops its SAS parameters, so SAS and RBAC enforcement aren't established, and the requested `x-ms-version` is echoed back.
Table_GetAccessPolicy	Implemented	Source inspection: Returns the stored access policies. Reading and writing them doesn't establish that they're enforced. The bundled storage engine handles it locally. Vera replaces the request's credentials and drops its SAS parameters, so SAS and RBAC enforcement aren't established, and the requested `x-ms-version` is echoed back.
Table_InsertEntity	Implemented	Local observation: Inserted an entity (HTTP 201). Inserting the same partition and row keys again answered HTTP 409 `EntityAlreadyExists`.
Table_MergeEntity	Implemented	Source inspection: The bundled storage engine handles it locally. Vera replaces the request's credentials and drops its SAS parameters, so SAS and RBAC enforcement aren't established, and the requested `x-ms-version` is echoed back.
Table_Query	Implemented	Source inspection: The bundled storage engine handles it locally. Vera replaces the request's credentials and drops its SAS parameters, so SAS and RBAC enforcement aren't established, and the requested `x-ms-version` is echoed back.
Table_QueryEntities	Implemented	Source inspection: The bundled storage engine handles it locally. Vera replaces the request's credentials and drops its SAS parameters, so SAS and RBAC enforcement aren't established, and the requested `x-ms-version` is echoed back.
Table_QueryEntityWithPartitionAndRowKey	Implemented	Local observation: Returned the entity by its partition and row keys, with its properties and a generated `Timestamp` (HTTP 200).
Table_SetAccessPolicy	Implemented	Source inspection: Stores the access policies. Reading and writing them doesn't establish that they're enforced. The bundled storage engine handles it locally. Vera replaces the request's credentials and drops its SAS parameters, so SAS and RBAC enforcement aren't established, and the requested `x-ms-version` is echoed back.
Table_UpdateEntity	Implemented	Source inspection: The bundled storage engine handles it locally. Vera replaces the request's credentials and drops its SAS parameters, so SAS and RBAC enforcement aren't established, and the requested `x-ms-version` is echoed back.

Azure Storage

Connect

Example

Queue messages

Table entities

Files

Data Lake

Clean up

Supported features

Limitations

API coverage

Blob 2026-12-06Plan: Free

AppendBlob

Blob

BlockBlob

Container

PageBlob

Service

Data Lake 2026-06-06Plan: Pro

FileSystem

Path

Service

Files 2026-12-06Plan: Free

Directory

File

Service

Share

Queue 2026-04-06Plan: Free

Queue

Service

Storage accounts 2026-09-01Plan: Free

AdvancedPlatformMetrics

BlobAccessPointConfigurations

BlobAccessPointConnectionTests

BlobContainers

BlobInventoryPolicies

BlobServices

Connectors

ContextCacheContainers

ContextCaches

DataShares

DeletedAccounts

EncryptionScopes

FileServices

FileShares

LocalUsers

ManagementPolicies

NetworkSecurityPerimeterConfigurations

ObjectReplicationPolicies

Operations

PrivateEndpointConnections

PrivateLinkResources

Queue

QueueServices

Skus

StorageAccounts

StorageTaskAssignmentInstancesReport

StorageTaskAssignments

StorageTaskAssignmentsInstancesReport

Table

TableServices

Usages

Table 2019-02-02Plan: Free

Service

Table