Qencode + Azure

Transcode and deliver video to Azure Blob Storage — authenticate with SAS tokens, serve through Azure CDN.

Overview

What This Integration Does

Qencode integrates with Microsoft Azure Blob Storage as both a source and destination for video transcoding jobs. Pull source video from any Blob Storage container, transcode it with any Qencode feature, and write the output — HLS, DASH, MP4, thumbnails and other — back to Azure automatically. Azure's global regions, SAS token authentication, and native CDN integration make it a strong fit for enterprise video workflows already running on the Microsoft stack.

Architecture

How the Integration Works

Source

Blob container or URL

Qencode pulls your source video from an Azure Blob Storage container (or any URL).

Process

Transcode & package

Qencode transcodes, encrypts, and packages the video per your job configuration.

Deliver

Destination container

Encoded files are written directly to your destination Blob Storage container.

Serve

Via Azure CDN

Serve via Azure CDN, or any HTTP endpoint pointing to the Blob Storage container.

Getting Started

Setup Steps

  1. Create your Blob Storage container

    In the Azure Portal, create a Storage Account and add a Blob container for your video files. Set the access tier to Hot for frequently accessed content.

    This step is completed in the Azure Portal — see Azure Blob Storage documentation

  2. Generate a SAS token

    Create a Shared Access Signature (SAS) token scoped to your container with Read and Write permissions. Set an appropriate expiration window.

    Store your SAS token as an environment variable. Never commit credentials to source control.

  3. Add credentials to Qencode

    In Transcode Media, go to Third-Party Storage, then choose Microsoft Azure. Enter your Bucket Name, Host, Access Key ID, and Secret Access Key.

  4. Set destination in your transcode job

    In your API request, set the destination parameter to your Azure Blob Storage URL with the desired output path.

  5. Verify the output

    After the job completes, check your Blob Storage container for the encoded files. Qencode sends a webhook notification when writing is complete.

Implementation

Code Example

Request Example

MP4 output to Azure Blob Storage

{
  "query": {
    "source": "https://core.windows.net/my-source-container/folder/input.mov",
    "format": [
      {
        "output": "mp4",
        "destination": {
          "url": "azblob://core.windows.net/my-blob-container/folder/output.mp4",
          "key": "YOUR_ACCOUNT_KEY",
          "secret": "YOUR_ACCOUNT_SECRET"
        }
      }
    ]
  }
}

Replace placeholder credentials with your actual Azure Storage Account name and SAS token. Use environment variables in production.

For a step-by-step walkthrough, see Tutorial: Azure Blob Storage Integration

Pricing

Cost Context

Storage costs at Azure

  • Blob Storage Hot tier runs approximately $0.018/GB/month
  • For video archives accessed infrequently, Cool tier drops to $0.01/GB/month
  • Pair with Azure CDN for delivery starting at $0.081/GB for the first 10 TB
For current rates, see Azure Blob Storage pricing

Estimated total cost per hour of 1080p video

Qencode transcoding (HLS, H.264)

~$1.80


Blob Storage Hot (1 GB encoded output)

~$0.018/mo


Azure CDN delivery (100 viewers × 1 GB)

~$8.10

Estimates based on standard configurations. Actual costs vary with codec, resolution, and encoding features. See Qencode pricing

We love creating powerful solutions that are aligned with the needs of your business.

Please send us a message if you have a question or Schedule a call for a demo to discuss your integration.

Let's talk

First Name
Last Name
Company
Email
Your Message

Contact us with any questions. We'd love to help.

Los Angeles, CA - (HQ)

San Francisco, CA

New York, NY