Azure Blob Storage - OpenText InfoArchive Integration and Automation

Common Integration Use Cases Between Azure Blob Storage and OpenText InfoArchive

Azure Blob Storage and OpenText InfoArchive complement each other well in enterprise environments where large volumes of files must be retained, governed, and made accessible over time. Azure Blob Storage is strong for scalable file storage and distribution, while OpenText InfoArchive is designed for compliant archiving, long-term retention, and legacy system decommissioning. Together, they support controlled movement of content from active storage into governed archive repositories.

1. Archive inactive files from Azure Blob Storage into OpenText InfoArchive

Organizations can move infrequently accessed documents, images, reports, and exported files from Azure Blob Storage into OpenText InfoArchive after a defined retention threshold. This reduces cloud storage costs while preserving access for audit, legal, and business retrieval needs.

• Data flow: Azure Blob Storage to OpenText InfoArchive
• Business value: Lower storage spend, improved retention control, reduced risk of keeping unmanaged content in active storage
• Typical users: IT operations, records management, compliance teams

2. Retain application export files and transaction extracts for regulatory compliance

Many systems generate monthly statements, invoices, claims extracts, or batch output files that are first stored in Azure Blob Storage for distribution. These files can then be transferred to OpenText InfoArchive to meet regulatory retention requirements and support future audit requests.

• Data flow: Azure Blob Storage to OpenText InfoArchive
• Business value: Ensures immutable retention of business records, simplifies audit response, supports legal hold and disposition policies
• Typical users: Finance, insurance operations, compliance, internal audit

3. Use Azure Blob Storage as a secure staging area for archive ingestion

Enterprises can use Azure Blob Storage as a landing zone for files collected from business applications, scanners, or external partners before they are validated and ingested into OpenText InfoArchive. This pattern supports bulk uploads, transformation, and quality checks before records are archived.

• Data flow: Azure Blob Storage to OpenText InfoArchive
• Business value: Improves ingestion reliability, enables validation and enrichment, supports high-volume archive onboarding
• Typical users: Integration teams, records administrators, application support teams

4. Preserve legacy system attachments and documents during application retirement

When decommissioning a legacy application, associated files can be extracted to Azure Blob Storage during migration and then archived in OpenText InfoArchive with metadata that preserves business context. This allows the legacy platform to be retired while users still retrieve historical documents through archive search and access workflows.

• Data flow: Legacy system to Azure Blob Storage to OpenText InfoArchive
• Business value: Reduces legacy licensing and infrastructure costs, maintains access to historical records, lowers operational risk
• Typical users: Application modernization teams, enterprise architecture, compliance

5. Distribute archived content from OpenText InfoArchive through Azure Blob Storage

In some scenarios, archived content that needs temporary external sharing or downstream processing can be exported from OpenText InfoArchive into Azure Blob Storage. This is useful for controlled distribution to business users, analytics teams, or external service providers without exposing the archive system directly.

• Data flow: OpenText InfoArchive to Azure Blob Storage
• Business value: Enables secure content distribution, supports downstream processing, avoids direct archive system access for non-archive consumers
• Typical users: Business operations, analytics teams, managed service providers

6. Support legal hold and eDiscovery workflows with controlled file transfer

When legal or regulatory teams request records, relevant files can be exported from OpenText InfoArchive into Azure Blob Storage for temporary review, redaction, or case preparation. After the case is closed, the files can be disposed of according to policy, while the authoritative archived copy remains governed in InfoArchive.

• Data flow: OpenText InfoArchive to Azure Blob Storage
• Business value: Speeds legal response, supports case collaboration, reduces risk of uncontrolled document copies
• Typical users: Legal, compliance, records management, external counsel

7. Maintain a hybrid retention model for active and archived content

Organizations can keep current working files in Azure Blob Storage for operational use and automatically move finalized versions into OpenText InfoArchive when business processes complete. This creates a clear separation between active content and governed records, improving lifecycle management across departments.

• Data flow: Azure Blob Storage to OpenText InfoArchive
• Business value: Better content lifecycle governance, reduced clutter in active storage, consistent retention enforcement
• Typical users: Business process owners, IT storage teams, compliance officers

These integration patterns are especially valuable in enterprises managing large file volumes, strict retention obligations, and legacy system retirement programs. Azure Blob Storage provides scalable operational storage, while OpenText InfoArchive ensures those files remain compliant, searchable, and available for the long term.