Roboflow + Azure Blob Storage
Run an RF-DETR model over every image and video in an Azure Blob Storage container with Roboflow Batch Processing, and get the predictions back as JSONL or CSV.
How to connect Azure Blob Storage to Roboflow
6 stepsBuild an RF-DETR Workflow
In Roboflow, create a Workflow with an RF-DETR object detection model, either pre-trained on the 80 COCO classes or fine-tuned on your own, and copy its Workflow ID.
Install the inference CLI
Run `pip install 'inference-cli[cloud-storage]'` and set `ROBOFLOW_API_KEY` to your Roboflow API key.
Set your storage account
Set `AZURE_STORAGE_ACCOUNT_NAME`, plus either `AZURE_STORAGE_SAS_TOKEN` (recommended) or `AZURE_STORAGE_ACCOUNT_KEY`.
Stage the files in your bucket
Run `inference rf-cloud data-staging create-batch-of-images --batch-id my-batch --data-source cloud-storage --bucket-path 'az://my-container/images/**/*.jpg'`. For video, use `create-batch-of-videos` with a path to your video files.
Run the Workflow
Run `inference rf-cloud batch-processing process-images-with-workflow --batch-id my-batch --workflow-id <your-workflow-id> --machine-type cpu --aggregation-format csv`. Use `process-videos-with-workflow` for a video batch.
Download the results
Check progress with `inference rf-cloud batch-processing show-job-details --job-id <job-id>`, then run `inference rf-cloud data-staging export-batch --batch-id <job-id>-export --target-dir ./results`.
What teams build with Azure Blob Storage
Audit an archive of inspection photos
Count defects, parts or people across every image already sitting in Blob Storage, in one job.
Find moments in stored video
Run detection over recorded footage at a set frame rate and get a row for every frame with a match.
Tag files before labeling
Get predictions for a whole bucket so your team knows which files are worth labeling first.
Questions
Yes, if you are happy to import the images into Roboflow. Connect the bucket as a Datasource in your workspace settings (choose Azure Blob Storage), then add a Workflow run set to "On Sync" so every sync runs your Workflow over the newly imported images. The CLI steps on this page import nothing.
Yes. Connect the Roboflow MCP server to Claude Code, Cursor or Codex and paste: "Run my RF-DETR Workflow over every JPG in az://my-container/images/ with Roboflow Batch Processing on CPU, and save the results as CSV in ./results." The agent stages the files with the CLI on your machine, then starts and tracks the job.
The CLI uses them locally to build a URL for each blob. With a SAS token, it appends the token to each URL, so the URLs stay valid for as long as the token does. Give the token read and list access only.
No. RF-DETR runs on CPU, which is the Batch Processing default and costs fewer credits than GPU. Choose GPU for Workflows that chain several models or use large ones such as SAM.
Staged files and job results expire after about seven days, so download them with `export-batch` once the job finishes.
Why are companies choosing Roboflow?
The end-to-end platform for vision AI: create datasets, train models and deploy to production.
Flexible deployment modes
Move from a scalable cloud API to edge hardware like NVIDIA Jetson without managing complex dependencies.
Integrated workflow builder
Combine multiple AI models, custom business logic and third-party integrations into one production-ready pipeline in a low-code editor.
Model monitoring and alerts
Dashboards track confidence, inference time and request volume for your deployed models, and email alerts tell your team when confidence suddenly drops.

















