← Back to Tutorials
Beginner⏱️ 25 min

Working with Connectors — SQL, Blob Storage, Outlook

Working with Connectors — SQL, Blob Storage, Outlook

What Are Connectors?

Connectors are pre-built interfaces that allow Azure Logic Apps to communicate with external services, APIs, and data sources without writing custom integration code. They handle authentication, connection management, and data serialization.

Types of Connectors

FeatureBuilt-in ConnectorsManaged ConnectorsCustom Connectors
HostingRun directly in the Logic Apps runtimeHosted and managed by MicrosoftCreated and managed by you
LatencyLower (in-process)Higher (external API call)Varies
CostIncluded in base pricePer-execution billingPer-execution billing
ExamplesHTTP, Schedule, Inline CodeSQL Server, Outlook, Blob StorageYour own REST/SOAP APIs
AvailabilityStandard & ConsumptionStandard & ConsumptionStandard & Consumption
ScalabilityScales with workflowThrottled by MicrosoftSubject to your API limits

Step-by-Step: Add a SQL Connector to Read Data

1. Open the Logic Apps Designer

Navigate to your Logic App in the Azure Portal and open the designer view.

Screenshot: Open Logic Apps Designer

2. Add a New Step

Click + New step after your trigger and search for "SQL Server".

Screenshot: Search for SQL Server connector

3. Select the Action

Choose Get rows (V2) to read data from a SQL table.

Screenshot: Select Get rows action

4. Configure the Connection

Provide your SQL Server connection details:

  • Server name: your-server.database.windows.net
  • Database name: your-database
  • Authentication: SQL Server Authentication or Managed Identity

Screenshot: Configure SQL connection

5. Configure the Query

Select the table name and optionally add a filter query (OData format) and row count limit.

Screenshot: Configure SQL query parameters

6. Test the Step

Run the workflow and verify the SQL data appears in the output.

Screenshot: SQL connector output results

Step-by-Step: Add Blob Storage Connector to Upload a File

1. Add a New Step

Click + New step and search for "Azure Blob Storage".

Screenshot: Search for Blob Storage connector

2. Select the Action

Choose Create blob (V2) to upload a file.

Screenshot: Select Create blob action

3. Configure the Connection

Provide your storage account details:

  • Storage account name: your-storage-account
  • Authentication: Access Key, Managed Identity, or Azure AD

Screenshot: Configure Blob Storage connection

4. Set Blob Parameters

Configure:

  • Container: select or type the target container
  • Blob name: define the file path/name (can use dynamic content)
  • Blob content: provide the file content from a previous step

Screenshot: Configure blob upload parameters

5. Test the Upload

Run the workflow and verify the blob appears in your storage container.

Screenshot: Blob upload success confirmation

Step-by-Step: Add Outlook Connector to Send Email

1. Add a New Step

Click + New step and search for "Office 365 Outlook".

Screenshot: Search for Outlook connector

2. Select the Action

Choose Send an email (V2).

Screenshot: Select Send email action

3. Authenticate

Sign in with your Microsoft 365 account when prompted. This creates an OAuth connection.

Screenshot: Outlook OAuth sign-in prompt

4. Compose the Email

Configure:

  • To: recipient email address (can use dynamic content)
  • Subject: email subject line
  • Body: email body (supports HTML)

Screenshot: Configure email fields

5. Test the Email

Run the workflow and verify the email arrives in the recipient's inbox.

Screenshot: Email sent successfully

Authentication Options

MethodUse CaseConnectors
Connection StringQuick setup for development/testingSQL Server, Blob Storage
Managed IdentityProduction workloads, no secrets to manageSQL Server, Blob Storage, Key Vault
OAuth 2.0User-delegated access to Microsoft 365 servicesOutlook, SharePoint, Teams
Service PrincipalApp-level access without user contextBlob Storage, SQL Server
Access KeySimple storage account accessBlob Storage

Recommendations

  • Use Managed Identity for production to avoid storing credentials
  • Use OAuth for connectors that act on behalf of a user
  • Rotate connection strings and access keys regularly
  • Store secrets in Azure Key Vault and reference them in your connections

Common Issues

IssueCauseSolution
"Forbidden" error on SQL connectorFirewall blocking Logic App IPAdd Logic App outbound IPs to SQL Server firewall rules
Blob upload fails with 404Container does not existCreate the container before running the workflow
Outlook connector expiresOAuth token refresh failedRe-authorize the connection in API Connections
"Gateway timeout" on SQLQuery takes too longAdd filters to reduce result set or increase timeout
Managed Identity not workingIdentity not assigned RBAC roleAssign the appropriate role (e.g., Storage Blob Data Contributor)
Connection shows "Invalid"Credentials rotated or expiredUpdate the API connection with new credentials

Previous: Logic Apps Triggers

Next: Data Operations