Skip to main content
This page describes how to establish private connectivity between your dedicated instance and Azure-managed services. For self-hosted applications, see Connecting to customer-managed services on Azure.

Azure managed services

This section covers Azure-managed services that have service-specific private connectivity requirements. The tables below use Order to indicate the general sequence of the information exchange — items with the same Order value can usually be provided at the same stage. Values like <UNSTRUCTURED_SP_ID> and <DI_AZURE_SUBSCRIPTION_ID> are placeholders; contact your Unstructured account team or open a ticket in the Unstructured Support Portal to get the actual values for your dedicated instance.
Each Azure service you connect to via Private Link must be in the same Azure region as your dedicated instance — cross-region Private Link is not supported. The example region codes in the tables below are illustrative; use the region your dedicated instance is deployed in. See Known limitations.

Azure Blob Storage

This applies to Azure Blob Storage and Azure Data Lake Storage Gen2 (ADLS Gen2). For ADLS Gen2, use sub-resource type dfs for hierarchical namespace operations. You must approve the private endpoint connection request. To do so, navigate to Storage Account > Networking > Private endpoint connections. Example: Azure role assignment The following Azure CLI command assigns the Storage Blob Data Reader role to Unstructured’s service principal so the platform can read blobs in your storage account.
For read/write access, use the Storage Blob Data Contributor role instead of Storage Blob Data Reader. Replace:
  • <UNSTRUCTURED_SP_ID> — Service principal ID for Unstructured (provided during onboarding)
  • <SUBSCRIPTION_ID> — Your Azure subscription ID
  • <RESOURCE_GROUP> — Resource group that contains the storage account
  • <STORAGE_ACCOUNT> — Storage account name

Azure OpenAI

Azure OpenAI supports private endpoint access. Unstructured creates a private endpoint in our VNet to access the your Azure OpenAI resource privately. Example: Azure role assignment for OpenAI Use Azure CLI to assign the Cognitive Services OpenAI User role to Unstructured’s service principal for your Azure OpenAI resource:
Replace:
  • <UNSTRUCTURED_SP_ID> — Service principal ID for Unstructured (provided during onboarding)
  • <SUBSCRIPTION_ID> — Your Azure subscription ID
  • <RESOURCE_GROUP> — Resource group that contains the storage account
  • <OPENAI_RESOURCE> — Your Azure OpenAI Resource ID
After the role assignment:
  1. Firewall: On the Azure OpenAI resource, configure networking so public access is disabled and traffic is allowed only as required for your private endpoint design.
  2. Approve the connection: In the Azure portal, go to the OpenAI resource > Networking > Private endpoint connections, then approve the pending private endpoint connection from Unstructured.

Azure Databricks

Azure Databricks supports Private Link for both front-end (user-to-workspace) and back-end (compute-to-control plane) connectivity. You must have Private Link enabled on your workspace. Example: Approve the Databricks private endpoint connection After Unstructured creates the private endpoint toward your workspace, approve the pending connection using Azure CLI:
You can also approve the same request in the Azure portal: open the Databricks workspace resource > Networking > Private endpoint connections, then approve the pending connection from Unstructured. Replace:
  • <RESOURCE_GROUP> — Resource group that contains the Databricks workspace
  • <WORKSPACE_NAME> — Name of the Databricks workspace resource
  • <PRIVATE_ENDPOINT_NAME> — Name of the private endpoint connection (shown in the portal or provided by Unstructured)

Azure Managed Services with private endpoint access

This section applies to Azure Managed Services that support private endpoint access, including: Azure AI Search, Azure SQL Database, Azure SQL Managed Instance, Azure Cosmos DB, Azure Database for PostgreSQL, Azure Database for MySQL, and Azure Synapse Analytics.
The Order column indicates the general sequence for the information exchange. Items with the same order value can usually be provided at the same stage.
Sub-resource types by service: