Reminder: IT Visibility Export/Parquet API Retirement (August 31, 2026)

Reminder that the legacy IT Visibility Export/Parquet API will be retired on August 31, 2026, as previously communicated in post

For customers still using the Export/Parquet API, final Parquet files will remain accessible for 90 days after retirement. Please transition to the Technology Intelligence Platform GraphQL API or Query API.

If you have any questions or need assistance with the transition, please contact support@flexera.com. 

Thank you for your continued partnership with Flexera. 

Official release of FlexNet Inventory Agent 26.2.0

We are pleased to announce the release of the FlexNet Inventory Agent 26.2.0.

Release Date: EU/AP: 2026-08-05, NA: 2026-08-12

This release includes:

• Support for alternative extraction tools on Azure Linux
• Kubernetes Remote Monitoring agent improvements
• Removal of obsolete OpenShift root extension
• Fix for macOS agent crash during bundle metadata parsing
• Fix for Unix software process cache limit
• Fix for network timeout preference being ignored
• Fix for Lightweight Kubernetes helm chart volume support
• Fix for KRM IBM Licensing Service scanning configuration
• Fix for KRM permission denied errors on persistent volumes
• Bundled software version updated

Customer Impact:

• Previously, the FlexNet Inventory Agent required the tar and awk utilities to extract and run on Linux containers, which are sometimes missing in Azure Linux environments. Now, the agent can fall back to using bsdtar and handles missing awk commands gracefully. This enhancement provides improved compatibility and reliability for inventory gathering in restricted container environments.
• Previously, the Flexera Kubernetes Inventory Agent (KRM) could experience instability in AKS environments due to transport issues and lacked granular timeouts for tracker execution. Now, KRM includes a global transport circuit breaker, improved platform detection for Azure, and hardened execution stages with specific timeouts. This enhancement provides greater resilience, reduced control-plane pressure, and more reliable image tracking across diverse cluster environments.
• Previously, the KRM installation included an OpenShift extension that allowed the agent to run as a root user. Now, this extension and its associated configurations have been removed as they are no longer required for modern deployments. This enhancement provides a more secure and streamlined installation process by adhering to least-privilege principles.
• Previously, the macOS agent would crash if bundle metadata contained a non-numeric "last modified" field. This release resolves this issue.
• Previously, the Unix software process cache did not have a fixed size limit, potentially leading to unbounded growth. This release resolves this issue.
• Previously, the agent's network timeout settings were not configurable, leading to potential communication failures under high load. This release resolves this issue.
• Previously, the Lightweight Kubernetes Agent (LWK) helm chart did not support volume mounts required for custom TLS certificates. This release resolves this issue.
• Previously, the Flexera Kubernetes Inventory Agent (KRM) helm chart would enable IBM Licensing Service scanning even when the property was explicitly set to false. This release resolves this issue.
• Previously, the Flexera Kubernetes Inventory Agent (KRM) could fail with a "permission denied" error when accessing its database on a PersistentVolumeClaim (PVC). This release resolves this issue.
• The libcurl, Expat, podman and Go third party libraries bundled with the agent have been updated in this release to address security vulnerabilities.

Product Documentation: Agent Documentation 

Please find more about the content of this release in the Release Notes.

Announcement: End of Life for FlexNet Inventory Agent Versions 17.x and 18.0.x

As part of Flexera’s product lifecycle policy, the FlexNet Inventory Agent versions 17.x and 18.0.x have reached the end of their supported lifecycle and are no longer supported. Those versions will no longer be available for download.

To ensure continued access to product enhancements, security updates, and technical support, Flexera recommends upgrading to a currently supported FlexNet Inventory Agent release as soon as possible. Customers running older agent versions should plan their upgrade strategy to maintain a supported and secure inventory collection environment.

For the latest lifecycle information and supported versions, please refer to the FlexNet Inventory Agent and Beacon End-of-Life Policy.

Official release of FlexNet Inventory Agent 26.1.0

We are pleased to announce the release of the FlexNet Inventory Agent 26.1.0.

Release Date: EU/AP: 2026-07-8, NA: 2026-07-15

This release includes:

• Detection of software installed in user profiles on Windows and macOS
• Detection of GPU, TPU, AI ASIC, and NPU hardware
• Collection of javaw executables
• Extension of KRM controller-managed resources via ConfigMap
• Fix for Flexera Kubernetes Inventory Agent least privilege support in AWS public ECR
• Fix for Windows agent HTTP module TLS 1.2 support on older servers
• Fix for KRM node inventory NDI file deletion
• Fix for k8s-node NDI file naming
• Fix for stuck uploader tasks during network issues
• Fix for agent service startup in least privilege mode on Unix-like systems
• Fix for inventory gathering crash with Unicode characters on Windows
• Fix for automounted filesystems during mvfs inventory gathering
• Fix for CPU and memory usage spikes during error logging
• Fix for Linux agent self-upgrade service startup
• Fix for incorrect exclusion of directories containing network shares
• Fix for web proxy upload failures
• Fix for WMI query errors in NDI files
• Fix for Kubernetes agent Helm chart monitor.logLevel setting
• Fix for agent installation failure on non-English Windows OS
• Bundled software version updated

Customer Impact:

• The FlexNet Inventory Agent has been enhanced to detect software installed in user profiles on on Windows and macOS. This enhancement provides more complete software inventory coverage.
• The FlexNet Inventory Agent has been enhanced to detect and report GPU, TPU, AI ASIC, and NPU hardware components. This enhancement provides more complete hardware inventory coverage.
• The FlexNet Inventory Agent has been updated to collect evidence of the javaw binary when the PerformOracleJavaAuditScan setting is set to true. This enhancement provides more comprehensive coverage for Oracle Java audits.
• The Flexera Kubernetes Inventory Agent (KRM) has been enhanced to provide greater flexibility when configuring controller-managed resources through the agent ConfigMap. This enhancement provides teams with the ability to extend and manage resources handled by the KRM controller without requiring changes to the agent deployment itself.
• Previously, the Flexera Kubernetes Inventory Agent (KRM) would not work with the AWS public ECR image when run in least privilege mode. This release resolves this issue.
• Previously, the FlexNet Inventory Agent was unable to upload files from Windows Server 2008 and 2012. This release resolves this issue.
• Previously, KRM node inventory would not delete the last uploaded NDI file. This release resolves this issue.
• Previously, the file name of k8s-node NDI files was always fixed at the node pod start time, rather than reflecting the inventory date. This release resolves this issue.
• Previously, ndupload could become stuck when encountering network issues. This release resolves this issue.
• Previously, FlexNet Inventory Agent services could fail to start on Unix-like operating systems when the FlexNet Inventory Agent was configured to run in least privilege mode and the shell for the flxrasvc user was configured as /usr/sbin/nologin. This release resolves this issue.
• Previously, the FlexNet Inventory Agent could crash while scanning folder and file names containing Unicode characters on Windows operating systems. This release resolves this issue.
• Previously, a large number of automounted filesystems could be mounted when gathering inventory details about mvfs file systems that point back into autofs mounts. This release resolves this issue.
• Previously, FlexNet Inventory Agent processes could encounter CPU and memory usage spikes in situations where logging an error resulted in another error, such as when the filesystem containing log files is full. This release resolves this issue.
• Previously, the agent for Linux could fail to start automatically after a self-upgrade from an older version that used /etc/init.d instead of systemd. This release resolves this issue.
• Previously, the agent would ignore folders that contained network share mounts. This release resolves this issue.
• Previously, uploads through a web proxy could fail with an error due to the agent mishandling proxy configuration settings containing trailing slashes. This release resolves this issue.
• Previously, WMI query errors would be collected as part of the NDI inventory file. This release resolves this issue.
• Previously, installing the Flexera Kubernetes Inventory Agent (KRM) using the Helm chart would not correctly set the monitor.logLevel setting. This release resolves this issue.
• Previously, the FlexNet Inventory Agent installation could fail with MSI error 1609 on non-English Windows operating systems if the built-in "Users" group name could not be converted without data loss to the currently configured "Language for non-Unicode programs". This release resolves this issue.
• The openssl and Go third party libraries bundled with the agent have been updated in this release to address security vulnerabilities.

Product Documentation: Agent Documentation 

Please find more about the content of this release in the Release Notes.

Cloud Sustainability – Turning Cost Optimization into Carbon Impact: CCO Recommendations Now Power the Carbon Optimizer Dashboard

Overview

Flexera One now automatically exports Cloud Cost Optimization (CCO) Usage Reduction Savings recommendations to Greenpixie for ingestion into the Carbon Optimizer Dashboard, enabling customers to translate cloud cost optimization actions into measurable sustainability outcomes.

Every rightsizing, idle-resource, and usage-reduction recommendation in CCO represents more than a cost-saving opportunity — it represents avoided carbon emissions, electricity consumption, and water usage. Until now, customers could see the financial impact of acting on these recommendations, but had no way to quantify the environmental impact of the same actions.

With this release, CCO Usage Reduction Savings recommendations flow directly into Carbon Optimizer, where Greenpixie's ISO 14064-certified methodology calculates the sustainability impact of each optimization opportunity. This is GreenOps in action: the same recommendation that saves money now also shows customers exactly how much carbon, electricity, and water it saves - at the resource level! 

What Is New

A new data platform job exports CCO Usage Reduction Savings recommendations to Greenpixie for the Carbon Optimizer Dashboard. Customers can now:

• Quantify the sustainability impact of cost optimization actions in three dimensions:
• Carbon savings (mtCO₂e)
• Electricity savings (kWh)
• Water savings (L)
• View sustainability impact across Azure, AWS, and GCP
• Translate every Usage Reduction Savings recommendation into an environmental outcome
• Bring cost and carbon decision-making into a single, unified motion

Why It Matters

Cloud optimization and cloud sustainability have historically lived in separate worlds. FinOps teams act on cost recommendations; sustainability teams report on emissions — often months later, from entirely different data. Customers making real progress on cloud efficiency had no credible way to claim the environmental benefit of that work.

This release closes that gap. By connecting CCO's optimization intelligence to Greenpixie's ISO 14064-certified carbon methodology, Flexera gives customers a defensible, resource-level answer to a question every sustainability leader is being asked: "What is our cloud efficiency work actually doing for our environmental commitments?"

It also deepens the Flexera + Greenpixie partnership, extending it beyond carbon visibility to Cloud Sustainability Impact Intelligence — moving customers from measuring emissions to quantifying the impact of actions.

Customer Value

• One action, two outcomes. The same rightsizing decision that reduces spend now carries quantified benefits in carbon, electricity, and water — no separate analysis, no spreadsheet math.
• Credible sustainability claims. Impact calculations are grounded in Greenpixie's ISO 14064-certified, bottom-up methodology — audit-ready, not spend-based estimates.
• A stronger business case for optimization. FinOps teams can now bring sustainability stakeholders into the optimization conversation, accelerating the adoption of previously stalled recommendations.
• Proven demand. This capability directly supports active customer use cases.

Key Benefits

• Delivers cost-to-sustainability translation for Usage Reduction Savings recommendations
• Enables Carbon Optimizer sustainability impact calculations across all three major clouds
• Strengthens chargeback, showback, and ESG reporting narratives with actionable impact data
• Advances Flexera's Carbon Like Cash vision, treating carbon with the same real-time rigor as cloud spend
• Reinforces Flexera's differentiated position as the only platform linking FinOps action to verified environmental impact

Your collaboration turned a data pipeline into a strategic capability, one that helps every Flexera customer see that optimizing the cloud and protecting the planet are the same motion.

Thank you for making it real.

-Mark

MSP Users Access Management with Access Policies in Flexera One – Live Now!

Partners with the Managed Service Provider capability can now centrally manage and enforce MSP user access across managed customer environments using Access Policies, enabling a consistent and scalable approach to access management in Flexera One. This feature simplifies operations and strengthens governance by allowing partners to:

• Define and apply access policies centrally across multiple managed customer organizations
• Assign groups of partner users to multiple managed customer organizations
• Standardize user permissions using policy-based controls
• Ensure consistent, compliant access enforcement at scale

This enhancement reduces administrative effort, improves security posture, and provides greater visibility and control over partner user access across partner-managed organizations.

Release Date: 07/06/2026

Product Documentation: Access Policy

Release Notes: Access Policy Release Notes

AI Spend and Tokenomics

Sustainability perspective: Tokenomics isn't just about cost; it's about what cost obscures.

Every AI prompt, every model call, every inference run has a price tag. Most teams are already tracking that cost. What they're missing is the carbon shadow beneath it, and that's where the deeper savings lie.

@MBradley​ put together a quick 3-minute overview of what we're calling Sustainable Tokenomics: how IT Sustainability gives AI Platform and FinOps teams a second lens on their AI investment, one that surfaces optimization opportunities that cost alone can't reveal.

Check out the video below

https://youtu.be/ybXr-LZU3og?si=ah8wSw0jrq8eAHPJ

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