Google launched Android Enterprise Essentials (AEE) as a stripped-down device management service for small businesses that didn't need a full EMM platform. The idea was straightforward: basic security, minimal setup, sold through resellers.
But Google has since discontinued Android Enterprise Essentials, leaving businesses that relied on it looking for alternatives. If you're one of them, or if you're evaluating Android device management options for the first time, here's what you need to know about both programs and what comes next.
What Was Android Enterprise Essentials?
AEE provided a small set of security features out of the box. Once enrolled, devices got automatic protections without requiring IT staff to configure policies manually.
The feature set was intentionally minimal:
- Screen lock and device encryption enforcement
- Google Play Protect malware scanning
- Remote device wipe for lost or stolen hardware
- Basic inventory tracking
That was pretty much it. No app distribution, no Work Profile separation, no kiosk mode, no per-app VPN. AEE targeted businesses with five to fifty devices and limited IT resources. Think a retail chain with a handful of tablets or a logistics company giving drivers shared phones.
Google sold AEE through carrier and reseller partners at a low per-device monthly fee, making it accessible to companies that had never considered formal device management.
What Is Android Enterprise?
Android Enterprise is Google's full device management framework, built into every Android device running version 5.0 or later. Unlike AEE, it isn't a standalone product. It's an API layer that EMM (Enterprise Mobility Management) providers like Appaloosa use to manage devices at scale.
The capabilities go far beyond what AEE offered:
- Work Profile: creates a separate container on the device for corporate apps and data, keeping personal content private. Ideal for BYOD scenarios.
- Fully managed mode: the entire device is under IT control. Used for company-owned hardware where employees don't need personal use.
- App distribution: deploy public and private apps silently, without user intervention. Configure app settings remotely through managed configurations.
- Kiosk mode: lock a device to one app or a small set of apps. Common in retail, warehousing, and field service.
- Zero-touch enrollment: devices configure themselves automatically when turned on for the first time. IT ships hardware directly to employees without touching it.
- Compliance policies: enforce passcodes, encryption, OS version requirements, and block compromised devices from accessing corporate resources.
- Per-app VPN and network configuration: route specific app traffic through a VPN without affecting personal browsing.
Android Enterprise requires an EMM provider to operate. The provider's console is where IT admins create policies, assign apps, and monitor the fleet. Google certifies EMMs through the Android Enterprise Recommended program to ensure compatibility and feature support.
Why Google Discontinued AEE
Google never published a detailed explanation, but the reasoning follows a pattern familiar to anyone who has watched Google's enterprise product strategy. AEE sat in an awkward middle ground: too limited for companies that needed real management, and competing with free or cheap MDM options from providers who offered much more.
The EMM ecosystem matured rapidly. Providers like Appaloosa, Hexnode, and others started offering entry-level plans that included everything AEE did plus app management, kiosk mode, and remote configuration. The value proposition for a separate Google-run service shrank.
For businesses that were using AEE, Google recommended migrating to an Android Enterprise EMM provider. The migration path is relatively smooth because both systems use the same underlying Android Management API.
AEE vs Android Enterprise: Feature Comparison
Here's how the two programs compared when AEE was still active:
| Feature | AEE | Android Enterprise (via EMM) |
|---|---|---|
| Screen lock enforcement | Yes | Yes |
| Device encryption | Yes | Yes |
| Malware protection | Google Play Protect only | Play Protect + custom policies |
| Remote wipe | Yes | Yes (selective or full) |
| Work Profile (BYOD) | No | Yes |
| App distribution | No | Yes (silent install) |
| Managed app configuration | No | Yes |
| Kiosk / single-app mode | No | Yes |
| Zero-touch enrollment | No | Yes |
| Per-app VPN | No | Yes |
| Compliance policies | Basic | Advanced |
| Fleet size | Small (5-50) | Any size |
| Admin console | Google-hosted | EMM provider console |
| Status | Discontinued | Active |
What to Do if You Were Using AEE
If your business relied on Android Enterprise Essentials, the transition to a full EMM is simpler than you might expect. Your devices already support Android Enterprise. The management framework is the same. What changes is the console you use and the depth of control you get.
Start by picking an EMM that matches your scale. You don't need an enterprise-grade platform with 200 policy settings if you're managing 30 devices. Look for a provider that offers:
- Simple onboarding with zero-touch enrollment support
- App distribution (both Play Store and private APKs)
- Work Profile for BYOD devices
- A clean admin console that doesn't require certification to operate
Appaloosa is certified for Android Enterprise and designed for IT teams that want full control without complexity. You can enroll your existing devices, push apps silently, and set up security policies in minutes.
The Bottom Line
Android Enterprise Essentials served its purpose as a gateway to mobile device management. But the market moved past it. Full EMM solutions now offer the same easy setup AEE promised, with the depth of control that growing businesses actually need. If you're choosing between entry-level and full management in 2026, there's really only one option left: Android Enterprise, powered by the EMM that fits your team.