Skip to Content
How-To GuidesConnect Azure Blob

Connect Azure Blob Storage

This guide walks you through connecting an Azure Storage Account to Slim.io using a Service Principal.

Time required: 5–10 minutes

Prerequisites:

  • Azure Portal access with permissions to create app registrations
  • A Storage Account with blob containers you want to scan

Step 1: Create an App Registration

  1. In the Azure Portal, go to Azure Active Directory > App registrations.
  2. Click New registration.
  3. Name: slim-io-scanner.
  4. Supported account types: Single tenant.
  5. Click Register.
  6. Note the Application (client) ID and Directory (tenant) ID from the Overview page.

Step 2: Create a Client Secret

  1. In the app registration, go to Certificates & secrets.
  2. Click New client secret.
  3. Description: Slim.io Scanner.
  4. Expiry: Choose your organization’s policy (6 months, 12 months, or 24 months).
  5. Click Add.
  6. Immediately copy the secret value — it will not be shown again.

The client secret is displayed only once when created. Copy it immediately. If lost, you must create a new secret and update the connector configuration.

Step 3: Grant Storage Access

  1. Navigate to your Storage Account in the Azure Portal.
  2. Go to Access control (IAM) > Add role assignment.
  3. Role: Storage Blob Data Reader.
  4. Members: Select the slim-io-scanner app registration.
  5. Click Review + assign.

Step 4: Configure the Connector in Slim.io

  1. Navigate to Connectors > Add Connector in the Customer Dashboard.
  2. Select Microsoft Azure.
  3. Enter the Tenant ID (from Step 1).
  4. Enter the Client ID (from Step 1).
  5. Enter the Client Secret (from Step 2).
  6. Enter the Storage Account Name.
  7. Click Test Connection.

Step 5: Verify

A successful test shows:

  • Green “Connected” status
  • List of accessible containers
  • Estimated blob count

Troubleshooting

IssueSolution
”Authorization failed”Verify Tenant ID and Client ID are correct; confirm the client secret has not expired
”Storage account not found”Check the storage account name (case-sensitive)
“Forbidden”Ensure you assigned Storage Blob Data Reader (not just Reader) on the storage account

Next Steps

Last updated on