Talk to our team

Explore Uplyst

Esc

Popular places to start

platformEnterprise intelligence for the way you work.

Uplyst connects operational data, business relationships and real time events to support decisions across your enterprise.

integrationsConnect your enterprise systems.

Explore Uplyst integrations across business applications, data platforms, databases, event streams and industrial systems.

DocumentationTechnical guides for connected systems

Guides to enterprise architecture, semantic models, integration contracts, security and operations.

resourcesEnterprise intelligence in practice

Architecture, integration and governance guidance for connecting enterprise data with operational decisions.

Azure Blob Storage integration

Bring files from Azure Blob Storage into a connected view of your business. Relate stored exports and datasets to operational records in Uplyst.

Connect the right data with the right access
Storage account
Your Azure environmentThe account that contains the source data
Container
Approved datasetsFiles and exports within the agreed scope
Microsoft Entra ID
Workload identityData access governed through Azure roles

Connect Azure datasets to Uplyst

Azure Blob Storage holds text and binary data in containers within a storage account. Uplyst connects approved datasets with its intelligence layer, giving stored exports the context of the transactions, customers and assets they describe.

The connection scope covers the source account, containers, file formats and business entities. Data Lake Storage accounts may also provide a hierarchical namespace for analytical workloads.

Microsoft Entra data access

Azure Storage supports Microsoft Entra identities and Azure role-based access control. A role such as Storage Blob Data Reader grants access to blob data at the assigned scope.

Data access is distinct from managing the storage account. The selected identity, network configuration and container permissions define the connection to the approved datasets.

Connect files with operational records

Inventory snapshots, financial exports and application data become more useful alongside the transactions and assets they describe.

Source
Storage account, container and blob name
Version
The specific object version, where versioning is available
Business context
Entities, reporting periods and related operational activity

Source references and versions

The storage account, container and blob name identify where data is held. Where Blob versioning is supported and enabled, a version ID distinguishes a specific version of the object's contents.

These references connect analysis with its source and help teams investigate updates to financial exports, inventory snapshots and other recurring files.

Map files to business entities

File structure, source identifiers and reporting periods determine how a dataset maps to Uplyst's business model. This makes it possible to relate an inventory file to products and locations, or a financial export to accounts and transactions.

Validation reflects the data's intended use, including required columns, record completeness and any agreed totals.

Inventory import example26 September 2026
stock.csv

Downloaded successfully

Storage account
operationsdatauk
Container
stock-snapshots
Blob name
2026/09/26/stock.csv
ETag
0x8DCE7206F304A18
Version ID
2026-09-26T08:00:00.0000000Z
Versioning enabled for this account
3 records parsed1 ready · 2 exceptions
MAT-1042WH-MAN01 · 120 EA
Ready

Product, location and unit resolved.

MAT-1042WH-MAN02 · 8 BOX
Unit review

No approved BOX to EA conversion.

MAT-2096WH-LEEDS · 36 EA
Location review

Source location has no business mapping.

Hold inventory publication

Resolve the unit and location exceptions before updating availability by product and site.

Use the ETag with request conditions to check the expected object state; the version ID identifies the selected version. A successful download does not approve its business data.

Analysis across Azure and enterprise systems

Datasets stored in Azure can support inventory reporting, financial reconciliation and operational analysis. Linking them with ERP, CRM and other sources gives teams the wider context behind a result.

Source history also helps distinguish an updated dataset from a missing delivery or a change in the source application.

Related integrations

Azure Event Hubs integrationGoogle Cloud Storage integrationAmazon S3 integration

Connect your systems
with Uplyst.

Talk with our team about the systems you use and the decisions they need to support.

Discuss an integration