# Inactive licensed users in Azure DevOps organization Canonical: https://www.pointfive.co/efficiency-hub/inefficiencies/inactive-licensed-users-in-azure-devops-organization Licensed Azure DevOps users remain assigned after individuals leave the organization or stop using the platform. By: Deepak Sreedhar Updated: 2026-09-28 [Cloud Efficiency Hub](https://www.pointfive.co/efficiency-hub) # Inactive Licensed Users in Azure DevOps Organization The short version Licensed Azure DevOps users remain assigned after individuals leave the organization or stop using the platform. [Deepak Sreedhar](https://www.linkedin.com/in/deepak-sreedhar-235260168) Azure FinOps Specialist @ Sodexo Azure service [Azure DevOps](https://www.pointfive.co/efficiency-hub/cloud-services/azure-devops) Category [Other](https://www.pointfive.co/efficiency-hub/service-category/other) Reference CER-0294 Type Idle or Unused Resource ## Explanation Why the waste happens and who it affects. These inactive users continue to generate recurring per-user charges despite providing no ongoing value, leading to unnecessary spend over time. ## Billing model The pricing dimensions that drive this cost. Azure DevOps charges per licensed user (e.g., Basic users) on a monthly basis. Licensed users incur cost regardless of activity level as long as the license remains assigned. The first five Basic users in an organization are free, Stakeholder access is free for an unlimited number of users, and users recognized as Visual Studio subscribers get access through their subscription rather than a paid Basic license. Savings therefore come from paid Basic (or Basic + Test Plans) assignments beyond the free allotment. ## How to detect 3 checks to find it in your estate. - Review whether licensed users have not accessed Azure DevOps for an extended period - Assess whether users are still actively contributing to projects or pipelines - Identify licenses assigned to former employees or role changes ## How to fix 3 ways to remove the waste. - Remove paid licenses from users who are no longer active, or downgrade them to free Stakeholder access if they still need limited access - Periodically review user access to ensure licenses align with current team needs - Assign paid licenses only to users who require full Azure DevOps capabilities ## Documentation Vendor references for pricing and configuration. - [Add users to organizations and manage access - Azure DevOps learn.microsoft.com](https://learn.microsoft.com/en-us/azure/devops/organizations/accounts/add-organization-users?view=azure-devops) - [Billing overview - Azure DevOps learn.microsoft.com](https://learn.microsoft.com/en-us/azure/devops/organizations/billing/overview?view=azure-devops) - [About access levels - Azure DevOps learn.microsoft.com](https://learn.microsoft.com/en-us/azure/devops/organizations/security/access-levels?view=azure-devops) ## Related inefficiencies [Browse the library](https://www.pointfive.co/efficiency-hub) - Azure Logic Apps CER-0309 ### [Idle or Untriggered Azure Logic Apps Generating Continuous Charges](https://www.pointfive.co/efficiency-hub/inefficiencies/idle-or-untriggered-azure-logic-apps-generating-continuous-charges) Azure Logic Apps can quietly accumulate costs even when no workflows are actively executing, but the mechanism differs significantly depending on the deployment model. In the Consumption (multitenant) plan, Logic Apps with polling triggers... Other - Azure Log Analytics CER-0424 ### [Unused Restored Tables in Log Analytics Workspaces](https://www.pointfive.co/efficiency-hub/inefficiencies/unused-restored-tables-in-log-analytics-workspaces) The Log Analytics restore operation brings a time range of data from long-term retention (or from any Analytics table) into the hot cache as a new table ending in \_RST, so that it can be queried with full KQL at high performance. It is... Other - Microsoft Fabric CER-0337 ### [Oversized Microsoft Fabric Capacity During Low-Utilization Periods](https://www.pointfive.co/efficiency-hub/inefficiencies/oversized-microsoft-fabric-capacity-during-low-utilization-periods) Microsoft Fabric capacity is billed based on the provisioned SKU tier (F2, F4, F8, F16, F64, etc.) on an hourly basis, regardless of whether workloads are actively consuming those resources. Each SKU tier provides a fixed pool of Capacity... Other --- Source: the public page above. Product screenshots and illustrative interfaces are examples, not live customer data.