Export Zoom recordings to Azure Blob Storage.

A recording archive in your Azure tenant.

Cloud Recording Exporter uses the connected Zoom user’s authorization to retrieve available files, then authenticates to Azure with the Microsoft Entra application you configure. The worker uploads each file, verifies the blob, updates destination metadata, and removes its private temporary copy.

Manual Export can move selected historical recordings. Pro can queue new recordings and later transcripts from verified Zoom completion webhooks. Both paths share the same retries, metadata, and remote-object checks.

Configure Azure Blob Storage.

1. Create or choose a containerSelect the storage account, blob container, and optional virtual-directory prefix that will hold Nimbus Whale exports.
2. Register a Microsoft Entra applicationCreate a dedicated app registration and record its tenant ID and application client ID.
3. Create the client secretCreate a long-lived secret that follows your organization’s policy and record its expiration date. Copy the secret value at creation time.
4. Assign the storage roleGrant the application Storage Blob Data Contributor at the narrowest practical storage-account or container scope.
5. Complete the connection testEnter the tenant, client, secret, storage account, container, and prefix in the dashboard. Nimbus Whale verifies blob access and writes the destination README before showing Connected.

Use Entra authorization instead of account keys.

The integration uses a tenant ID, client ID, and encrypted client secret to obtain Azure access tokens. The Storage Blob Data Contributor role permits the blob create, read, list, and delete operations needed for connection validation, uploads, metadata reads, and remote-object verification.

Assign the role only to the container when your Azure configuration supports that scope. Nimbus Whale stores the supplied credential expiration date and can warn before the secret expires; the secret value is never returned by destination APIs.

The same dated layout across destinations.

<configured-prefix>/
├── index.json
├── README.md
└── YYYY/MM/DD/
    ├── <meetingUUID>.json
    ├── <recording-file>.mp4
    ├── <audio-file>.m4a
    └── <transcript>.vtt

The root index is cumulative. The dated meeting manifest lists source file IDs and types, relative blob names, byte counts, SHA-256 checksums, and completion state. Existing legacy Azure monthly indexes remain readable during metadata checks.

Your Azure administrators remain responsible for container encryption, network restrictions, lifecycle management, replication, and retention policies.

Do not confuse Zoom readiness with Azure delivery.

A Zoom recording can be fully processed before it has been exported. Nimbus Whale reports Azure completion only after the blob and its metadata are written. On later refreshes, it reads destination metadata and verifies that referenced blobs still exist.

If index.json, the dated meeting metadata, or a referenced blob is missing, the file becomes exportable again. The same rule applies to manual and automatic transfers.

Rotate the secret before it expires.

Create a replacement client secret, update the Azure configuration in Nimbus Whale, verify the connection, and then remove the prior secret in Microsoft Entra. Disconnecting Azure deletes the encrypted destination configuration and cancels unfinished jobs for that destination; completed blobs remain in your container.

For security details, read the Cloud Recording Exporter security overview. For setup help, email [email protected] without including secrets.