OpenText DAM (OTMM) - Azure Blob Storage Integration and Automation

Common Integration Use Cases Between OpenText DAM (OTMM) and Azure Blob Storage

1. Publish approved product and campaign assets from OpenText DAM (OTMM) to Azure Blob Storage for external distribution

Data flow: OpenText DAM (OTMM) to Azure Blob Storage

Marketing, eCommerce, and channel operations teams can push final approved images, videos, and campaign files from OpenText DAM (OTMM) into Azure Blob Storage for high-volume distribution to websites, partner portals, retail systems, and content delivery processes. OTMM remains the system of record for asset governance, version control, and approvals, while Azure Blob Storage serves as the scalable delivery layer for downstream consumers.

• Reduces load on the DAM for external file serving
• Supports fast, reliable access for global distribution channels
• Ensures only approved assets are exposed outside the DAM

2. Ingest large media files from Azure Blob Storage into OpenText DAM (OTMM) for curation and governance

Data flow: Azure Blob Storage to OpenText DAM (OTMM)

Field teams, agencies, photographers, and event production vendors can upload raw images and video into Azure Blob Storage first, especially when files are large or arrive in bulk. OpenText DAM (OTMM) then ingests selected files for metadata enrichment, rights management, review, and approval before they are made available to business users.

• Simplifies intake of large media files from external contributors
• Creates a controlled review process before assets enter the DAM
• Improves collaboration with agencies and production partners

3. Store derivative renditions and thumbnails in Azure Blob Storage while keeping master assets in OpenText DAM (OTMM)

Data flow: OpenText DAM (OTMM) to Azure Blob Storage

OpenText DAM (OTMM) can generate renditions such as thumbnails, web-optimized images, preview clips, and compressed video files, then store those derivatives in Azure Blob Storage for fast retrieval by portals and applications. The DAM retains the master asset and metadata, while Blob Storage handles lightweight delivery copies.

• Improves performance for web and mobile consumption
• Reduces storage and bandwidth pressure on the DAM
• Supports multiple file formats for different channels

4. Use Azure Blob Storage as a staging area for bulk product image and video imports into OpenText DAM (OTMM)

Data flow: Azure Blob Storage to OpenText DAM (OTMM)

Retail and product content teams can drop large batches of product imagery, 360-degree views, and demonstration videos into Azure Blob Storage during seasonal launches or catalog refreshes. Automated workflows can then validate file naming, map metadata, and import the assets into OpenText DAM (OTMM) for catalog association and publishing.

• Speeds up bulk onboarding of product media
• Supports structured import workflows for large campaigns or catalog updates
• Reduces manual handling of files across teams

5. Deliver museum and heritage collection media from OpenText DAM (OTMM) to Azure Blob Storage for public access and digital exhibits

Data flow: OpenText DAM (OTMM) to Azure Blob Storage

Museums and heritage organizations can manage high-resolution collection images and archival videos in OpenText DAM (OTMM), then publish selected public-facing copies to Azure Blob Storage for exhibit websites, educational portals, and research access. This allows curators to maintain strict control over master files while enabling broad access to approved digital assets.

• Separates preservation masters from public delivery copies
• Supports scalable access for online exhibits and learning platforms
• Improves governance over sensitive or restricted collection content

6. Synchronize asset status and availability between OpenText DAM (OTMM) and Azure Blob Storage

Data flow: Bi-directional

When an asset is approved, expired, replaced, or withdrawn in OpenText DAM (OTMM), the corresponding file in Azure Blob Storage can be updated or removed automatically. Likewise, usage or delivery status from Azure-based applications can be fed back to the DAM to support lifecycle management, auditability, and content refresh decisions.

• Prevents outdated assets from remaining in distribution channels
• Improves compliance with rights and expiration rules
• Provides a clearer operational view of asset lifecycle

7. Support broadcast and event media workflows with Azure Blob Storage as a transfer and distribution layer

Data flow: OpenText DAM (OTMM) to Azure Blob Storage and Azure Blob Storage to OpenText DAM (OTMM)

Broadcast, live event, and corporate communications teams can use Azure Blob Storage to move large video files quickly between production systems, editors, and distribution endpoints, while OpenText DAM (OTMM) manages the approved source library, metadata, and rights. This is especially useful for short-form and long-form video assets that need to move efficiently across production, review, and publishing stages.

• Improves handling of large video files across production workflows
• Supports collaboration between creative, legal, and distribution teams
• Enables controlled publishing of final media assets

8. Provide secure external access to approved assets through Azure Blob Storage while retaining governance in OpenText DAM (OTMM)

Data flow: OpenText DAM (OTMM) to Azure Blob Storage

Organizations can expose approved assets to agencies, distributors, franchisees, and regional teams through Azure Blob Storage using controlled access methods such as SAS tokens, private endpoints, or application-level permissions. OpenText DAM (OTMM) remains the authoritative source for metadata, approvals, and version history, while Blob Storage provides secure and scalable access for external stakeholders.

• Reduces the need to grant external users direct DAM access
• Improves security and access control for third parties
• Accelerates asset sharing across distributed business teams