Some links on this page are affiliate links: if you buy through them we may earn a commission, at no extra cost to you.
Yes—an Android Virtual Device (AVD) can serve as a useful, low-cost Microsoft Intune lab. It is well suited to testing Android Enterprise work-profile enrollment, configuration and compliance policies, Managed Google Play applications, app configuration, reporting, and many user-facing workflows. It is not a complete substitute for a physical Android device: hardware identifiers, OEM behavior, cellular features, biometrics, provisioning, and production hardware acceptance still require real hardware.
This guide uses current Android Studio and Intune terminology. Older walkthroughs may refer to Android Studio Giraffe, Android for Work, Android 14/API 34, or Company Portal as the only enrollment path; those details should not be treated as current requirements.
What an AVD is—and what it is not
The terms are related but different:
- Android Emulator: the program that runs a simulated Android device.
- Android Virtual Device: the definition of that simulated device, including its hardware profile, Android version, system image, storage, and settings.
- Android Studio: Google’s development environment, which includes the Emulator and Device Manager.
Each AVD has its own virtual storage, installed applications, settings, and user data. You can create disposable test devices, wipe them between enrollment modes, and reproduce a test using a named image and API level. Google documents AVD management at Managing AVDs.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →For Intune, think of the AVD as a way to exercise the software control plane: enrollment screens, policy delivery, application assignment, work-profile separation, compliance evaluation, and reporting. Do not treat it as proof that every physical Android model will behave identically.
#1 Best Overall
- telephone wire cable testing FSK/DTMF dual system Caller ID.
- telephone cable tester with On/Off and hangup buttons.FSK/DTMF dual system Caller ID.
- Come with Three type of line plug,easily connect to the phone line.
- Easy for the lineman to check your telephone line fault.
- This set offers Last number redial, On/Off and hangup buttons, so the lineman can check your telephone line fault.
What you can test in an emulator
| Scenario | Suitability | Important qualification |
|---|---|---|
| Android Enterprise work profile | Good | Usually the most straightforward AVD scenario. |
| Company Portal or web-based enrollment | Good | The available path depends on the tenant and enrollment configuration. |
| Configuration profiles | Good for supported settings | Some settings apply only to a particular Android Enterprise mode or device capability. |
| Compliance policies | Useful | Hardware- and OEM-dependent signals may not represent a physical device. |
| Managed Google Play apps | Good with a Google Play image | Google Play services and authentication must work first. |
| App configuration | Useful | Validate the application’s actual support for the configuration keys. |
| Conditional Access | Useful in a controlled tenant | Use a test account and avoid creating a compliance-before-enrollment loop. |
| Corporate-owned or dedicated enrollment | Limited to scenario-specific testing | Provisioning behavior must be verified on representative physical hardware. |
A successful AVD test demonstrates that a particular Intune assignment and Android software workflow worked in that environment. It does not prove that all Intune policies work on all Android devices.
What you need before creating the AVD
Intune and Android Enterprise preparation
Before troubleshooting Android Studio, prepare the tenant:
- Confirm that Microsoft Intune is the mobile device management authority.
- Connect Intune to Managed Google Play. Microsoft requires this connection for Android Enterprise management options. Start with Microsoft’s Android enrollment deployment guide.
- Create a dedicated test user with an Intune license and the necessary Microsoft Entra permissions.
- Create a small test group and assign only the policies and applications needed for the experiment.
- Confirm that enrollment restrictions allow the intended Android platform and ownership type.
- Review Conditional Access. Initially exclude the test account from policies that could require a compliant device before enrollment is complete, or maintain a recovery path.
- Decide whether you are testing a personally owned work profile, corporate-owned work profile, fully managed device, or dedicated device. These are different Android Enterprise modes.
Keep a record of the AVD name, Android image, API level, enrollment mode, test user, policy assignments, and expected result. That makes a later failure much easier to reproduce.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallOutdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchHost requirements
Google’s current Android Emulator requirements recommend a 64-bit operating system, at least 16 GB of RAM, and at least 16 GB of available disk space for a good experience. The SDK, system images, snapshots, and AVD data require additional space, so treat 16 GB as a baseline rather than a comfortable allocation.
Hardware virtualization is important. On Windows, prefer Windows Hypervisor Platform (WHPX). CPU virtualization must be enabled in BIOS/UEFI, using the appropriate Intel or AMD setting. Apple silicon hosts use Apple’s virtualization support. Android documents the relevant options in Emulator acceleration.
Android’s documentation says the Android Emulator Hypervisor Driver is scheduled to be sunset on December 31, 2026. For a new Windows lab, do not build the design around the older AEHD path when WHPX is available.
Install Android Studio
- Download the current stable release from Google’s official Android Studio page.
- Install Android Studio and the Android SDK components offered by the setup wizard.
- Allow the initial SDK setup to finish.
- From the Welcome screen, open More Actions > Virtual Device Manager. After opening a project, use View > Tool Windows > Device Manager.
Do not hard-code an old Android Studio release in your lab documentation. The Device Manager labels and available images change over time, so record the release and image that you actually used.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Rank #2
- 12V internal battery
Create a Google Play-enabled AVD
- In Device Manager, select Create Device.
- Choose Phone, then select a Pixel or comparable phone hardware profile.
- Choose a recent Android system image that matches your test requirement.
- Select an image marked Google Play when the test needs Google Play Store, Google Play services, Google authentication, Company Portal, or Managed Google Play applications.
- Download the image if necessary.
- Use an architecture compatible with the host. An x86_64 image is generally a practical choice on an x86_64 Windows or Linux host where available.
- Name the device clearly, such as
Intune-Android-WorkProfile-PolicyLaborIntune-Android-API36-Test. Do not describe an API level as “latest” unless you have verified it at publication time. - Open the advanced settings. Start with automatic or hardware graphics acceleration and sensible RAM and storage values. Avoid allocating nearly all host memory to the emulator.
- Finish the wizard and start the AVD.
Google Play images include the Play Store and Google Play services and are release-key signed, so they do not provide root access. AOSP images can be useful for development-specific troubleshooting but do not represent an ordinary Google Play Android device and are usually the wrong choice for Intune enrollment testing.
Validate Google services before enrolling
Do not begin with Intune if the underlying Android image is unhealthy. Confirm all of the following:
- The emulator boots consistently to the Android home screen.
- The Play Store opens.
- Network access works.
- Google Play services are running and can update.
- A Google account can sign in if your test requires one.
- Date, time, and time zone are correct.
- The Android version meets the requirements of the enrollment application and your test.
- The emulator has sufficient free storage.
- There is no unresolved Play Protect or Google authentication error.
A Google Play-enabled AVD is preferable, but it should not automatically be assumed to behave exactly like a Google-certified physical device. Android’s emulator troubleshooting guidance specifically warns of Google-account, first-party-app, and GMSCore problems on unpatched API 37 images. If you use API 37 and encounter those symptoms, update to revision 5 or later or use a newer available system image.
Update the image and Google Play services before concluding that an Intune enrollment problem exists. If authentication remains broken, wipe the AVD or create a fresh device rather than carrying a corrupted state into the enrollment test.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Enroll the AVD in Intune
Personally owned work profile
This is generally the best first scenario for an emulator. Microsoft’s current documentation describes both Company Portal and web-based enrollment for personally owned Android Enterprise work profiles. Web-based enrollment is the default for some new tenants or tenants that have migrated to it; the exact route depends on your organization’s configuration. See Microsoft’s personal work-profile enrollment guide.
- Use the organization’s current enrollment URL if web-based enrollment is enabled, or install/open the current Company Portal app if that is the tenant’s configured route.
- Sign in with the dedicated test account.
- Read and accept the organization’s management disclosures and terms.
- Follow the prompts to create the work profile.
- Confirm that work and personal applications are visibly separated.
- Wait for the device to appear in Intune.
- Trigger a sync from the relevant enrollment application or Android settings.
- Check policy, compliance, and application status in Intune.
Microsoft’s Company Portal documentation lists Android 8.0 and later for the documented Company Portal enrollment experience and states that support for Company Portal versions earlier than 5.0.5421.0 ended on October 1, 2025. Use the current application rather than copying an old APK into the emulator.
Corporate-owned, fully managed, and dedicated devices
Do not assume that a normal AVD boot reproduces every corporate-owned flow. Corporate-owned enrollment can involve QR code, token, NFC, or zero-touch provisioning and commonly assumes a new or factory-reset device. Microsoft documents these methods separately in its corporate-owned Android enrollment guidance.
Rank #3
- FOR for RAPID FAULT TRACKING: Quickly identify module errors during for mobile phone repair to minimize downtime and boost technician efficiency
- PORTABLE DESIGN: Compact 12.5g SIM tester fits easily in pockets for on-the-go signal detection and convenient field use
- EFFICIENT SIGNAL CHECK: Detects connectivity issues fast to optimize equipment repair time without needing complex customization
- ESSENTIAL REPAIR TOOL: Reliable addition to any electrical DIY kit for professionals needing accurate mobile diagnostics
- DIRECT OPERATION: Standard ABS device works immediately out of the box for seamless integration into your daily workflow
Dedicated-device testing also has separate requirements, including Android Enterprise support, Google Mobile Services connectivity, Android 8.0 or later, and a Managed Google Play connection. See Microsoft’s dedicated-device documentation.
Recommended Free Tools
An emulator may help you test the policy and application behavior after provisioning, but the exact provisioning path must be tested on a physical device before production use.
Validate the Intune deployment
Test one policy or application assignment at a time. A useful matrix looks like this:
| Area | Expected result | Record |
|---|---|---|
| Enrollment | Work profile is created and the device appears in Intune. | Enrollment mode, user, timestamp, errors. |
| Inventory | Model, Android version, ownership, management type, and last check-in populate. | Reported values and unavailable fields. |
| Configuration | Assigned supported settings appear on the intended side of the device. | Assignment, filter, sync time, result. |
| Compliance | The device evaluates against the selected requirements. | State, grace period, and signal limitations. |
| Application | A required or available Managed Google Play app installs and launches. | Assignment type, install state, version, errors. |
| App configuration | The application receives and uses the assigned configuration. | Configuration keys and application behavior. |
| Removal | Unassignment removes or makes the application unavailable as expected. | Expected timing and final state. |
| Reporting | Portal status and device-side behavior eventually agree. | Last check-in and reporting delay. |
Device inventory limitations
An emulator may report a model resembling sdk_gphone64_x86_64 rather than a commercial handset. IMEI and serial-number fields may be blank or unavailable. This was also observed in the original HTMD AVD walkthrough at HTMD. Treat those values as an emulator limitation, not automatically as an Intune defect.
For configuration policies, specifically check whether the setting targets the work profile, the personal profile, or both. A policy can report successfully while a setting is inapplicable to the emulator or to the selected Android Enterprise mode.
Optional diagnostic commands
Android Debug Bridge (ADB) is useful for confirming the emulator’s state, but it is not required for ordinary Intune enrollment.
adb devices
adb shell getprop ro.build.version.release
adb shell getprop ro.build.version.sdk
adb shell getprop ro.product.model
adb shell getprop ro.product.cpu.abilistIf ADB does not show the emulator:
adb kill-server
adb start-server
adb devicesTo list and launch AVDs from a terminal:
emulator -list-avds
emulator -avd <AVD_NAME>On Windows, the following checks the older AEHD service when it is installed:
Rank #4
- 5x2cm Compact Silent Operation: Advanced capacitive mapping technology ensures zero noise and no screen damage providing smooth clicking without the clicking sounds of traditional mechanical devices
- Adjustable High Frequency Clicking: Integrated digital display allows real time frequency monitoring for high speed gaming or likes during live streaming to meet different task requirements
- Plug and Play USB Interface: Universal compatibility with various smartphones and tablets requiring no app installation or complicated setup for immediate automatic screen tapping
- Anti Slip Stable Design: Crafted with non slip materials to ensure the stays firmly in place even during intense high frequency sessions while remaining lightweight for portable use
- Wide Application for Gaming and Apps: Perfect for idle games live stream liking and repetitive app testing tasks with professional support to ensure optimal device response and performance
sc query aehdA new Windows setup should generally favor WHPX. Android documents the virtualization choices and their limitations in its acceleration guide.
Troubleshooting guide
The emulator is extremely slow
- Confirm CPU virtualization is enabled in BIOS/UEFI.
- Enable Windows Hypervisor Platform on Windows and reboot.
- Check Android Studio’s acceleration status.
- Reduce AVD memory, resolution, or background workload if the host is constrained.
- Try automatic graphics mode, then software graphics if the GPU driver is problematic.
- Check for conflicting virtualization software.
- Avoid running a VM-accelerated emulator inside another virtual machine; nested virtualization can prevent acceleration or create unstable performance.
The AVD will not boot
Try a cold boot or launch without a snapshot:
emulator -avd <AVD_NAME> -no-snapshotIf that fails, wipe the AVD data from Device Manager, update the Emulator and system image, check free disk space, reduce graphics acceleration, or create a new AVD. Wiping data removes the existing work profile and installed applications.
Play Store or Google sign-in fails
- Confirm the system image is marked Google Play.
- Update the system image and Google Play services.
- Check date, time, time zone, and network access.
- For API 37, verify that the image is revision 5 or later if Google services are failing.
- Check whether tenant Conditional Access is blocking the Google or Microsoft sign-in flow.
- Wipe or recreate the AVD if it remains stuck in a broken authentication state.
Company Portal cannot enroll
- Confirm which enrollment method the tenant expects: web-based enrollment or Company Portal.
- Verify the Android Enterprise and Managed Google Play connection.
- Check the user’s Intune license and group assignments.
- Review enrollment restrictions and ownership settings.
- Update or reinstall the current enrollment application.
- Remove the old work profile, wipe the AVD, and retry with the dedicated test account.
- Temporarily exclude the test account from Conditional Access rules that create a circular dependency.
- Review Intune enrollment failures, device-management logs, and the device’s last check-in.
If the same test succeeds on a physical device but not on the AVD, compare the image’s Google services, Android version, reported identifiers, and supported enrollment mode before changing tenant policy.
A policy does not apply
Check in this order:
- Is the device enrolled and checking in recently?
- Is the user or device in the intended assignment group?
- Is an exclusion group taking precedence?
- Is an assignment filter excluding the emulator?
- Does the policy target the correct Android Enterprise management mode?
- Is the setting intended for the work profile rather than the personal profile?
- Has the device synced since the assignment was made?
- Is another policy creating a conflict?
- Is the setting unsupported by the emulator?
Start with one test group and one small policy. Expanding a full production policy set before proving the basic assignment makes failures difficult to isolate.
What an AVD cannot prove
Use a physical Android device for testing involving:
- IMEI, serial-number behavior, SIM, eSIM, cellular radio, phone calls, or carrier services.
- Samsung Knox, Zebra controls, rugged-device features, OEM update behavior, or other manufacturer-specific functionality.
- Fingerprint, face unlock, hardware-backed biometrics, NFC, barcode scanners, specialized peripherals, or hardware-backed security behavior.
- Battery life, thermal behavior, camera, GPS, Bluetooth, real-world networking, or sensor behavior.
- Zero-touch enrollment and manufacturer-specific provisioning.
- Representative Play Protect certification and Google Mobile Services behavior.
- Final kiosk or dedicated-device acceptance on production hardware.
The practical boundary is simple: an AVD is excellent for rapid policy iteration and disposable software workflows; it is not a physical-device certification test.
The most defensible lab setup
For most administrators and learners, use a three-stage model:
- AVD: rapidly test work-profile enrollment, policy assignments, app deployment, app configuration, and reporting.
- Google-certified physical Android device: verify baseline enrollment, compliance, identifiers, Google services, and user experience.
- Representative production device: complete acceptance testing if the organization uses Samsung, Zebra, Lenovo, rugged hardware, or another specific OEM.
Start with free Android Studio and a Google Play-enabled AVD. Add a properly licensed Intune test user and a small test tenant or test group. Buy or borrow one physical Android device before making a production rollout decision. Hosted services such as BrowserStack App Live, AWS Device Farm, or Firebase Test Lab may help with application testing, but they do not automatically reproduce your Intune tenant, Managed Google Play provisioning, or Conditional Access environment.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
