Azure Blob Storage - OpenText Extended ECM - Business Workspaces Integration and Automation

Common Integration Use Cases Between Azure Blob Storage and OpenText Extended ECM - Business Workspaces

1. Centralized document repository for business workspaces

Flow: Azure Blob Storage ? OpenText Extended ECM - Business Workspaces

Large file sets such as scanned contracts, engineering drawings, media assets, or claim evidence can be stored in Azure Blob Storage and linked into the relevant OpenText business workspace. The workspace provides the business context, metadata, and governance, while Blob Storage handles scalable, low-cost file storage.

• Reduces content sprawl across shared drives and email attachments
• Improves access to large files without overloading the ECM repository
• Supports teams working in customer, project, or case-based workspaces

2. Automated ingestion of project deliverables into workspaces

Flow: Azure Blob Storage ? OpenText Extended ECM - Business Workspaces

When project teams upload deliverables, design files, or final reports to Azure Blob Storage, an integration can automatically create or update the related business workspace in OpenText Extended ECM. Metadata such as project ID, client name, document type, and version can be applied during ingestion.

• Speeds up onboarding of project content into governed workspaces
• Ensures deliverables are tied to the correct business object
• Improves traceability for audits and handoffs

3. Controlled access to large files from line of business processes

Flow: OpenText Extended ECM - Business Workspaces ? Azure Blob Storage

Users working in ERP, CRM, or case management processes can access large supporting files stored in Azure Blob Storage directly through the OpenText workspace. The workspace manages permissions and context, while Blob Storage provides efficient file delivery for high-volume access.

• Enables users to retrieve supporting content without leaving the business process
• Maintains governance and role-based access control
• Improves productivity for sales, service, legal, and operations teams

4. Retention-based archiving of inactive workspace content

Flow: OpenText Extended ECM - Business Workspaces ? Azure Blob Storage

Completed case files, closed project records, or inactive workspace attachments can be archived from OpenText Extended ECM into Azure Blob Storage for long-term retention. The workspace retains the business record reference and metadata, while the file payload is moved to lower-cost storage.

• Reduces ECM storage footprint and operating cost
• Supports retention and lifecycle management policies
• Keeps historical content available for compliance or legal review

5. Evidence collection for regulated business processes

Flow: Azure Blob Storage ? OpenText Extended ECM - Business Workspaces

In regulated workflows such as claims, audits, procurement disputes, or loan processing, evidence files can be collected in Azure Blob Storage from external systems or field teams and then attached to the corresponding OpenText workspace. The workspace becomes the controlled environment for review, approval, and decision-making.

• Creates a single source of truth for case evidence
• Improves collaboration between operations, compliance, and legal teams
• Supports structured review and approval workflows

6. External file exchange with partners and suppliers

Flow: Bi-directional

Organizations can use Azure Blob Storage as a secure exchange layer for large files shared with external parties, while OpenText Extended ECM manages the internal business workspace and approval process. For example, suppliers upload technical documents to Blob Storage, and approved versions are linked into the procurement or supplier workspace.

• Supports secure collaboration with external stakeholders
• Separates file transfer from governed internal content management
• Improves supplier onboarding and document approval cycles

7. Versioned content delivery for customer or project portals

Flow: OpenText Extended ECM - Business Workspaces ? Azure Blob Storage

Approved documents from OpenText workspaces, such as customer statements, project packs, or policy documents, can be published to Azure Blob Storage for distribution through portals or downstream applications. The workspace controls approval and versioning before content is exposed externally.

• Ensures only approved content is distributed
• Supports high-volume, scalable document delivery
• Reduces manual publishing effort across teams

8. Disaster recovery and content resilience for critical workspace files

Flow: OpenText Extended ECM - Business Workspaces ? Azure Blob Storage

Critical workspace documents can be replicated or backed up to Azure Blob Storage to support resilience, recovery, and business continuity. In the event of a repository outage or migration activity, content can be restored while preserving workspace metadata and business context.

• Improves resilience for mission-critical content
• Supports backup, recovery, and migration strategies
• Reduces risk of content loss for regulated business records