# December 2025
URL: https://docs.datarobot.com/en/docs/release/cloud-history/2025-announce/dec2025-announce.html

> Read about DataRobot's new features, released in December 2025.

# December 2025

## December SaaS feature announcements

December 2025

This page provides announcements of newly released features available in DataRobot's SaaS multi-tenant AI Platform, with links to additional resources. From the release center, you can also access past announcements and [Self-Managed AI Platform release notes](https://docs.datarobot.com/en/docs/release/archive-release-notes/index.html).

### Agentic AI

#### BYO LLMs now available for select compliance tests

This release brings the ability to [customize the LLM](https://docs.datarobot.com/en/docs/agentic-ai/playground-tools/playground-eval-metrics.html#view-and-customize-datarobot-compliance-tests) used in assessing whether a response is appropriate. By default, DataRobot uses GPT-4o because of its performance, but for the following tests, the LLM is configurable.

- Jailbreak
- Toxicity
- PII

This broadens the usefulness of compliance tests for those organizations that prohibit use of GPT or those that want to employ a BYO LLM.

#### TogetherAI LLM deprecated

With this release, and as of November 28, 2025, TogetherAI's Mistral-7B-Instruct-v0.1 has been retired. See the [availability page](https://docs.datarobot.com/en/docs/reference/gen-ai-ref/llm-availability.html) for a full list of supported and retired LLMs.

### Predictions and MLOps

#### Access quota monitoring on the Usage tab

The Quota monitoring dashboard appears on the Usage tab for agentic and NIM deployments, providing visibility into API usage and rate limiting to help administrators track and manage quota consumption more effectively. This dashboard provides filterable charts and tables displaying information on total requests, total rate limited requests, total token count, and average concurrent requests for the deployment, including access to request tracing details.

For more information, see the [quota monitoring](https://docs.datarobot.com/en/docs/workbench/nxt-console/nxt-monitoring/nxt-usage.html#quota-usage-monitoring) documentation.

#### Custom association IDs and metrics in chat completion requests

For DataRobot-deployed text generation and agentic workflow custom models implementing the Bolt-on Governance API (chat completions), specify custom association IDs and report custom metrics directly within chat completion requests using the `extra_body` field. This enhancement provides more granular monitoring and governance capabilities for custom models integrated via DataRobot’s Bolt-on Governance API.

```
extra_body = {
    # These values pass through to the LLM
    "llm_id": "azure-gpt-6",
    # If set here, replaces the auto-generated association ID
    "datarobot_association_id": "my_association_id_0001",
    # DataRobot captures these for custom metrics
    "datarobot_metrics": {
        "field1": 24,
        "field2": 25
    }
}
completion = openai_client.chat.completions.create(
    model="datarobot-deployed-llm",
    messages=[
        {"role": "system", "content": "Explain your thoughts using at least 100 words."},
        {"role": "user", "content": prompt},
    ],
    max_tokens=512,
    extra_body=extra_body
)
print(completion.choices[0].message.content)
```

For more information, see the [Bolt-on Governance API](https://docs.datarobot.com/en/docs/agentic-ai/genai-code/genai-chat-completion-api.html) documentation.

#### Manage custom job environment

From the Assemble tab for a custom job, change the selected environment, update the environment version, or view the environment information. If a newer version of the environment is available, a notification appears, and you can click Use latest to update the custom job to use the most recent version with a successful build.

For more information, see the [custom job environment management](https://docs.datarobot.com/en/docs/workbench/nxt-registry/nxt-jobs-workshop/nxt-custom-job-env-version.html) documentation.

### Platform

#### View how assets are handled upon Use Case deletion

When you [delete a Use Case](https://docs.datarobot.com/en/docs/workbench/nxt-workbench/usecases/build-usecase.html#delete-a-use-case), DataRobot now displays a window detailing how each Use Case asset will be handled, specifically, which assets will be permanently deleted and which assets will be unlinked from the Use Case but remain accessible in Registry. This provides greater visibility into the effect of deleting a Use Case with assets already associated with it.

### Admin

#### Grant tenant-wide consent for Microsoft OAuth providers

This feature allows administrators to [grant tenant-wide consent](https://docs.datarobot.com/en/docs/platform/acct-settings/manage-oauth.html#organization-wide-consent-for-microsoft-oauth) for user permissions required by the DataRobot application in [Microsoft Entra ID](https://learn.microsoft.com/en-us/entra/identity/enterprise-apps/configure-user-consent?pivots=portal#configure-user-consent-in-microsoft-entra-admin-center). In Azure, by default, user permissions are not granted to individual user resources, requiring personal user consent when authorizing a [Microsoft OAuth provider](https://learn.microsoft.com/en-us/entra/architecture/auth-oauth2). When enabled, users also no longer receive consent prompts.

### Code first

#### Configure Kubernetes for notebooks

For Self-Managed and STS users, a notebooks' runner service now has the ability to configure (alter the default) Kubernetes liveness and startup probes.

#### Python client v3.11

Python client v3.11 is now generally available. For a complete list of changes introduced in v3.11, see the [Python client changelog](https://docs.datarobot.com/en/docs/api/reference/changelogs/py-changelog/index.html).

#### DataRobot REST API v2.40

DataRobot's v2.40 for the REST API is now generally available. For a complete list of changes introduced in v2.40, see the [REST API changelog](https://docs.datarobot.com/en/docs/api/reference/changelogs/rest-changelog/index.html).

All product and company names are trademarks™ or registered® trademarks of their respective holders. Use of them does not imply any affiliation with or endorsement by them.

---
