Integrations / Azure

Azure

Microsoft Azure is a cloud computing platform providing infrastructure, platform, and software services including virtual machines, storage, and managed databases.

OAuth 2.0

Indexes

Actions

What Telara does

Capability matrix

Indexes Yes Tracks spend No Discovers shadow AI No Runs actions Yes Real-time events No

Before you connect

Prerequisites

A Microsoft Entra tenant and an Azure subscription you can grant access to. A personal Microsoft account is not a subscription.

Permission to create an app registration or service principal, and to assign Azure roles on the subscription.

Vendor setup

Get the credential

Prefer the Connect button

Settings → Integrations → Azure. If Telara offers OAuth, click Connect and sign in with a user who can consent for the tenant. You do not paste a password.

Or register an app in Entra

In the Azure portal, open Microsoft Entra ID → App registrations → New registration. Name it for Telara. Note the Application (client) ID and Directory (tenant) ID.

Create a client secret and grant the subscription

On the app, open Certificates & secrets → New client secret. Copy the secret value immediately. Then open the subscription → Access control (IAM) → Add role assignment and grant that app the Azure roles you intend. Paste tenant ID, client ID, and secret in Telara.

Permissions Telara requests

https://management.azure.com/.default
OAuth 2.0

In Telara

Connect in Telara

OAuth 2.0

Azure AD OAuth2 client credentials flow. tenant_id and subscription_id are required alongside the OAuth token.

In Telara, open Settings → Integrations, choose this connector, and click Connect. Telara sends you to the vendor to approve access, then returns you here. You do not create an OAuth app or paste a client secret.

Fields Telara asks for

Tenant Id
Subscription Id

Custom

Azure service principal client credentials. The Go runtime exchanges these fields for a management API bearer token.

In Telara, open Settings → Integrations, choose this connector, and complete the fields Telara shows.

Fields Telara asks for

Client ID
Client secret
Tenant Id
Subscription Id

Knowledge

What gets indexed

Resource	Coverage
Resource inventory	Partial — not every record the vendor holds is synced
Resource inventory	Partial — not every record the vendor holds is synced

Sync

Freshness & sync

Resource	Lag	Deletions
Resource inventory	Up to 1 day	Removed records disappear on the next full sync
Resource inventory	Up to 1 day	Removed records disappear on the next full sync

Data handling

Permissions & data handling

The scopes above are the permissions this connector requests. They come from the catalog, not from a hand-written page.

Excluded from semantic search: Resource inventory.

After connect

Verify it worked

After you save, Telara runs a read-only check against the account. The integration shows as connected when that check succeeds.

Honesty

Known limitations

Tenant, subscription, and app ID mismatches are the usual failure — the credential authenticates on the wrong directory.

A Reader role that cannot list the resource types you care about produces an empty estate, not an auth error.