The Collibra integration now supports mapping multiple Collibra domains to a single warehouse.

Configure fine-grained MC domain to Collibra domain mappings from the integration edit page.

If a table sits in one of the mapped MC domains, Monte Carlo routes the monitor relationship to the corresponding Collibra domain; otherwise it falls back to the warehouse-level mapping.

If your team organizes its Collibra catalog across many domains — for example, one per data product — you can now sync data quality scores from Monte Carlo to the right Collibra assets across all of them.

Azure blob storage data stores now support OAuth authentication via a Microsoft Entra ID Service Principal, as an alternative to connection strings.

If your organization has disabled storage account keys, you can register and connect Azure blob data stores using service principal credentials, keeping the integration aligned with your cloud security posture.

Learn more here: https://docs.getmontecarlo.com/docs/create-and-register-an-azure-blob-data-store

The Monte Carlo Agent Toolkit now includes instrument-agent, a skill that automates your agent-side setup for Monte Carlo Agent Observability.

From a single prompt in your editor, the skill detects the AI libraries in use, installs the Monte Carlo OpenTelemetry SDK at compatible versions, places decorators that categorize LLM calls for evaluation, and verifies traces are landing in Monte Carlo.

Available in Claude Code, Cursor, VS Code, Copilot CLI, and Codex -- wherever you build. Install the Monte Carlo Agent Toolkit and run /instrument-agent in your agent codebase.

Learn more:

• https://docs.getmontecarlo.com/docs/agent-toolkit
  • https://github.com/monte-carlo-data/mc-agent-toolkit/blob/main/skills/instrument-agent/SKILL.md

You can now connect Monte Carlo directly to Claude — query alerts, explore lineage, create monitors, and troubleshoot data issues in plain English, right from your Claude workspace.

Find it here: search "Monte Carlo" in the Claude directory (claude app → customize → connectors → "+" )

Two changes make collection agent and data store onboarding simpler and more secure:

• The AWS IAM External ID is now generated and managed by Monte Carlo during provisioning. This aligns the integration with AWS's recommended pattern for cross-account IAM roles and closes the confused deputy gap.
• Agent and data store onboarding across all cloud platforms now follows a consistent two-step Provision → Enable flow, and a node is auto-provisioned for every new agent

P95 and P99 are now selectable in the Agent metric monitor aggregation dropdown, with support for both ML-based and manual thresholds. P50 remains available under the existing Median option.

Tail latency is where agent reliability problems show up, and a single slow tool call can drag down an entire run. With P95 and P99 alerting, you can monitor tail latency on your agents directly.

The Alerts page now includes a Triage alerts banner. With one click, an AI agent runs through selected alerts (up to 50, respecting your current filters) and prioritizes the alert feed into high, medium, and low confidence buckets.

This allows teams to prioritize alerts and spend time on the more critical problems first.

Each row has a View triage reasoning icon that opens a drawer with the agent's alert description, rationale, and confidence badges.

Alert detail pages now feature a first-class Triage agent section alongside the Troubleshooting agent, embedding the triage experience directly in the alert workflow.

The PR Agent now shows exactly how it calculates risk, broken down by category. This lets you customize how each factor is weighted to match your team's priorities.

The CI Agent now consumes the PR Agent's risk score directly, and introduces full policy management in the Monte Carlo UI: teams can set an installation-wide default gate threshold and add per-repo exception rules, with policies resolving in cascade order from your CI workflow configuration down through per-repo and installation-level UI settings.

To configure: Head to Monte Carlo Settings > GitHub Integration to access the new unified configuration page and adjust thresholds to fit your workflow.

Full documentation: https://docs.getmontecarlo.com/docs/github#risk-factor-weights

You can now control which of your audience recipient channels receive monitor change notifications — opt-in to these notifications via the UI, Notifications-as-Code (using the receive_monitor_changes flag), or the API. (Disabled by default)

When enabled, you'll be notified when a monitor using this audience is disabled, enabled, or deleted. This gives teams full control over which monitor lifecycle activity lands in their channel — so you only see the changes that matter to your workflow.

Learn more here:

• https://docs.getmontecarlo.com/docs/notifications-v2#monitor-change-notifications
  • Notifications-as-code: https://docs.getmontecarlo.com/docs/notifications-as-code-20
  • API: https://apidocs.getmontecarlo.com/#definition-CreateOrUpdateNotificationSetting

You can now subscribe to your Data Operations dashboard and receive a recurring email digest, so your team stays on top of data health without having to log in.

Subscribers get a scheduled summary of dashboard state on a cadence you choose, making it easy to forward to teammates or bring into a recurring meeting.