Skip to main content

January 2026

Flexera One introduced the following new features and enhancements this month.

Administration​

Flexera One introduced the following new features and enhancements in January 2026.

Flexera One now supports Azure Tier-2 CSP (Indirect Reseller) MCA billing export ingestion​

note

This feature is available with Administration. If you would like this feature enabled, contact Flexera Support. For more information, see Contacting Flexera Support.

Customers who purchase Azure through a Tier-2 Cloud Solution Provider (CSP)—also known as an Indirect Reseller—under a Modern Commerce Agreement (MCA) are now supported. In this arrangement, the Tier-2 CSP works through a Tier-1 CSP, who owns the billing account and manages the relationship with Microsoft. Previously, onboarding was limited because Tier-2 CSPs did not have direct access to the billing account.

With this feature, Flexera One introduces a subscription scoping mechanism that enables onboarding of Azure Tier-2 CSP customers by allowing ingestion of Azure billing exports without requiring a billing account ID. Customers can now ingest billing exports independently, without relying on a Tier-1 CSP. By ingesting this data, customers gain visibility into their Azure spending, empowering them to manage cloud costs efficiently, avoid unnecessary expenses, and maximize savings.

For more information, see the "Subscription Scoping" section in Microsoft Cloud Solution Provider (CSP) Partner - Azure MCA (New) in the Flexera One Help.

Cloud Cost Optimization​

Cloud Cost Optimization introduced the following new features and enhancements in January 2026.

Rename Support for Rule-Based Dimensions​

note

This feature is available with Cloud Cost Optimization.

You can now rename your rule-based dimensions directly from the Rule-Based Dimensions page (Cloud > Administration > Rule-Based Dimensions). This enhancement helps you keep dimension names consistent with changing business terminology without needing to delete and recreate existing dimensions. To rename a dimension, open the action menu for any customer-defined dimension and select Rename Dimension. System‑defined dimensions cannot be renamed.

This release also improves guidance when creating dimensions. The updated help text in the Create New Dimension slide‑out now clearly communicates limits such as the maximum number of allowed dimensions and clarifies how effective dates are applied to rules lists.

Flexera One SaaS Management​

Flexera One SaaS Management introduced the following new features and enhancements in January 2026.

Smartsheet connector enhancement: Subscriptions and insights​

We’ve expanded the Smartsheet connector in Flexera One SaaS Management to deliver deeper visibility and improved control over your Smartsheet licensing.

  • Subscription management: You can now create and manage Smartsheet subscriptions directly in Flexera One. For customers with multiple Smartsheet plans, users are automatically mapped to the correct subscription based on their planID.

  • New user insights: A new custom insight highlights users with provisional membership, helping you identify free or non-paid licenses for optimization opportunities.

  • Enhanced user detail: Two new attributes—Seat Type and Sheet Creator—are now displayed in subscription user tables, giving you a clearer picture of user entitlements and capabilities.

  • Automated user mapping: New Smartsheet users are automatically added to the appropriate subscription, ensuring your data stays accurate without manual intervention.

  • Accurate license tracking: Changes such as user downgrades (e.g., Member > Viewer or Sheet Creator > No) are now fully reflected, supporting better governance and cost control.

Enhanced error details for SaaS connectors​

When setting up or managing SaaS connectors, you can now view detailed error information that identifies why a connection failed, such as expired tokens or invalid credentials. This enhancement replaces generic error messages and reduces the need to contact Support to diagnose common connection issues.

Errors are also surfaced through Recommended actions on the home page. This provides quick access to the affected connector for a fast resolution. In this initial release, detailed error information is available for the Microsoft 365 connector. Support for additional connectors will be expanded in future releases, delivering a more consistent and transparent troubleshooting experience.

Smartsheet connector​

Flexera One SaaS Management has introduced the Smartsheet connectors to help you automatically fetch and consolidate user activity data for better insights and governance.

Easily view Smartsheet user details and seat classifications, including Member, Provisional Member, Viewer, and Guest. This seat type information was not available in Flexera SaaS Manager but is now accessible under the application view in Flexera One SaaS Management. SAM managers can now distinguish paid from non-paid members, as Member seat type represents paid licenses.

HR roster integration in Flexera One SaaS Management​

We have introduced the HR roster configuration feature, enabling you to import your preferred HR roster list via CSV upload with the following capabilities:

  • Display key HR data such as employment status, start date, and end date
  • Flag users not included in the HR roster
  • Flag users who have left but still hold a subscription

Flexera One SaaS Management released the following feature and enhancements in January 2026.

New connector setup for Jira and Confluence​

Flexera One SaaS Management is introducing a major improvement to the way Jira and Confluence connectors are configured, making the process simpler and more secure. Previously, setting up these connectors required using two different authentication methods—OAuth 2.0 for most API calls and Basic Authentication for specific endpoints, such as retrieving the number of seats in Jira. This approach was necessary because, at the time, Atlassian only supported Basic Auth for certain data. However, it added complexity for users and increased security risks.

Atlassian has since introduced API tokens with granular scopes, providing a modern and secure way to access all required endpoints. With this update, Basic Authentication is being removed from the Jira connector. Users will now have two secure options for authorization: OAuth 2.0 or API Token with Scopes. The API token method requires creating a service account with appropriate permissions and generating a token, but it offers a streamlined and secure setup experience. For Confluence, Basic Auth remains necessary for seat-related APIs because these endpoints are not yet officially documented. Users can choose to skip this step and manually enter seat counts if preferred, and we’ve already submitted a request to Atlassian to make these APIs official.

This change delivers significant benefits: a simplified setup process, enhanced security by eliminating Basic Auth for Jira, reduced risk of configuration errors, and alignment with Atlassian’s latest standards. Overall, it ensures a better experience for customers and prepares the connectors for future improvements.

SaaS applications per user report​

Flexera One SaaS Management now introduces a Reports section, starting with a powerful new report that provides a centralized view of all applications assigned to a specific user:

  • Access the new Applications per User report under the Reports section
  • View every application linked to a user in one place to quickly assess license usage, detect redundant assignments, and ensure compliance
  • Apply filters such as Vendor, Application Category, Country, Department and other relevant fields for targeted analysis and advanced reporting

IT Asset Management

IT Asset Management released the following feature and enhancements in January 2026.

License consumption for stand-by Oracle databases​

Starting with this release, Oracle inventory has been enhanced to recognize primary/stand-by (also referred to as active/passive) database clusters, improving licensing accuracy and audit readiness. By linking cluster nodes as logical pairs, the system prevents false exceptions and ensures consistent reporting of options and packs across both nodes.

Previously, when reporting on Oracle instances, the primary node correctly showed a running database instance, while the stand-by node detected the database configuration but not a running instance. This resulted in an exception stating that no instance was running at the time of inventory collection.

With this enhancement, IT Asset Management now stores cluster pair information in the database. After reconciliation, the primary node continues to report a running instance, and the stand-by node is no longer flagged as missing a running Oracle instance because it is recognized as part of an primary/stand-by cluster pair.

For licensing purposes, Oracle databases can have one or more standby databases for a running database. If you have a standby database, you must license all Oracle options and packs running on the primary database for the standby database as well. Previously, scans on passive databases did not show all instances, which led to under-calculated consumption.

With this enhancement, IT Asset Management now merges enabled Oracle options and packs from both primary and stand-by databases:

  • If an option is used on the stand-by database but not on the primary database, it is still counted for consumption.
  • If an option is used on the primary database but not on the stand-by database, it is counted for consumption.
  • If an option is used on both, nothing changes.
  • If an option is used on neither, nothing changes.

New System Task and Health API endpoints​

Two new API endpoints have been added to the Flexera One Data ITAM to enhance data access and monitoring capabilities, providing improved visibility into system health and task execution.

These endpoints empower IT Asset Management customers with greater control by enabling automated checks on system health and task status. This reduces manual effort, boosts operational efficiency, and supports proactive monitoring for smoother IT Asset Management operations.

New API endpoints:

  • System Health Status: /Suite/SystemHealth
    • Delivers real-time insights into the overall health of your ITAM system.
  • System Tasks: /Suite/SystemTasks
    • Facilitates monitoring of system tasks for better operational awareness.

These endpoints are part of the ITAM Data API. For API documentation, refer to IT Asset Management Data API.

note

These updates apply to the API only; there are no UI changes in this release.

Service Accounts supported by Flexera One IAM API​

The Flexera One IAM API now supports service accounts, enabling customers and partners to authenticate to IAM APIs using non-human, role-based identities. This enhancement improves security, facilitates automation, and supports scalable, maintainable API integrations. Using the Flexera One IAM API users can create, view, update, and delete service accounts.

For details on IAM API endpoints that support service accounts, refer to the Identity and Access Management API documentation. To make requests against IAM API endpoints, a service account must have one or more of the following privileges (as listed in the API documentation).

To grant a service account the following privileges, assign the fnms_admin role:

  • fnms:application:index
  • fnms:asset:index
  • fnms:device:create
  • fnms:file:show
  • fnms:inventory:index
  • fnms:license:index
  • fnms:operator:index

To grant a service account the following privilege (which grants access to all endpoints), assign the org_owner role:

  • common:org:own

Once a service account is created by way of the API, visiting the All Accounts page triggers a sync process that creates corresponding compliance operator records.

For guidance on using service accounts with Flexera One APIs, see Using a Service Account With the Flexera One APIs.

Inventorying Azure Uniform VMSS instances​

IT Asset Management has been enhanced to support inventorying Virtual Machine Scale Sets (VMSS) created in Uniform Mode, complementing the existing support for Flexible Mode.

Previously, IT Asset Management only retrieved Flexible VMSS instances. With this update, it now collects both Uniform and Flexible VMSS instances. There are no changes to the user interface. Uniform VMSS instances will appear in the same location as Flexible ones on the Cloud Service Provider Inventory page in IT Asset Management.

The outcome remains the same: customers with Uniform VMSS instances will now see these automatically included alongside Flexible instances.

Tanium adapter now supports software usage tracking​

The Tanium adapter has been enhanced to track software usage data and imports it into IT Asset Management. This improvement enables IT Asset Management to capture and visualize application usage metrics, supporting better license optimization and compliance reporting.

Previously, the Tanium adapter collected data on computers, applications, file evidence, installer evidence, and cloud instances. However, it did not include application usage details, limiting organizations’ ability to make informed decisions about software utilization.

With this release, the existing PowerShell-based Tanium inventory adapter running on the FlexNet Beacon now gathers usage information and imports it into IT Asset Management. Customers can view the Last Used Date for tracked applications on the Inventory Device Properties page. This data is sourced directly from Tanium.

For detailed instructions on tracking software usage for Tanium applications, see Software usage tracking for applications in the Inventory Adapters and Connectors Reference user guide.

In Maintenance added to the list of hardware statuses​

A new hardware status, In Maintenance, has been added to the existing list of hardware statuses in IT Asset Management. This expands the current list, which includes statuses such as Disposed, In Transit, Purchased, and Installed, to better reflect the movement and tracking of hardware assets.

In Maintenance—This status applies to hardware assets that are undergoing repair or updates. It indicates the asset is temporarily out of regular use for servicing. For example, your laptop requires a new screen, so it has been collected for repair. You receive a loan device, and the original asset is marked as In Maintenance.

Description field added to the Report Builder for Cost Center​

The Description field under the Cost Center view is now available in the Report Builder.

Previously, this field was not visible in the Reporting Module, even though the data was captured in IT Asset Management under the Cost Center view.

With this update, reports generated through the Report Builder will now include the Cost Center Description column, providing greater clarity and detail.

Add custom asset types for multi-tenant databases​

Previously, when creating an asset type in IT Asset Management, users could only choose from predefined, out-of-the-box options provided by Flexera. These standard asset types were shared across all cloud tenants and could not be customized for individual tenant needs.

If a tenant defined a custom asset type, it became visible to all tenants sharing the same database. In other words, tenants in a shared database could not create unique asset types for their exclusive use.

This enhancement removes that limitation. Now, any tenant, whether on a shared or separate database, can have its own custom asset types. This allows customers to create bespoke asset types in multi-tenant environments without affecting other tenants.

note

Currently, new asset types cannot be added through the UI. To request this, customers should contact Flexera Support and raise a case. A future release will introduce self-service functionality, enabling customers to add custom asset types directly without Support involvement. Until then, all requests must go through Support.

New optional fields added to the Oracle Instances view​

The Oracle Instances view has been enhanced with several optional fields to provide deeper insights into active inventory devices that have one or more Oracle database instances installed on them across your organization.

The following fields are now available for inclusion:

  • Corporate unit
  • Cost center
  • Environment
  • Location
  • Licensable

For more details on the viewing Oracle Instances associated with active inventory devices, see Oracle Instances in the Online Help.

Changes to supported operating systems and compatibility with other products​

The following product versions have been added to the compatibility list of IT Asset Management with other products:

  • Citrix Virtual Apps server 7.2503
  • Citrix Virtual Desktops 7.2503
  • EdgeSight for Citrix Virtual Apps 7.2503
  • IBM License Metric Tool (ILMT) on IBM DB2 9.2.41
  • IBM License Metric Tool (ILMT) on Microsoft SQL Server 9.2.41.

For the full lists, see Prerequisite Software and Compatibility with Other Products in System Requirements and Compatibility.