The Azure Blob Storage Connector imports conversation recordings, transcripts, and metadata stored in Microsoft Azure Blob Storage into Quality AI Express. Organizations can use this connector with third-party CCaaS platforms to enable automated quality evaluations, conversation analytics, sentiment analysis, coaching workflows, and reporting.
The connector periodically scans configured Azure Blob Storage locations and ingests supported conversation data into Quality AI Express.
Prerequisites
Azure Storage Requirements
| Requirement | Description |
|---|
| Storage Account | Azure Storage Account with Blob access subscription |
| Authentication | Connection String |
| Container | Azure Blob container containing conversation files |
| Supported File Types | WAV, MP3, JSON, CSV |
| Maximum File Size | 50 MB per file |
| Timestamp Format | ISO 8601 UTC (YYYY-MM-DDTHH:MM:SSZ) |
| Requirement | Description |
|---|
| Quality AI Express | Connector feature enabled |
| Agent Setup | Agents configured with valid email addresses |
| Queue Setup | Quality AI queues configured and available for mapping |
| Permissions | Access to Connectors configuration |
Authentication Methods
The connector supports Connection String authentication.
Connection String (Recommended)
Use this method for production deployments.
- Open Azure Portal.
- Navigate to Storage Account.
- Go to Security + Networking > Access Keys.
- Copy the Connection String for Key1 or Key2.
Use Account Key authentication for simple setups. Use Connection Strings for centralized credential management in production environments.
Supported Data Types and File Requirements
Azure Blob Storage supports the same data types as AWS S3 Connector.
| Data Type | Format | Files per Conversation | File Requirements | Analytics Support |
|---|
| Stereo Voice | WAV, MP3 | 1 dual-channel file | Single dual-channel recording (agent + customer). | Complete Analytics |
| Mono Voice | WAV, MP3 | 2 files (agent and customer) | Separate agent and customer recordings.
- Supported: conv-123456-agent.wav and conv-123456-customer.wav.
- Not Supported: conv-123456-mixed.wav containing both speakers. | Enhanced Analytics |
| Voice Transcript | JSON | 1 transcript file | Pre-transcribed voice conversation. | Text Analytics |
| Chat Transcript | JSON | 1 transcript file | Message-level chat transcript. | Complete Text Analytics |
Mono voice conversation requires two-file recording structure (for agent and customer). Combined recordings aren’t supported.
Storage Structure Options
Option A: Unified Path (Voice and Chat in a Single Folder Structure)
container/
├── metadata.csv
├── audio/
│ ├── conv-123456.wav
│ ├── conv-123457-agent.wav
│ └── conv-123457-customer.wav
├── chat/
│ └── chat-123459.json
└── test.csv
container/
├── voice/
│ ├── metadata.csv
│ ├── recordings/
│ └── test.csv
└── chat/
├── metadata.csv
├── transcripts/
└── test.csv
- Upload all required files to Azure Blob Storage.
- Metadata CSV contains required fields and valid values.
- Mono conversations contain separate agent and customer files.
- The configured container and folder paths are available.
- A
test.csv file exists in each ingestion path.
- Blob permissions enable the connector to access the files.
- Avoid spaces and special characters in file and folder names to simplify ingestion and troubleshooting.
Step 1: Create the Connector
- Navigate to Quality AI > Configure > Connectors.
- Select + Add Connector > Azure Blob Storage > Connect.
- Enter a Name for the connector.
- Select the Azure Region for the storage account.
- Choose Authentication Type as Connection String.
- Enter the Connection String from Azure Storage Account.
- Configure the Channel and Storage Paths:
- Unified Path: Enter a single Blob path containing both voice and chat data.
- Separate Paths: Enter separate Voice Path and Chat Path for ingestion.
Step 2: Test Connection
Run validation checks:
- Select the Test tab.
- Run the connection test.
- Verify that the system passes all validation checks: Authentication, File Path Access, File Format Validation, and Metadata Validation.
- Select the Queue tab.
- Map each
queueId value from the CSV files to a Quality AI Express queue. Values must match exactly.
- Repeat for all queue identifiers.
- Select Save.
Every queue ID in the metadata file must map to an existing Quality AI Express queue before ingestion can run. Evaluation forms linked to mapped queues determine how interactions are evaluated.
- Select the Schedule tab.
- Set the Interval Type, Start Date, Repeat Every, and Start Time (UTC).
- Select Save to activate the schedule.
Verify Configuration
- Save and validate the queue mappings.
- Activate the processing schedule.
- Verify that the first ingestion job appears in the Log tab.
- Confirm that the system reports no processing errors.
Success Indicators
- All conversations display in Quality AI Express dashboards.
- Analytics data is available for ingested interactions.
Step 5: Monitor Ingestion Jobs
Use the Log tab to monitor ingestion activity.
| Column | Description |
|---|
| Start Time | Job start time |
| Finish Time | Job completion time |
| Uploaded | Uploaded files count |
| Processing | Processed files count |
| Job Status | Current processing status |
| View Details | Opens job details |
Troubleshooting
Authentication Issues
| Problem | Symptom | Resolution |
|---|
| Authentication Failed | Authentication error | Verify the Account Key, Connection String, and Storage Account Name. Re-copy the credentials from the Azure portal and test again. |
| Authorization Header Error | Request rejected | Generate a new access key and update the connector configuration. |
Storage Access Issues
| Problem | Symptom | Resolution |
|---|
| Container Not Found | Container or path not found | Verify the container name and folder structure. |
| File Not Available | Blob Access denied | Verify blob access permissions and storage access settings. |
File Validation Issues
| Problem | Symptom | Resolution |
|---|
| File Format Validation Error | Unsupported or invalid file format | Verify the CSV metadata structure and required headers. |
| Metadata Validation Error | Missing or invalid metadata | Verify required metadata fields and timestamp values. |
Data Processing Issues
| Problem | Symptom | Resolution |
|---|
| Timestamp Validation Error | Invalid timestamp format | Use ISO 8601 UTC format. |
| Queue Mapping Error | Queue IDs not mapped | Map all queue IDs before ingestion. |
