It looks like you don't have any applicable devices can appear when a service, app, or platform cannot detect compatible hardware on your network. This message often blocks setup, updates, or remote management workflows and signals a mismatch between device profiles and policy rules.
Understanding the conditions that trigger this status helps you align your devices, accounts, and permissions so that services recognize eligible hardware quickly. The following sections break down the most common causes and targeted fixes across platforms.
| Trigger | Typical Scenario | Immediate Effect | Verification Step |
|---|---|---|---|
| Platform Policy | OS version below minimum required | Device hidden from deployment or update | Check system version in Settings |
| Architecture Mismatch | Arm vs x64 package selected | Installer fails silently or shows no devices | Confirm processor type on device |
| Account Scope | Device not added to team or org | Admin console lists zero eligible devices | Verify device membership in admin panel |
| Compliance Status | Jailbreak, missing patch, or disk encryption disabled | Device flagged non-compliant and excluded | Review compliance dashboard entry |
| Network Restrictions | Firewall blocks required ports | Service cannot reach device for inventory | Test connectivity on required ports |
Device Compatibility Requirements
Hardware and operating system compatibility are primary factors that determine whether a service recognizes a device as applicable. Each solution enforces minimum CPU, memory, storage, and OS version criteria that must be met.
Check official documentation for architecture support, Secure Boot requirements, and driver recommendations. Misaligned specs explain why it looks like you don't have any applicable devices even when inventory reports healthy hardware.
Account and Permission Configuration
Access control settings define which devices fall within your management or subscription scope. If a device resides outside your team, group, or organizational boundary, it will not appear in applicable inventories.
Review group memberships, automatic enrollment rules, and administrative roles. Adjust filters or reassign devices to the correct group to resolve visibility gaps tied to identity and permission models.
Policy and Compliance Filters
Platform policies can automatically exclude devices based on security posture, patch level, or encryption state. A single non-compliant setting can hide hardware from updates, installs, or remote sessions.
Use the compliance dashboard to identify failing endpoints, apply required configurations, and remediate eligibility blockers without physically touching each device.
Network and Connectivity Checks
Reachability issues between the management service and endpoints often mimic permission or compatibility problems. Firewalls, proxy configurations, and port restrictions can prevent device registration and status reporting.
Validate that required hostnames and IP ranges are allowed, test connectivity with built-in tools, and confirm that time synchronization and TLS certificates are valid across the environment.
Action Plan for Reliable Device Visibility
- Confirm OS version, architecture, and storage capacity against documented requirements
- Validate account group membership and administrative role scope
- Audit compliance status and apply missing patches or configuration changes
- Test network reachability on required ports and protocols
- Align agent and service versions to avoid compatibility gaps
FAQ
Reader questions
Why does my management console show zero devices after updating the agent?
The agent update may have changed compatibility reporting. Verify that the new agent version aligns with your platform's minimum OS and architecture requirements, and confirm device membership in the correct account or group.
My hardware passes inventory but still appears as not applicable, what could be wrong?
Compliance policies might be blocking the device due to missing patches, disabled disk encryption, or jailbreak status. Review the compliance score and remediate any failing checks to restore eligibility.
Devices on my network are not showing up in deployment plans, why?
Network-level restrictions or service account permissions can prevent discovery. Check firewall rules, required ports, proxy settings, and the service account used by the deployment tool for adequate scope and credentials.
How do I include older devices that keep being marked as non applicable?
Either retire them if they no longer meet security standards, or adjust policy thresholds to extend support while ensuring compensating controls are applied and monitored rigorously.