Onaro™ONARO
OverviewImplementationExtraction guides

Documentation / Integrations / Azure OpenAI

Azure OpenAI connector

Beta — implemented and listed for early use. Confirm the first sync in a non-production window before relying on it for close.

Connect Azure Cost Management credentials to pull Azure OpenAI spend (Beta).

Status: Beta · Claim C-20

Overview

Connect Azure Cost Management credentials to pull Azure OpenAI spend (Beta).

Data pulled

  • Daily spend from Azure Cost Management for Azure OpenAI
  • Token and request counts are not provided by this path (recorded as zero)
  • Persisted as source_type=api_sync

Authentication & credential storage

Meridian stores the following fields for this connector (values encrypted at rest):

  • subscription_id
  • tenant_id
  • client_id
  • client_secret
  • resource_group (optional)
  • Credentials are encrypted with AES-256-GCM using a KMS-wrapped data encryption key (DEK) and stored in vendor_connections.credentials_encrypted.
  • Meridian never returns the plaintext key after save. Revocation is disconnect: deactivate or delete the vendor connection — sync stops and the encrypted blob is no longer used.
  • OAuth client-credentials fields are stored together in the encrypted credentials blob (no Azure portal password is stored beyond the client secret you provide).

Sync schedule & behavior

Azure Cost Management often lags 24–48 hours. Syncs automatically every 6 hours; manual sync anytime. There is no per-connection frequency setting.

Setup steps

  1. Register an app in Entra ID with Cost Management read access to the subscription.
  2. Enter subscription, tenant, client id/secret (and optional resource group) in Meridian Vendors → Azure OpenAI.
  3. Confirm spend rows after the Cost Management lag window.

Troubleshooting

  • Auth errors: verify client secret expiry and Cost Management Reader role.
  • Empty spend: wait 24–48h after usage; confirm the resource group filter if set.

Related