Azure Blob Storage - Consonance Integration and Automation

Common Integration Use Cases Between Azure Blob Storage and Consonance

Azure Blob Storage and Consonance complement each other well in publishing operations. Azure Blob Storage provides scalable, secure file storage and distribution for large volumes of assets, while Consonance manages the editorial, production, rights, and metadata workflows that publishers use to move titles from acquisition through publication. Integrating the two helps publishers keep large files and final deliverables in Azure while Consonance remains the system of record for title workflow, approvals, and metadata.

1. Centralized storage for manuscript and production files

Data flow: Consonance to Azure Blob Storage

When editors, authors, or production teams upload manuscripts, revised proofs, cover files, or interior layouts in Consonance, the files can be automatically stored in Azure Blob Storage as the long-term file repository. Consonance retains the workflow status, version history, and title metadata, while Azure provides scalable storage for large and growing file sets.

• Reduces file storage load inside the workflow platform
• Creates a secure, durable archive for all title assets
• Supports easy retrieval of prior versions during editorial and production review

2. Automated delivery of final publication assets to downstream channels

Data flow: Consonance to Azure Blob Storage

Once a title reaches publication readiness in Consonance, final print PDFs, EPUB files, audiobook masters, and marketing assets can be pushed to Azure Blob Storage for distribution to printers, digital retailers, audio vendors, or internal sales teams. Consonance can trigger the transfer based on workflow milestones such as final approval or publication date.

• Speeds handoff from production to distribution
• Ensures only approved assets are released
• Supports multi-format publishing with consistent file packaging

3. Shared access to cover art and marketing materials

Data flow: Azure Blob Storage to Consonance

Marketing and design teams can store high-resolution cover images, jacket files, author photos, and promotional artwork in Azure Blob Storage, then link those assets back into Consonance title records. This gives editorial and production teams direct access to approved creative files without duplicating storage across systems.

• Keeps creative assets organized in a single scalable repository
• Improves coordination between marketing, design, and production teams
• Reduces the risk of using outdated or unapproved artwork

4. Version-controlled manuscript and proof management

Data flow: Bi-directional

Consonance can manage the workflow state for manuscript drafts and proof cycles, while Azure Blob Storage holds each version of the file with timestamps and naming conventions. When a new proof is uploaded, Consonance can update the title record with the latest file link, and Azure can preserve earlier versions for audit and rollback purposes.

• Supports editorial review and legal traceability
• Helps teams compare versions during copyediting and design changes
• Provides a reliable archive for compliance and dispute resolution

5. Rights and permissions controlled asset distribution

Data flow: Consonance to Azure Blob Storage

For titles with territory-specific rights or embargoed materials, Consonance can determine who is allowed to access a file package, then generate secure Azure Blob Storage links for approved users or partners. This is especially useful for rights teams sharing sample chapters, translation files, or licensed artwork with external stakeholders.

• Aligns file access with rights and contractual restrictions
• Reduces manual sharing of sensitive materials
• Improves control over external partner distribution

6. Metadata-driven file packaging for retailers and industry databases

Data flow: Consonance to Azure Blob Storage

Consonance can assemble title metadata, cover images, and product files into structured packages and store them in Azure Blob Storage for downstream systems that feed retailers, wholesalers, and industry databases. This allows publishers to generate consistent title packages by imprint, format, or market without manually collecting files from multiple teams.

• Improves accuracy of title data and associated assets
• Speeds preparation of distribution-ready content packages
• Supports repeatable publishing operations across large catalogs

7. Long-term archival of completed title records and assets

Data flow: Consonance to Azure Blob Storage

After publication, completed title files, final metadata exports, royalty support documents, and production deliverables can be archived in Azure Blob Storage for long-term retention. Consonance continues to manage the title record and business context, while Azure serves as the archival layer for future audits, reprints, and rights reviews.

• Reduces operational clutter in active workflow systems
• Supports audit, legal, and reissue requirements
• Makes historical title assets easy to retrieve when needed

Overall, integrating Azure Blob Storage with Consonance helps publishers separate workflow management from large-scale file storage. Consonance remains the operational hub for title development and publishing decisions, while Azure Blob Storage provides secure, scalable, and cost-effective storage for the files that support those workflows.