Azure Blob Storage - OpenText Core Digital Asset Management Integration and Automation

Common Integration Use Cases Between Azure Blob Storage and OpenText Core Digital Asset Management

Azure Blob Storage is well suited for scalable, low-cost storage and high-volume file distribution, while OpenText Core Digital Asset Management is designed to organize, govern, search, approve, and distribute approved digital assets across teams and channels. Together, they can support efficient asset lifecycle management, from raw file intake to controlled publishing and archival.

1. Centralized asset ingestion from Azure Blob Storage into OpenText Core Digital Asset Management

Direction: Azure Blob Storage to OpenText Core Digital Asset Management

Marketing, creative, or production teams can drop large image, video, and document files into Azure Blob Storage as a staging area. OpenText Core Digital Asset Management can then ingest selected files for metadata enrichment, rights management, version control, and approval workflows. This reduces manual upload effort and creates a controlled path from file delivery to asset governance.

• Useful for agencies delivering campaign assets in bulk
• Supports automated intake of raw files from production teams
• Improves consistency by applying DAM metadata and approval rules after upload

2. Publishing approved digital assets from OpenText Core Digital Asset Management to Azure Blob Storage for external distribution

Direction: OpenText Core Digital Asset Management to Azure Blob Storage

Once an asset is approved in OpenText Core Digital Asset Management, it can be exported to Azure Blob Storage for high-volume distribution to websites, partner portals, mobile apps, or regional teams. Azure Blob Storage provides scalable delivery and can serve as the downstream distribution layer for finalized content.

• Supports fast delivery of approved assets to external systems
• Reduces load on the DAM for public or partner-facing distribution
• Enables region-specific or channel-specific file publishing

3. Automated archival of expired or superseded assets from OpenText Core Digital Asset Management to Azure Blob Storage

Direction: OpenText Core Digital Asset Management to Azure Blob Storage

When assets are no longer active in campaigns or product launches, they can be moved from OpenText Core Digital Asset Management into Azure Blob Storage for long-term retention. This helps organizations keep the DAM focused on active assets while using Azure Blob Storage as a cost-effective archive for compliance, audit, or historical reference.

• Reduces clutter in the active asset library
• Supports retention policies and legal hold requirements
• Lowers storage costs for inactive content

4. Large media file staging in Azure Blob Storage before DAM enrichment and approval

Direction: Azure Blob Storage to OpenText Core Digital Asset Management

Video production teams, photographers, and external vendors can upload large source files to Azure Blob Storage first, avoiding performance issues in the DAM during initial transfer. OpenText Core Digital Asset Management can then pull in the files for review, tagging, rights clearance, and approval. This is especially valuable for high-resolution media and bulk creative deliveries.

• Improves handling of large file transfers
• Separates technical upload from business review
• Speeds up collaboration with external contributors

5. Version synchronization between master files in Azure Blob Storage and approved renditions in OpenText Core Digital Asset Management

Direction: Bi-directional

Azure Blob Storage can hold master source files, while OpenText Core Digital Asset Management manages approved renditions, derivatives, and channel-ready versions. When a master file is updated in Azure Blob Storage, the DAM can be notified to create a new managed version. Conversely, approved renditions from the DAM can be pushed back to Azure Blob Storage for downstream use by applications and business units.

• Maintains a clear separation between source and approved assets
• Reduces version confusion across teams
• Supports controlled reuse of assets across channels

6. Metadata-driven asset routing from OpenText Core Digital Asset Management to Azure Blob Storage containers

Direction: OpenText Core Digital Asset Management to Azure Blob Storage

Assets in OpenText Core Digital Asset Management can be routed to specific Azure Blob Storage containers based on metadata such as brand, region, campaign, product line, or usage rights. For example, approved assets for Europe can be published to a dedicated container for regional websites, while retail assets can be sent to a separate container for store systems.

• Improves governance over where assets are distributed
• Supports multi-brand and multi-region operating models
• Enables automated downstream consumption by business applications

7. Secure external collaboration using Azure Blob Storage as a transfer layer and OpenText Core Digital Asset Management as the system of record

Direction: Azure Blob Storage to OpenText Core Digital Asset Management and OpenText Core Digital Asset Management to Azure Blob Storage

External agencies, freelancers, and production vendors can exchange large files through Azure Blob Storage, while OpenText Core Digital Asset Management remains the authoritative system for approved assets and business metadata. This pattern allows secure file exchange without giving external users direct access to the DAM, while still ensuring that final assets are captured, governed, and searchable in the enterprise repository.

• Reduces access risk for external collaborators
• Keeps the DAM as the controlled source of truth
• Supports secure handoff between creative production and business approval

These integration patterns help organizations combine Azure Blob Storage?s scalable file handling with OpenText Core Digital Asset Management?s governance, search, and lifecycle control, creating a more efficient and auditable asset management process.