> AI agents: this is one page from PostHog's docs. Full index of Markdown docs for LLMs: https://posthog.com/llms.txt

# Linking Microsoft Azure (Application Insights) as a source

Canonical URL: https://posthog.com/docs/data-pipelines/sources/azure-application-insights

> **Cloud region:** This page uses US Cloud hosts. For an EU Cloud project, use `https://eu.posthog.com` instead of `https://us.posthog.com` or `https://app.posthog.com` (app host for links).

## On this page

- [Prerequisites](#prerequisites)
- [Adding a data source](#adding-a-data-source)
- [Available tables](#available-tables)
- [Sync modes](#sync-modes)
- [Sync limitations](#sync-limitations)
- [Configuration](#configuration)
- [Supported tables](#supported-tables)
- [Troubleshooting](#troubleshooting)

**Beta release**

This source is currently in **beta**. It works end to end, but you may still hit rough edges. [Let us know](https://us.posthog.com/#panel=support%3Asupport%3Adata_warehouse%3A%3Atrue) if you do.

![](https://res.cloudinary.com/dmukukwp6/image/upload/texture_tan_9608fcca70)

![](https://res.cloudinary.com/dmukukwp6/image/upload/texture_tan_dark_a92b0e022d)

Let AI connect your sources for you

Skip the manual setup — run this in your project and the wizard auto-detects your databases and APIs and connects them to PostHog.

`npx @posthog/wizard warehouse`

![PostHog Wizard hedgehog](https://res.cloudinary.com/dmukukwp6/image/upload/wizard_3f8bb7a240.png)

![](https://res.cloudinary.com/dmukukwp6/image/upload/wizard_3f8bb7a240.png)Let AI connect your sources for you

The Azure Application Insights connector syncs your application telemetry – requests, dependencies, exceptions, and availability results – into the PostHog data warehouse. This enables you to analyze your application monitoring data alongside your product analytics.

## Prerequisites

Before connecting, you need:

1.  A **Microsoft Entra app registration** with the **Reader** role assigned on your Application Insights resource. Follow [Microsoft's authentication setup](https://learn.microsoft.com/en-us/azure/azure-monitor/app/azure-ad-authentication) for instructions.

2.  A **client secret** for the app registration. Create one under **App registrations > Certificates & secrets** in the Azure portal.

3.  Your **Application Insights application ID**. Find it under **API Access** in your Application Insights resource in the Azure portal.

> **Note:** Only Azure public cloud is supported (`api.applicationinsights.io`). Sovereign clouds (government, China) are not supported.

## Adding a data source

1.  In PostHog, go to the [Sources tab](https://app.posthog.com/data-management/sources) of the data pipeline section.
2.  Click **\+ New source** and click **Link** next to this source.
3.  Enter your credentials (see [Configuration](#configuration) below) and click **Next**.
4.  Select the tables you want to sync, choose a sync method and frequency, then click **Import**.

Once the syncs are complete, you can start querying this data in PostHog.

When linking Azure Application Insights, you'll need:

-   **Tenant ID** – your Microsoft Entra (Azure AD) tenant ID.

-   **Client ID** – the application (client) ID of your Microsoft Entra app registration.

-   **Client secret** – the client secret you created for the app registration.

-   **Application Insights application ID** – the application ID from the **API Access** section of your Application Insights resource (this is different from the Azure resource ID).

## Available tables

| Table | Description | Sync method |
| --- | --- | --- |
| `requests` | Incoming application requests, with their duration and result | Incremental |
| `dependencies` | Calls to external services or storage, with their duration and result | Incremental |
| `exceptions` | Application exceptions and their diagnostic details | Incremental |
| `availabilityResults` | Availability test results that measure application responsiveness and uptime | Incremental |

All tables support both **incremental** and **full refresh** sync. Incremental syncs only fetch new or updated records using the `timestamp` field.

## Sync modes

Each table can be synced in one of several modes, depending on what the source supports:

-   **Webhook** (when available) – the source pushes changes to PostHog in real time. Fastest freshness, lowest ongoing cost, and the only mode that reliably captures updates and deletes.
-   **Incremental** – only new or updated rows are synced on each run, using a cursor field (such as an `updated_at` timestamp). Cheaper than a full refresh, but deletes aren't captured.
-   **Append only** – new rows are appended using a cursor field; existing rows are never updated. Ideal for immutable, append-only tables like event logs.
-   **Full refresh** – the whole table is reloaded on every sync. Use it when a table has no reliable cursor or when you need deletions reflected.

See [sync methods](https://posthog.com/docs/data-pipelines/sources.md#sync-methods) for a full explanation of how each mode works and how to choose between them.

## Sync limitations

-   Each sync reads at most the **last seven days** of telemetry, including full refresh. To import older telemetry, use a separate [Azure export](https://learn.microsoft.com/en-us/azure/azure-monitor/app/export-telemetry).

-   Incremental syncs repeat the **previous hour** before the last saved timestamp to capture delayed telemetry. Data that arrives more than one hour late may be missed.

## Configuration

| Option | Type | Required |
| --- | --- | --- |
| `Tenant ID` | text | Yes |
| `Client ID` | text | Yes |
| `Client secret` | password | Yes |
| `Application Insights application ID` | text | Yes |

## Supported tables

| Table | Description | Sync method | Incremental field | Primary key |
| --- | --- | --- | --- | --- |
| `requests` | Incoming application requests, with their duration and result. | Incremental, Full refresh | timestamp | — |
| `dependencies` | Calls to external services or storage, with their duration and result. | Incremental, Full refresh | timestamp | — |
| `exceptions` | Application exceptions and their diagnostic details. | Incremental, Full refresh | timestamp | — |
| `availabilityResults` | Availability test results that measure application responsiveness and uptime. | Incremental, Full refresh | timestamp | — |

## Troubleshooting

-   **Authentication error:** Your tenant ID, client ID, or client secret is incorrect or the secret has expired. Verify them in the Azure portal under **App registrations**, then reconnect.

-   **Permissions error:** Your Microsoft Entra app does not have the **Reader** role on the Application Insights resource. Assign the role under **Access control (IAM)** on the resource, then reconnect.

-   **Application not found error:** The Application Insights application ID is incorrect or the app registration does not have access. Check the ID under **API Access** in your Application Insights resource.

If your sync is failing or data looks wrong, see the [Data warehouse troubleshooting guide](https://posthog.com/docs/data-warehouse/troubleshooting.md). If that doesn't help, [contact support](https://us.posthog.com/#panel=support%3Asupport%3Adata_warehouse%3A%3Atrue) – we're happy to help.