The Feature Finder Problem: When SharePoint Features Slip into Obscurity

Features are the building blocks of SharePoint — whether a site is created via out-of-the-box prefab configurations or you've layered in custom Features and scripts. They’re powerful… until they disappear—or get misconfigured—and leave you guessing: What do I actually have?

I’ve experienced it plenty of times:

• Orphaned Features—those defined but not scoped properly—linger in the system, especially after migrations or updates.

• SharePoint doesn’t make it easy to list what’s installed, enabled, or orphaned.

• Using PowerShell like Get-SPFeature helps, but running and interpreting those scripts across a farm is time-consuming and error-prone.

  
  

In both SharePoint Online and on-premises, administrators often don’t have a clear, visual report of what Features are in play—nor which ones might be unsupported or orphaned.

How SharePoint Manages Features

• In SharePoint Server, you can use Get-SPFeature (optionally with parameters like -Site, -Web, -WebApplication, or -Farm) to list activated [Features.Microsoft Learn]

• Administrators often use PowerShell scripts to generate environment-wide Features reports—grouped by scope, display name, and more. [SharePoint DiaryThe Frog Pond of Technology]

• Orphaned Features, which have no defined Scope, can be listed with Get-SPFeature | where { $_.Scope -eq $null }, and potentially cleaned up—though caution is advised. [bits and bytesSharePoint Stack Exchange]

• In SharePoint Online, administrators can use CSOM-based PowerShell (via ClientContext) or the Get-PnPFeature command to list site and web scoped Features. [SharePoint Diary]

  
  

But still, these require scripting fluency and cross-environment checks. There’s no out-of-the-box UI that tells you everything clearly.

How the Commander Tool Solves the “Feature” Blind Spot

How Commander delivers major value:

• Unified feature visibility: See every Feature available, enabled, or disabled at both Site (collection) and Web levels—without running scripts or parsing logs.

• Legitimacy reference: Commander ships with a prebuilt inventory from a standard SharePoint 2013 farm. This gives you a baseline to spot unexpected or custom Features that may need validation.

• Inventory updates for newer farms: For environments beyond SP2013, Commander provides the required PowerShell script and clear instructions so you can refresh and align your baseline.

• Easy control: Enable or disable Features with a simple switch inside the dashboard—no deep-diving into Site Settings or Central Admin.

• Orphan detection: Instantly spot orphaned or unsupported Features that never clean themselves up, potentially surfacing upgrade risks before they become serious.

  
  

Why This Matters

• Clean governance: Knowing which Features are active, where they originated, and whether they’re valid helps you reduce upgrade and compliance headaches.

• Risk reduction: Orphaned or rogue Features can break site behavior or even block upgrades. Flagging them early helps avoid major disruptions—especially in on-prem farms approaching end-of-life cycles.

• Operational clarity: Instead of running custom PowerShell scripts or hunting through Central Admin, administrators get one place for feature oversight—so you can act fast.

  
  

In short: Features should empower your SharePoint environment, not mystify it. With Commander’s Feature management capabilities, you gain clarity and control—without complicated scripting.