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

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

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!

📢Question Roundup for this week[26th June ]: 

Hello Everyone,

Lots of activity this week across App Broker and FNMS, thank you to everyone contributing 🙌

🔧New responses:

 [App Broker]

Error codes from SCCM in AppBroker/AppPortal

View solution

Intune deployment showing as failed in App Broker (despite success)

View solution

[FNMS]

FNMS 2026 R1 Release availability

View response

❓Open questions

[FlexNet Manager Suite On-Premises]

• Config.ps1 Powershell error (FNMP 2019 R2)
• View question
• Database Upgrade Scripts  missing object 'PopulateInitialDataForDM_MT
• View question

[Admin Studio]

• Latest Microsoft OLE DB Driver 19 update
• View question

Thanks so much in advance for taking a look, every reply keeps the community moving forward

Mercedes

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