Fitting Puzzle Pieces Together: Insights from the Flexera 2024 State of ITAM Report

Brian Adler
Flexera

The complex landscape of IT asset management (ITAM) presents evolving challenges — and noteworthy achievements. The Flexera 2024 State of ITAM Report offers a deep dive into how ITAM is evolving. Based on insights from over 500 IT professionals, the report underscores the need for improved collaboration and visibility to optimize IT investments.

At the forefront of this year's findings is the critical gap between software asset management (SAM) and FinOps (cloud financial management) teams. This year, 32% of SAM teams reported having significant interactions with FinOps teams. While this marks an improvement from last year's 25%, it highlights the persistent challenge of integrating these two essential functions that both emphasize cost optimization as part of an important and broad set of initiatives, including lifecycle management, tracking of inventory, software versioning, and more.

Without this integration, organizations risk inefficiencies and missed opportunities for cost savings. As the analogy goes, companies have all the puzzle pieces but have yet to start putting them together. When IT asset management teams are flexible, manage a comprehensive view of the enterprise's data, and share actionable data-driven insights with other teams in the enterprise, great efficiencies are possible.

1. COLLABORATION IS GROWING, BUT IS INSUFFICIENT

Saving the almighty dollar is more important than ever. Finding those dollars to save, wherever possible, is going to be looked on in a positive light. ITAM folks are trying to find where to do that; FinOps teams have historically been trying to do that. We're heading in the right direction, but more collaboration is necessary.

Today there's a lack of significant interaction between SAM and FinOps teams, making it a major concern. Despite the improvement from last year, collaboration is still far from where it needs to be. Organizations have gathered the right people, but have not yet figured out how to bring responsibilities and goals together effectively. This disjointed approach can lead to inefficiencies and missed opportunities for optimization across IT investments.


Improved cross-team collaboration between ITAM (including SAM) and FinOps will deliver efficiencies in the coming years. Working together is an essential part of illuminating — and eliminating — the significant visibility gap regarding licenses for software running in the cloud.

Collaborative efforts for SAM teams are important for various focus areas, including infrastructure and operations, security, cloud (including cloud central teams and cloud centers of excellence). For example, the report's findings also show that only 19% of respondents feel secure in their BYOL (bring your own license ) positioning. This low confidence indicates that BYOL efforts are a significant area where better integration and visibility could drive improvements.

2. CLOUD SERVICES AND LICENSING COMPLEXITIES ADD TO THE NEED FOR GREATER VISIBILITY

Cloud environments add another layer of complexity to ITAM, particularly concerning various licensing models and discount options. The resource costs and the licensing implications must both be considered when optimizing cloud environments.

Consider this example: a company is running Microsoft SQL Server workloads in Azure. If the workloads would be moved to reserved instances without considering the associated licenses, the company could have saved on instance costs, but would have incurred higher overall expenses due to new licensing requirements.

CCOEs provide a centralized approach to managing an organization's cloud journey. Enterprises are wise to include ITAM practitioners in their CCOEs in order to ensure that licensing is incorporated into cloud-cost planning and deployment. Today 72% of organizations have a central cloud team, such as a CCOE; 88% of CCOEs have an ITAM/SAM member on the team, helping guide an organization's cloud journey.

While cloud providers offer tools to help manage and optimize cloud costs, many organizations find these tools insufficient as they mature in their cloud journey. Initially, provider tools like AWS Trusted Advisor and Azure Cost Management can be beneficial, but as organizations grow, they often outgrow these tools and seek more comprehensive third-party solutions.


3. VENDOR AUDITS MAY CAUSE SIGNIFICANT FINANCIAL IMPACT

A positive trend is highlighted in this year's report: a decline in wasted IT spend. Historically, wasted spend has been a significant issue, but this year's report shows a decrease below the 30% threshold. This reduction is encouraging, indicating that organizations are becoming more efficient in managing their IT assets.

However, the financial impact of vendor audits remains significant. The report shows that more than 20% of respondents spent more than $5 million in software vendor audit costs over the past three years. This substantial expenditure underscores the need for robust ITAM practices to avoid such costly audits, particularly as major vendors (including IBM, Oracle, and ServiceNow) increase their audit activities. Perhaps unsurprisingly, responding to these audits is now the top initiative for ITAM teams that report to the CIO or CTO.

Being proactive — getting your internal house in order — allows you to worry less about external audits. Internal audits not only help ensure that you're in a good state; they reduce the time and money spent on external audits.


Broad Responsibilities, Broad Benefits

The report underscores the critical need for improved collaboration and visibility within ITAM practices. Today's ITAM professionals take on a broad range of responsibilities, including tracking ownership of SaaS usage, providing security analysis, getting ready for contract renewals, and maintaining software licensing inventories. As organizations continue to navigate the complexities of modern IT environments, integrating ITAM initiatives into FinOps and other initiatives, leveraging advanced tools, and enhancing data visibility will all be essential for optimizing IT investments and driving operational efficiency.

Brian Adler is Senior Director of Cloud Market Strategy at Flexera

Related Links

Hot Topics

The Latest

Implementing AI Isn't the Hard Part Anymore - Adoption Is

Two years ago, almost every customer conversation about AI started with the same questions: Which model should we use? What can it do? Is it ready for the enterprise? Today, those discussions have moved on. CIOs are far more interested in how to govern AI, integrate it with existing systems, prepare their workforce and make it part of everyday operations. The challenge is no longer to prove that AI can deliver value. It's instead about how to embed AI into the business in a way that's secure, scalable and delivers measurable outcomes ...

 

The Incident Load Is Rising, but Recovery Times Aren't Moving

Two things happened to production incidents between 2023 and now, and they did not happen at the same speed. The first is that a class of dependency that barely existed three years ago now accounts for one incident in ten. Incidents disclosed by AI model and AI application providers rose from 1.7% of all disclosed unplanned incidents in 2023 to 10.7% in 2026 year to date, roughly a sixfold rise; that counts only incidents at AI companies themselves, so the true share is higher. The second is that the time to close an incident has not come down ...

Your AI Pipeline May Have a Document Observability Problem

When an AI assistant gives an incomplete or incorrect answer, teams often blame the model. They adjust prompts, switch models, increase context windows or test a new retrieval strategy. However the model may not be a problem. In many enterprise AI workflows, the problem begins inside the document-ingestion pipeline ...

The SIEM Isn't the Problem. Your Telemetry Architecture Is

If you talk to any security or observability teams right now, they're all fighting the same fire: their tooling was built to ingest X, but their sources are pumping Y and soon to be doing Z. The knee-jerk reaction is always the same: we need more platform. However, this reaction is wrong. Let me explain why, because the solution to this problem is foundational, not financial. Instead of hurling yet more money at the problem, make sure you've done what's needed upstream ...

As AI Scales Across Enterprises, Breaking Points Emerge

Rapid AI adoption and the unique ways AI workloads operate is redefining the scope and structure of what these teams must deliver. This shift is forcing organizations to rethink how they manage scale, automation, and control, according to The State of SRE and Platform Engineering 2026, a new report from Dynatrace ...

Preparing Network Infrastructure for AI Starts with the Basics

AI is usually talked about as a software tool, but it also depends heavily on the network behind it. Whether a company is using AI for chatbots, automation, monitoring, analytics, or employee support, all of that information has to move across the network in a reliable and secure way. That means AI is not just an application decision. It is also an infrastructure decision. Before organizations rush into AI, they should ask a simple question: Is our network ready to support it? ...

Agentic Operations Begin with Governed Middleware Access

Enterprise AI often lacks governed access to where business processes actually execute. Without that access, AI agents may be able to reason, but they cannot operate reliably across enterprise workflows. For AI agents to effectively carry out workflows, they will require integration-layer context and controls. Organizations can implement these prerequisites by providing AI with managed access to the middleware layer ...

The Network Data Problem Slowing Down Enterprise AIOps

Enterprise networks rarely behave the same way for very long. A routing adjustment in one region may unexpectedly alter application performance in another. A cloud migration may introduce hidden dependencies that go unnoticed until an outage occurs. All the while, the network is managed by several different teams, each of whom use different tool sets — and as a result, have different views of the network ... There’s usually an engineer who remembers why traffic fails over a certain way between sites, or which transparent firewall was added where. The problem is that human memory cannot scale alongside enterprise-scale networks ...

The Governance Gap Behind AI's Infrastructure Problem

Ask an infrastructure team how confident they are in their ability to govern AI, and most will tell you they've got it handled. A recent survey of 406 IT decision-makers and platform engineering leaders found 86% expressing exactly that confidence. Ask the same group whether they have a formal written AI governance policy, and the number drops to 30%, according to Spacelift's Infrastructure Automation Report ...

MEAN TIME TO INSIGHT Podcast - Episode 27: Observability Unification

In MEAN TIME TO INSIGHT Episode 27, Shamus McGillicuddy, EMA VP of Research, Network Infrastructure and Operations, and Parker Hathcock, EMA Research Director covering IT Service/Operations (ServiceOps), discuss observability unification in modern IT operations ... 

Fitting Puzzle Pieces Together: Insights from the Flexera 2024 State of ITAM Report

Brian Adler
Flexera

The complex landscape of IT asset management (ITAM) presents evolving challenges — and noteworthy achievements. The Flexera 2024 State of ITAM Report offers a deep dive into how ITAM is evolving. Based on insights from over 500 IT professionals, the report underscores the need for improved collaboration and visibility to optimize IT investments.

At the forefront of this year's findings is the critical gap between software asset management (SAM) and FinOps (cloud financial management) teams. This year, 32% of SAM teams reported having significant interactions with FinOps teams. While this marks an improvement from last year's 25%, it highlights the persistent challenge of integrating these two essential functions that both emphasize cost optimization as part of an important and broad set of initiatives, including lifecycle management, tracking of inventory, software versioning, and more.

Without this integration, organizations risk inefficiencies and missed opportunities for cost savings. As the analogy goes, companies have all the puzzle pieces but have yet to start putting them together. When IT asset management teams are flexible, manage a comprehensive view of the enterprise's data, and share actionable data-driven insights with other teams in the enterprise, great efficiencies are possible.

1. COLLABORATION IS GROWING, BUT IS INSUFFICIENT

Saving the almighty dollar is more important than ever. Finding those dollars to save, wherever possible, is going to be looked on in a positive light. ITAM folks are trying to find where to do that; FinOps teams have historically been trying to do that. We're heading in the right direction, but more collaboration is necessary.

Today there's a lack of significant interaction between SAM and FinOps teams, making it a major concern. Despite the improvement from last year, collaboration is still far from where it needs to be. Organizations have gathered the right people, but have not yet figured out how to bring responsibilities and goals together effectively. This disjointed approach can lead to inefficiencies and missed opportunities for optimization across IT investments.


Improved cross-team collaboration between ITAM (including SAM) and FinOps will deliver efficiencies in the coming years. Working together is an essential part of illuminating — and eliminating — the significant visibility gap regarding licenses for software running in the cloud.

Collaborative efforts for SAM teams are important for various focus areas, including infrastructure and operations, security, cloud (including cloud central teams and cloud centers of excellence). For example, the report's findings also show that only 19% of respondents feel secure in their BYOL (bring your own license ) positioning. This low confidence indicates that BYOL efforts are a significant area where better integration and visibility could drive improvements.

2. CLOUD SERVICES AND LICENSING COMPLEXITIES ADD TO THE NEED FOR GREATER VISIBILITY

Cloud environments add another layer of complexity to ITAM, particularly concerning various licensing models and discount options. The resource costs and the licensing implications must both be considered when optimizing cloud environments.

Consider this example: a company is running Microsoft SQL Server workloads in Azure. If the workloads would be moved to reserved instances without considering the associated licenses, the company could have saved on instance costs, but would have incurred higher overall expenses due to new licensing requirements.

CCOEs provide a centralized approach to managing an organization's cloud journey. Enterprises are wise to include ITAM practitioners in their CCOEs in order to ensure that licensing is incorporated into cloud-cost planning and deployment. Today 72% of organizations have a central cloud team, such as a CCOE; 88% of CCOEs have an ITAM/SAM member on the team, helping guide an organization's cloud journey.

While cloud providers offer tools to help manage and optimize cloud costs, many organizations find these tools insufficient as they mature in their cloud journey. Initially, provider tools like AWS Trusted Advisor and Azure Cost Management can be beneficial, but as organizations grow, they often outgrow these tools and seek more comprehensive third-party solutions.


3. VENDOR AUDITS MAY CAUSE SIGNIFICANT FINANCIAL IMPACT

A positive trend is highlighted in this year's report: a decline in wasted IT spend. Historically, wasted spend has been a significant issue, but this year's report shows a decrease below the 30% threshold. This reduction is encouraging, indicating that organizations are becoming more efficient in managing their IT assets.

However, the financial impact of vendor audits remains significant. The report shows that more than 20% of respondents spent more than $5 million in software vendor audit costs over the past three years. This substantial expenditure underscores the need for robust ITAM practices to avoid such costly audits, particularly as major vendors (including IBM, Oracle, and ServiceNow) increase their audit activities. Perhaps unsurprisingly, responding to these audits is now the top initiative for ITAM teams that report to the CIO or CTO.

Being proactive — getting your internal house in order — allows you to worry less about external audits. Internal audits not only help ensure that you're in a good state; they reduce the time and money spent on external audits.


Broad Responsibilities, Broad Benefits

The report underscores the critical need for improved collaboration and visibility within ITAM practices. Today's ITAM professionals take on a broad range of responsibilities, including tracking ownership of SaaS usage, providing security analysis, getting ready for contract renewals, and maintaining software licensing inventories. As organizations continue to navigate the complexities of modern IT environments, integrating ITAM initiatives into FinOps and other initiatives, leveraging advanced tools, and enhancing data visibility will all be essential for optimizing IT investments and driving operational efficiency.

Brian Adler is Senior Director of Cloud Market Strategy at Flexera

Related Links

Hot Topics

The Latest

Implementing AI Isn't the Hard Part Anymore - Adoption Is

Two years ago, almost every customer conversation about AI started with the same questions: Which model should we use? What can it do? Is it ready for the enterprise? Today, those discussions have moved on. CIOs are far more interested in how to govern AI, integrate it with existing systems, prepare their workforce and make it part of everyday operations. The challenge is no longer to prove that AI can deliver value. It's instead about how to embed AI into the business in a way that's secure, scalable and delivers measurable outcomes ...

 

The Incident Load Is Rising, but Recovery Times Aren't Moving

Two things happened to production incidents between 2023 and now, and they did not happen at the same speed. The first is that a class of dependency that barely existed three years ago now accounts for one incident in ten. Incidents disclosed by AI model and AI application providers rose from 1.7% of all disclosed unplanned incidents in 2023 to 10.7% in 2026 year to date, roughly a sixfold rise; that counts only incidents at AI companies themselves, so the true share is higher. The second is that the time to close an incident has not come down ...

Your AI Pipeline May Have a Document Observability Problem

When an AI assistant gives an incomplete or incorrect answer, teams often blame the model. They adjust prompts, switch models, increase context windows or test a new retrieval strategy. However the model may not be a problem. In many enterprise AI workflows, the problem begins inside the document-ingestion pipeline ...

The SIEM Isn't the Problem. Your Telemetry Architecture Is

If you talk to any security or observability teams right now, they're all fighting the same fire: their tooling was built to ingest X, but their sources are pumping Y and soon to be doing Z. The knee-jerk reaction is always the same: we need more platform. However, this reaction is wrong. Let me explain why, because the solution to this problem is foundational, not financial. Instead of hurling yet more money at the problem, make sure you've done what's needed upstream ...

As AI Scales Across Enterprises, Breaking Points Emerge

Rapid AI adoption and the unique ways AI workloads operate is redefining the scope and structure of what these teams must deliver. This shift is forcing organizations to rethink how they manage scale, automation, and control, according to The State of SRE and Platform Engineering 2026, a new report from Dynatrace ...

Preparing Network Infrastructure for AI Starts with the Basics

AI is usually talked about as a software tool, but it also depends heavily on the network behind it. Whether a company is using AI for chatbots, automation, monitoring, analytics, or employee support, all of that information has to move across the network in a reliable and secure way. That means AI is not just an application decision. It is also an infrastructure decision. Before organizations rush into AI, they should ask a simple question: Is our network ready to support it? ...

Agentic Operations Begin with Governed Middleware Access

Enterprise AI often lacks governed access to where business processes actually execute. Without that access, AI agents may be able to reason, but they cannot operate reliably across enterprise workflows. For AI agents to effectively carry out workflows, they will require integration-layer context and controls. Organizations can implement these prerequisites by providing AI with managed access to the middleware layer ...

The Network Data Problem Slowing Down Enterprise AIOps

Enterprise networks rarely behave the same way for very long. A routing adjustment in one region may unexpectedly alter application performance in another. A cloud migration may introduce hidden dependencies that go unnoticed until an outage occurs. All the while, the network is managed by several different teams, each of whom use different tool sets — and as a result, have different views of the network ... There’s usually an engineer who remembers why traffic fails over a certain way between sites, or which transparent firewall was added where. The problem is that human memory cannot scale alongside enterprise-scale networks ...

The Governance Gap Behind AI's Infrastructure Problem

Ask an infrastructure team how confident they are in their ability to govern AI, and most will tell you they've got it handled. A recent survey of 406 IT decision-makers and platform engineering leaders found 86% expressing exactly that confidence. Ask the same group whether they have a formal written AI governance policy, and the number drops to 30%, according to Spacelift's Infrastructure Automation Report ...

MEAN TIME TO INSIGHT Podcast - Episode 27: Observability Unification

In MEAN TIME TO INSIGHT Episode 27, Shamus McGillicuddy, EMA VP of Research, Network Infrastructure and Operations, and Parker Hathcock, EMA Research Director covering IT Service/Operations (ServiceOps), discuss observability unification in modern IT operations ...