Hello everyone,

As we move into the second half of 2026, we wanted to share a summary of the latest Android Management API features released over the first half of the year. These updates are designed to provide IT admins with more granular control, enhanced security, and support for emerging device types.

Feature 1: Android XR Support

We are excited to announce official support for managing Android XR devices via AMAPI. As mentioned in our recent announcement, ‘Android Enterprise management arrives for Android XR,’ this allows organizations to secure, manage, and deploy XR headsets and AI glasses with the same robust Android Enterprise controls you rely on for mobile devices.

Why is this useful?

With official XR support, you can confidently integrate immersive technology into your enterprise workflows while maintaining the same security and management standards as your mobile fleet.

How can it be applied?

This applies to company-owned XR devices. For deeper insight our Help Centre article. 

Feature 2: Autofill Service Control

A new AutofillPolicy allows IT admins to completely disable the autofill service on managed devices.

Why is this useful?

Unwanted autofill prompts have been a recurring pain point for fleet management, particularly on dedicated devices. This policy provides the granular control needed to disable the service, ensuring a consistent and secure user experience. 

We’ve been following the ongoing discussion in the community regarding this, and we’re pleased to provide this control to assist with those use cases.

How can it be applied?

This policy can be configured via the AMAPI autofillPolicy field. See the Android Management API Documentation for details.

Feature 3: Application Roles

We have transitioned to application roles, which replaces the extensionConfig field in ApplicationPolicy.

Why is this useful?

This update simplifies app management and configuration, making it easier for IT admins to define and manage app-specific permissions and behaviors.

How can it be applied?

Update your existing ApplicationPolicy configurations to use the new roles field.

Feature 4: Private DNS Management

IT admins can now manage privateDnsSettings on company-owned devices.

Why is this useful?

This allows organizations to enforce specific DNS configurations, supporting modes such as user choice and automatic (on both fully managed and company-owned work profile devices), or a specified host (supported on fully managed devices only), which is critical for network security and compliance.

How can it be applied?

Configure the privateDnsSettings field under deviceConnectivityManagement in your device policies. See the Android Management API Documentation.

Feature 5: User-Initiated eSIM Control

A new userInitiatedAddEsimSettings policy allows admins to restrict users from adding eSIM profiles on Android 15+ devices.

Why is this useful?

This gives IT admins greater control over device connectivity and prevents unauthorized changes to cellular configurations.

How can it be applied?

This policy applies to Android 15+ devices. Configure the userInitiatedAddEsimSettings field in your device policies. See the Android Management API Documentation.

Feature 6: ProvisioningInfo Clarification

We have clarified that the provisioningInfo object is available for up to 24 hours after device provisioning.

Why is this useful?

This helps EMMs better manage the enrollment lifecycle by providing a clear window for accessing necessary provisioning data.

How can it be applied?

EMMs should ensure their systems are designed to retrieve provisioningInfo within the 24-hour window post-enrollment.

Stay updated

For those catching up, you can view our previous Android Management API update article. We will be sharing these quarterly, but for the latest technical specs we recommend bookmarking our Android management API Documentation. 

In the meantime, share your thoughts in the comments below. Do any of these new features solve existing pain points for your fleet management?

Thanks,

The Android Enterprise Team