← All integrations
Import.io + Azure Blob Storage

Web data delivered into Azure Blob Storage

Managed Services and Aperture deliver into your Azure storage account on schedule, where Fabric, Synapse, Databricks and Power BI pick it up.

Connects via
Managed
Setup
At onboarding
Available on
Managed Services and Aperture
Delivery
Destination  https://youraccount.blob.core.windows.net/importio/
Schedule     agreed with your Managed Services team
Format       CSV or JSON, to your schema

How it connects.

Source

The web

Any public page, rendered, through managed proxies

Engine

Import.io

Rendering, proxy routing, captcha handling, extraction

Path

Managed delivery

Built, run and QA’d under an SLA

Destination

Azure Blob Storage

Managed delivery into your Azure storage account.

What teams do with it.

Microsoft Fabric and Synapse

Shortcut or load deliveries into your lakehouse.

Power BI dataflows

Enterprise reports on governed files.

Databricks on Azure

Auto Loader streams deliveries into Delta tables.

Set it up.

  1. Create a container for Import.io deliveries.
  2. Share the storage details with your Import.io team at onboarding.
  3. Point your lakehouse, dataflow or Auto Loader job at the container.

Questions.

Is Azure delivery available on self-service plans?

Self-service plans deliver into S3 and SFTP. Azure Blob delivery comes with Managed Services and Aperture.

Who sets up managed delivery?

Your Managed Services team. They agree destination, format, schedule and schema with you, then build, run, monitor and QA the feed under an SLA.

Which destinations can Managed Services deliver into?

Amazon S3, Google Cloud Storage, Azure Blob Storage, SFTP, Snowflake, BigQuery, API, email and Slack alerts. Aperture delivers into the same destinations.

Fresh web data
in Azure Blob Storage.