The following information applies only to dedicated instance deployments with Azure Private Link for Unstructured Business on Azure.For dedicated instance deployments of Unstructured Business to Azure without Azure Private Link, contact your Unstructured sales representative,
or email Unstructured Sales at sales@unstructured.io.
High-level onboarding process
Use a support ticket for all configuration data exchanges. Open a ticket in the Unstructured Support Portal with the subject line
PrivateLink Configuration Request — [Your Company Name].Step 1: Provide provisioning information
Provide the information listed in Before you begin to Unstructured to begin provisioning your dedicated instance.Step 2: Unstructured provisions your dedicated instance
No action is required from you during this step. Once provisioning is complete, Unstructured will provide you with:- The Azure Subscription ID your dedicated instance is hosted in
- The Private Link Service Resource ID for your dedicated instance
Step 3: Connect to the Unstructured Platform
Once your dedicated instance is provisioned, establish private connectivity from your environment so your users can access Unstructured Pipelines and the API. In Azure terminology, Unstructured is the service provider (publishing a Private Link Service) and you are the service consumer (creating a Private Endpoint to connect to it).Information exchange
Step 3a: Provide your Azure Subscription IDs
Provide Unstructured with the Azure Subscription IDs that need access to your dedicated instance. Unstructured adds these subscriptions to the auto-approval list on the Private Link Service, so Azure approves Private Endpoint connections from those subscriptions automatically.Step 3b: Create a Private Endpoint
In each Azure subscription that requires access, create a Private Endpoint targeting Unstructured’s Private Link Service. Learn how. When creating the endpoint:- Use the Private Link Service Resource ID provided by Unstructured in Step 2
- Create it as a manual connection request. In the portal, choose Connect to an Azure resource by resource ID or alias and paste the Private Link Service Resource ID. With the Azure CLI, run
az network private-endpoint createwith--private-connection-resource-id <PLS resource ID> --connection-name <name> --manual-request true. A direct (non-manual) connection fails withLinkedAuthorizationFailed, because it requires approval rights on Unstructured’s Private Link Service - Deploy it in a VNet and subnet in the same Azure region as your dedicated instance
- Confirm the subnet’s private endpoint network policies are configured to allow the Private Endpoint to deploy. New subnets default to allowing this; on existing subnets, verify that your network security group (NSG) and route table (UDR) policies do not block the Private Endpoint
Step 3c: Unstructured approves your connection request
No action is required from you during this step. Connection requests from the subscriptions you provided in Step 3a are approved automatically. A request from any other subscription stays Pending until Unstructured approves it.Step 3d: Configure DNS
Configure DNS so your dedicated instance hostname resolves to the private IP of your Private Endpoint. The right approach depends on your authoritative DNS and where your clients connect from. For setup details across the most common scenarios — clients in your Azure VNet, on-premises clients reaching the platform over ExpressRoute or VPN, and clients connecting through a Zero Trust Network — see Configure DNS for Azure Private Link.Step 4: Connect to your data sources and destinations
Once your users can access the Unstructured Platform, connect the platform to your data sources and destinations. The approach depends on the type of service.- Azure-managed services (Blob Storage, ADLS Gen2, Azure OpenAI, AI Search, Azure SQL, Cosmos DB, PostgreSQL, MySQL, Synapse, Azure Databricks): See Connecting to Azure-managed services
- Customer-managed services on Azure (self-hosted applications fronted by an Azure Standard Load Balancer): See Connecting to customer-managed services on Azure

