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

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