Skip to content

Azure Storage

This section shows how to connect to an Azure Blob Storage container where SAP data is written.

Prerequisites

To connect to a Microsoft Azure Blob Storage, generate a Shared Access Signature (SAS) token for authentication, see Microsoft Documentation: Create SAS tokens for storage containers. The following SAS permissions are required to write data to the Azure container:

  • Add
  • Create
  • Write
  • Delete
  • List

Connect to Azure Blob Storage

Use the following endpoint to create a new connection to an Azure blob storage container: 

POST /v1/connections/azureblob/{name}

POST /v1/connections/azureblob/azure HTTP/1.1
Host: localhost:1337
Content-Type: application/json
Content-Length: 223

{
"Account": "my-account",
"Token": "sv=YYYY-MM-DD&ss=...%3D(1)",
"Container": "container"
}
  1. You can copy the SAS token from the Azure portal in:
    Storage accounts > [account_name] > Data storage > Containers > [container_name] > Generate SAS.
    container-sas
curl -X POST \
     -H '[Content-Type: application/json]' \
     -H '[Content-Length: 223]' \
     -d '"Account": "my-account", "Token": "sv=YYYY-MM-DD&ss=...%3D", "Container": "container"' \
     'http://localhost:1337/v1/connections/azureblob/azure'

fetch('http://localhost:1337/v1/connections/azureblob/azure', {
  "method": "POST",
  "headers": {
    "[Content-Type": "application/json]",
    "[Content-Length": "223]"
  },
  "body": JSON.stringify("Account": "my-account", "Token": "sv=YYYY-MM-DD&ss=...%3D", "Container": "container")"
});

When this endpoint is called, the Xtract Core web server tries to establish a connection to Azure before saving the connection.

Tip

The Content-Length property in the header represents the byte size of the JSON string in the request body. When using curl, the Content-Length can be determined automatically. The -v (verbose) option returns the request details, including Content-Length.

Last update: September 5, 2025