IT Visibility: TI reporting - New Report Release Update

Container Inventory Overview – Live Now!

The Container Inventory Overview report introduces a comprehensive view of containerized environments within the TI platform, enabling customers to gain structured visibility into their container ecosystem—from underlying infrastructure to container-level insights.

Note: As part of this release, the report focuses on Kubernetes container environments, providing comprehensive visibility across your Kubernetes ecosystem. Stay tuned, as we're actively enhancing this experience in future releases by expanding support to Podman and Docker environments, while also bringing in Container Software visibility extending the report beyond infrastructure and runtime into the software layer inside containers.

Problem Statement

Customers face limited visibility and fragmented insights into their container environments, making it difficult to answer key questions such as:

• What containers are running across the environment?
• How are they structured across clusters, nodes, and pods?
• Where are these workloads running?
• What is their operational and lifecycle state?

What’s New

1. Container Visibility

• Introduces containers as a first-class reporting entity within the platform
• Provides a consolidated view of clusters, nodes, pods, and containers
• Bridges the gap between raw container data and actionable insights

2. Container Ecosystem Intelligence (What / Where / Structure / State)

• What: KPIs for total clusters, nodes, pods, and containers
• Where: Distribution across clusters, nodes, and pods
• Structure: Hierarchical mapping (Cluster → Node → Pod → Container)
• State: Running vs terminated containers with restart insights

Outcome: Enables customers to move from fragmented visibility to a structured understanding of their container ecosystem.

3. Infrastructure & Lifecycle Insights

• Hardware visibility: Manufacturer, model, and product distribution
• Lifecycle tracking: Node Hardware Lifecycle stages such as GA, End of Sale, and Obsolete
• Risk visibility: Identification of nodes approaching obsolescence
• Infrastructure context: OS, CPU, memory, storage, location, business unit, and cost center
• Workload distribution: Containers, pods, and nodes across clusters

Outcome: Connects container workloads with underlying infrastructure risk, lifecycle, and scalability insights.

4. Container Ecosystem Analytics

• Hierarchical visualization of container environments
• Node-level mapping of container deployments
• Container growth and churn tracking over time
• Restart indicators to highlight instability
• Pod-level health and status visibility

Outcome: Enables customers to monitor container health, understand adoption patterns, and track operational stability.

5. Drill-Through & Detailed Inventory

• Seamless drill-through across:
  • Clusters → Nodes → Pods → Containers
• Detailed metadata views for deeper analysis

Outcome: Empowers platform, infrastructure, and operations teams to move from visibility to actionable decision-making.

Key Value Delivered

• Transforms fragmented container data into a structured ecosystem view
• Converts raw metadata into meaningful operational insights
• Connects infrastructure and containers into a unified, end-to-end story
• Enables better governance, planning, and optimization of container environments

Release Date: 06/30/2026

Product Documentation: https://docs.flexera.com/flexera-one/it-visibility/it-visibility-with-tip-reports/working-with-tip-reports/technology-intelligence-platform-report-descriptions/container-inventory-overview, https://docs.flexera.com/flexera-one/it-visibility/it-visibility-with-tip-reports/understanding-report-types, https://docs.flexera.com/flexera-one/it-visibility/it-visibility-with-tip-reports/working-with-custom-reports/working-with-measures, https://docs.flexera.com/itam-discovery/gathering-flexnet-inventory/k8s-agents

Release Notes: https://docs.flexera.com/flexera-one/feature-list/new-features-in-2026/june-2026

IT Visibility: Full Transparency into File Evidence UI

Software Evidence UI has been enhanced to display all file evidence collected from your environment, giving you a complete view of your discovery data. 

What's New? 

File evidence is now grouped into three categories: 

• Active (Technopedia Mapped): Recognized and mapped to a known software product. 
• Unrecognized: Collected but not currently mapped to Technopedia. 
• Irrelevant: Excluded from recognition of workflows.  
• A supporting Irrelevant Reason column is now available in both the UI and CSV exports. 

These categories are visible in Devices (Inventory > IT Visibility Devices > Devices > File Evidence tab) and Software Evidence (Applications & Evidence > IT Visibility Software > Software Evidence > File Evidence tab) 

How the UI Works 

• File evidence is pre-filtered to Active by default. Unrecognized or Irrelevant evidence can be selected as required. 
• Summary counts at the top of the page reflect only Active (Technopedia Mapped) file evidence, so your existing recognition metrics remain unchanged. See more details below in Understanding File Evidence Recognition. 

Understanding File Evidence Recognition 

File evidence is a supplementary data source in IT Visibility, useful for validating executables, troubleshooting, and supporting investigative workflows. It is not the primary path for software recognition, which is driven by installer-based evidence and Technopedia normalization. As a result, a large volume of unmapped file evidence is expected and does not indicate a recognition issue. The new categorization simply provides greater visibility into your raw file evidence data. 

Learn More 

For a detailed explanation of file evidence categories, recognition rates, and FAQs, refer to our KB article: Understand file evidence in IT Visibility: Recognition, eligibility, and what to expect

For questions, please contact Flexera Support. 

Release Date: 29th June, 2026

Product Documentation: https://docs.flexera.com/flexera-one/it-visibility/identifying-devices-using-evidence

https://docs.flexera.com/flexera-one/it-visibility/identifying-applications-using-evidence

Release Documentation: https://docs.flexera.com/flexera-one/feature-list/new-features-in-2026/june-2026#updates-to-file-evidence-on-the-device-detail-and-software-evidence-pages

IT Visibility: TI reporting Updates

Report Replication Across Organizations - Live Now!

Feature Overview

The TI Platform now supports Report Replication Across Organizations, enabling authorized users to efficiently replicate custom and out-of-the-box reports from one organization to multiple destination organizations. This capability reduces manual effort, improves reporting consistency, and accelerates report deployment at scale.

What's New

Replicate Reports Across Multiple Organizations

Users can now clone an existing report and distribute it to one or more destination organizations through a guided replication workflow.

Comprehensive Report Structure Replication

The replication process preserves the complete report design and configuration, including:

• Report visuals (charts, KPIs, tables, and other report elements)
• Report layout and visual positioning
• Filters and slicers
• Report-level configurations and settings
• Report metadata, including source organization and creator information

This ensures a consistent reporting experience across organizations without requiring manual recreation.

Permissions & Access

The Report Replication capability is available to users with Manage Custom Reports permissions, helping to ensure that report replication activities are performed only by authorized users.

Replication Workflow

• Navigate to Reports and select a Custom Report or Out-of-the-Box Report.
• Choose the Replicate option.
• Select one or more destination organizations.
• Define replication handling preferences:
  • Overwrite Existing Report
  • Create New Copy
  • Skip Existing Report
• Submit the replication request.
• Monitor replication progress and status for each destination organization.

Dependency Handling

Report Replication transfers the report structure and configuration only. The following are not replicated:

• Underlying datasets
• Data sources
• Organizational data

If the destination organization contains the required datasets and dependencies, the replicated report will function as expected.

If dependencies are unavailable, the report structure will still be imported successfully. Users will receive warnings or error messages identifying unresolved datasets, mappings, or configuration dependencies, allowing remediation after replication.

Enhanced Status Visibility

To improve troubleshooting and operational efficiency:

• Replication status is available for each destination organization.
• Hovering over a Failed or Error status displays detailed failure information.
• Error details help users quickly identify issues such as:
  • Missing permissions
  • Configuration conflicts
  • Missing datasets or dependencies
  • Replication processing errors

Benefits

• Reduces manual report creation and maintenance effort
• Improves consistency across organizations
• Accelerates report onboarding and deployment
• Supports scalable report governance and administration
• Provides greater transparency into replication outcomes and failures

Important Notes

• Report Replication copies report structure, configurations, and metadata only.
• Organizational data and datasets are not transferred during replication.
• Destination organizations must have the necessary data sources and dependencies available for full report functionality.
• Reports can be replicated to multiple organizations in a single operation, simplifying large-scale report rollouts.

Release Date: 06/29/2026

Product Documentation: https://docs.flexera.com/flexera-one/it-visibility/it-visibility-with-tip-reports/working-with-custom-reports/replicating-reports-across-organizations/  

Release Notes: https://docs.flexera.com/flexera-one/feature-list/new-features-in-2026/june-2026#replicate-custom-reports-across-organizations



ITV Data Explorer Drill-Downs are live - in-context entity detail without leaving the report

You can now click straight into any device or software row in a Data Explorer report and open a slide-out panel with the full, grouped detail for that entity without leaving the report or running a separate query.

Reports are great at breadth: lots of entities side by side. But the moment you need to understand one of them in depth, you used to hit a wall, navigate away, re-query, or ask someone to pull the detail by hand. Drill-downs close that gap. The depth is one click away, in the same view, so you can move from "what's across my estate?" to "tell me everything about this one device" in a single step.

Why it matters

Every context-switch costs an momentum. Jumping out to re-query, or waiting on someone else to pull the detail, is exactly where investigations stall and questions go unanswered. Drill-downs now keep that depth inline, so the person looking at the report is the person who gets the answer in the moment, without breaking flow and without a separate query. That's faster time-to-insight and a lot more self-service for you.

How it works

In a report you have built you can now click into:

• Device detail - core attributes (manufacturer, model, serial, memory, storage) plus grouped sections for business services, lifecycle, network adapters, operating system, processors, installed software, and sustainability metrics.
• Software detail - core attributes (manufacturer, product, version, edition) plus the associated device, lifecycle, taxonomy, installer evidence, and file evidence.

I am also looking for feedback so if there is any improvements you feel we can make to the data returned, please let me know!

Cloud Sustainability - Decarbonization Plan

• Surfaces current, actionable intelligence the moment a customer opens it:
  • Portfolio carbon grade (A+ to F) — overall Cloud Carbon score with region-level breakdown showing the path to improvement.
  • Top accounts by carbon impact — accounts graded C or below are auto-surfaced as prioritization targets, ranked by Carbon/Dollar efficiency ratio.
  • Cost and carbon savings opportunities — rightsizing recommendations across compute, database, and storage, each quantified with CO₂e reduction.
  • Region guidance — low-carbon regions (Norway, The Dalles, Paris) earn A+/A grades; higher-carbon regions surface as migration candidates, backed by Greenpixie-certified carbon intensity data.

This is the shift from "we know our emissions" to "we have a plan" — and the plan updates automatically as the cloud estate evolves.

Where to Find More Information:

March 2026 Release Notes

SBOM in Flexera One IT Visibility — now GA!

We’re excited to announce the General Availability (GA) of SBOM ingestion and inventory management—now enhanced with automated obsolete data handling.

With this release, you can:

✅ Ingest and normalize SBOM data alongside traditional inventory

✅ Gain deeper visibility into software components and dependencies

✅ NEW: Automatically clean up stale SBOM data with configurable expiry / auto-delete settings

No more manual cleanup. No more outdated inventory lingering in the system.

This is a big step toward trusted, accurate, and unified visibility across modern software supply chains

Documentation:

• Release notes
• SBOM upload docs
• Auto-delete configuration

Configurable Inactivity Timeout 

Release Date: July 2, 2026

We’re introducing a new setting that allows organisations to customise their inactivity timeout in Flexera One.

Previously, users were automatically logged out after 30 minutes of inactivity, which many customers found too restrictive especially during longer tasks such as analysis, meetings, or operational workflows.

With this update, Organisation Admins can configure the timeout between 30 minutes and 6 hours, while the default remains set to 30 minutes.

What’s Changed

• Organisation Admins can now adjust inactivity timeout settings
• Timeout can be configured between 30 minutes and 6 hours
• New setting available in Administration → Platform Settings Section→ Manage Inactivity Timeout

Why This Matters

• Greater flexibility to support longer workflows without interruption
• Helps organisations align session behaviour with internal security policies
• Balances usability and security, rather than relying on a fixed timeout

Stay Ahead of IBM Sub-Capacity Compliance: Introducing IBM SubCapacity Technology Eligibility

We’re excited to announce a major enhancement in the ITAM June 2026 release: full visibility into IBM sub-capacity licenses and the inventory devices running end-of-support (EOS) operating systems and virtualization technologies, enabling organisations to reduce compliance risk, maintain sub-capacity eligibility, and proactively plan upgrades of technologies that are EOS or announced to be EOS in the future for IBM sub-capacity licensing.

With this release, you can quickly pinpoint sub-capacity licenses and related inventory devices running operating systems or virtualization technologies that have already reached EOS or are scheduled to within the next 180 days so you can act before compliance becomes a concern.

IBM regularly refreshes the list of operating systems and virtualization technologies ineligible for sub-capacity licensing, removing versions that have reached end of standard support (EOS) from their vendors. Once removed, these technologies are no longer supported by the IBM License Metric Tool (ILMT). Customers typically have a 180-day window to migrate to supported versions, although in some cases the effective removal date may extend further with compliance still required by the specified deadline.

To help customers stay informed and plan upgrades proactively, IT Asset Management June 2026 release leverages IBM EOS lifecycle data to automatically flag inventory devices linked to IBM sub-capacity licenses that are running operating systems or virtualization technologies which have reached or are approaching EOS. For more details, see the online documentation.

ITAM Continued Tracking with Backward Compatibility

IT Asset Management (including FNMS) continues to support inventory agent versions that work with EOS operating systems and virtualization technologies. That means uninterrupted resource usage inventory data collection and ingestion for accurate sub-capacity license calculations even while you’re transitioning to supported platforms.

What’s new in this release:

Enhanced Compliance Visibility

Gain clearer visibility into devices running EOS operating systems or virtualization technologies tied to IBM sub-capacity licenses. A new license alert now appears on applicable sub-capacity license types whenever related inventory devices are running EOS technologies.

The new alert “This license has one or more devices running technology that IBM has declared ineligible for subcapacity licensing” appears for each affected sub-capacity license on the “All Licenses” page and within the license properties “Possible Issues” section, making it easy to spot licenses that may need EOS technology upgrades.

The License Consumption grid now includes a new filter showing the number of inventory devices running EOS operating systems or virtualization technologies giving you faster insight into where action is needed.

 IBM Sub-Capacity Peak and Current Consumption Reports Extended

Quickly identify non-compliant or at-risk environments where EOS technologies are in use. This makes it easier to plan upgrades proactively and have informed conversations with IBM about migration and upgrade timelines.

Note: The example screenshot below shows a PUV license consumption report, but the same applies to all IBM sub-capacity license types reports.

Dedicated EOS Visibility Report

The new IBM Ineligible Technology report delivers a single, consolidated view of devices running technologies that are already ineligible (where the removal date has passed) alongside those approaching a future removal date so you can stay ahead of operating system and virtualization technology upgrades.

Important Note: The IBM ineligible technology indicator is a risk indicator only. It does not automatically change how license consumption is calculated. You should review flagged devices and take appropriate action as required to remain compliant with IBM sub-capacity licensing requirements. Flexera recommends engaging with IBM to agree on upgrade timelines for EOS technologies, to maintain sub-capacity eligibility while transitioning from EOS platforms to supported versions.

This enhancement is available now in Flexera One ITAM with the June 2026 release, and will reach on-premises customers in FNMS On-Premises 2026 R1. Explore the new capabilities and strengthen your IBM sub-capacity compliance posture by proactively planning upgrades of EOS operating system and virtualization technologies.