Microsoft Azure Blob Service
12 min
the microsoft azure blob service connector enables automated interactions with azure blob storage, allowing for efficient data management and operations microsoft azure blob service is a scalable cloud storage solution that allows for the storing and retrieval of large amounts of unstructured data this connector enables swimlane turbine users to automate the management of blob storage, such as creating or updating blobs with base64 encoded content, setting blob properties, and applying access controls by integrating with azure blob service, users can enhance their security workflows with efficient data storage operations, ensuring data integrity and optimizing storage management within their security automation processes limitations none to date supported versions this connector supports the latest version of the microsoft azure blob service api additional docs microsoft azure blob service api docs https //learn microsoft com/en us/rest/api/storageservices/authorize with shared key configuration prerequisites to effectively use the microsoft azure blob service connector with swimlane turbine, ensure you have the following custom authentication with the azure blob service api using these parameters storage account name the unique name of your storage account storage account key the key that provides access to your storage account api version the version of the azure blob service api you wish to use authentication methods uses custom authentication, ensure you have the following prerequisites aws credentials authentication with the following parameters storage account name the unique name of your storage account storage account key the access key that provides authentication for your storage account api version the version of the azure storage services api to use for requests capabilities this connector provides the following capabilities put blob put blob the put blob action creates a new block, page, or append blob, or updates the content of an existing block blob click here https //learn microsoft com/en us/rest/api/storageservices/put blob?tabs=microsoft entra id configurations microsoft azure blob service authentication authenticates using the microsoft azure blob service api configuration parameters parameter description type required account name the name of the storage account string required account key the key for the storage account string required api version the version of the api to use string required verify ssl verify ssl certificate boolean optional http proxy a proxy to route requests through string optional actions put blob creates or updates a blob in the specified container with provided content requires path parameters 'container' and 'blob name', and 'base64 encode' for content encoding endpoint url /{{container}}/{{blob name}} method put input argument name type required description container string required the name of the container where the blob will be stored blob name string required the name of the blob to be created or updated base64 encode string required the content to be uploaded as a blob, encoded in base64 headers object required http headers for the request x ms blob type string required the type of blob to create or update possible values are blockblob, pageblob, or appendblob content encoding string optional specifies which content encodings have been applied to the blob this value is returned to the client when the get blob operation is performed on the blob resource when this value is returned, the client can use it to decode the blob content content language string optional specifies the natural languages that are used by this resource content md5 string optional an md5 hash of the blob content this hash is used to verify the integrity of the blob during transport when this header is specified, the storage service checks the hash that has arrived against the one that was sent if the two hashes don't match, the operation fails with error code 400 (bad request) when the header is omitted in version 2012 02 12 or later, blob storage generates an md5 hash results from get blob, get blob properties, and list blobs include the md5 hash x ms content crc64 string optional a crc64 hash of the blob content this hash is used to verify the integrity of the blob during transport when this header is specified, the storage service checks the hash that has arrived against the one that was sent if the two hashes don't match, the operation fails with error code 400 (bad request) this header is supported in versions 02 02 2019 and later if both content md5 and x ms content crc64 headers are present, the request fails with a 400 (bad request) cache control string optional blob storage stores this value but doesn't use or modify it x ms blob content type string optional set the blob's content type x ms blob content encoding string optional set the blob's content encoding x ms blob content language string optional set the blob's content language x ms blob content md5 string optional set the blob's md5 hash for blockblob, this header takes precedence over content md5 when verifying the integrity of the blob during transport for pageblob and appendblob, this header directly sets the md5 hash of the blob x ms blob cache control string optional sets the blob's cache control x ms encryption scope string optional indicates the encryption scope to use to encrypt the request contents this header is supported in versions 2019 02 02 and later x ms tags string optional sets the given query string encoded tags on the blob see the remarks for additional information supported in version 2019 12 12 and later x ms blob content disposition string optional sets the blob’s content disposition header available for versions 2013 08 15 and later x ms access tier string optional the tier to be set on the blob for page blobs on a premium storage account only with version 2017 04 17 and later for a full list of page blob supported tiers, see high performance premium storage and managed disks for virtual machines (vms) x ms immutability policy until date string optional version 2020 06 12 and later specifies the retention until date to be set on the blob this is the date until which the blob can be protected from being modified or deleted follows rfc1123 format x ms immutability policy mode string optional version 2020 06 12 and later specifies the immutability policy mode to be set on the blob valid values are unlocked and locked with unlocked, users can change the policy by increasing or decreasing the retention until date with locked, these actions are prohibited x ms legal hold string optional version 2020 06 12 and later specifies whether a legal hold is set on the blob valid values are true and false when set to true, the blob cannot be deleted or modified until the legal hold is cleared x ms expiry option string optional version 2023 08 03 and later specifies the expiration date option for the request for more information, see expiryoption this header is valid for accounts with hierarchical namespace enabled x ms expiry time string optional version 2023 08 03 and later specifies the time when the blob is set to expire the format for expiration date varies according to x ms expiry option for more information, see expiryoption this header is valid for accounts with hierarchical namespace enabled stringtosign object optional parameter for put blob output parameter type description status number status value message string response message example \[ { "status" 201, "message" "blob uploaded successfully" } ]