January 2026: Features Summary Preview

The January ’26 release focuses on strengthening the foundation enterprises rely on as technology cost, risk, and accountability continue to rise. These updates improve how asset data is trusted, governed, and acted on across IT, Finance, Security, and Compliance. Teams can detect issues earlier, reduce manual effort, and make decisions with greater confidence at scale.

Below is a preliminary list of the key features and enhancements that are currently targeted for inclusion in this release.

Oomnitza Guard - Limited Availability EAP

As asset environments grow, visibility becomes fragmented across hardware, software, identity, cloud, and financial systems. This makes it difficult to detect risk early, often resulting in overspend, audit findings, security exposure, and reactive cleanup.

Guard continuously detects anomalies across all asset classes — including shadow IT, catalog mismatches, and unusual asset behavior — so teams can address risk, cost leakage, and data drift before they cascade into operational, security, or compliance problems.

For customers interested in licensing Guard, please reach out to your Customer Success Manager.

Finance System Integrations

When financial data lives outside asset systems, teams rely on manual reconciliation to understand spend, slowing decisions and obscuring true cost.

New integrations for Ariba, Coupa, and Concur bring purchase order, invoice, and expense data directly into Oomnitza as structured records.
IT and Finance operate from the same source of truth, improving forecasting accuracy, renewal planning, and cost governance with less manual effort.

Integration Reliability and Credential Hardening

As cloud environments evolve, integrations that rely on static credentials make rotation slow, brittle, and dependent on support, increasing security risk and operational friction.

Building on the initial Direct Role Assumption foundation, AWS integrations now support automated credential lifecycle management with self-service regeneration, removing the need for support intervention.

Cloud teams can rotate credentials on demand, maintain stable integrations as account structures change, and meet security requirements with less overhead.

Workflow and Data Guardrails

As automation scales, bulk updates and rigid workflow routing can unintentionally corrupt data, bypass governance controls, or stall critical lifecycle processes.

This release strengthens platform guardrails by enforcing conditional visibility rules during bulk edits and imports and expanding notification and approval routing options across workflows.

Teams protect sensitive fields, reduce cleanup caused by accidental changes, and keep lifecycle workflows running reliably as usage and complexity increase.