Use custom settings for Android devices in Microsoft Intune
Using Microsoft Intune, you can add or create custom settings for your Android devices using a custom profile. Custom profiles are a feature in Intune. They're designed to add device settings and features that aren't built in to Intune.
This feature applies to:
- Android device administrator
Important
Microsoft Intune is ending support for Android device administrator management on devices with access to Google Mobile Services (GMS) on December 31, 2024. After that date, device enrollment, technical support, bug fixes, and security fixes will be unavailable. If you currently use device administrator management, we recommend switching to another Android management option in Intune before support ends. For more information, see Ending support for Android device administrator on GMS devices.
Android custom profiles use Open Mobile Alliance Uniform Resource Identifier (OMA-URI) settings to configure different features on Android devices. These settings are typically used by mobile device manufacturers to control these features.
Using a custom profile, you can configure and assign the following Android settings. The following settings aren't built in to Intune:
- Create a Wi-Fi profile with a pre-shared key
- Create a per-app VPN profile
- Allow and block apps for Samsung Knox Standard devices
- Configure web protection in Microsoft Defender for Endpoint for Android
Important
Only the settings listed can be configured by in a custom profile. Android devices don't expose a complete list of OMA-URI settings you can configure.
This article shows you how to create a custom profile for Android devices.
Create the profile
Sign in to the Microsoft Intune admin center.
Select Devices > Manage devices > Configuration > Create > New policy.
Enter the following settings:
- Platform: Select Android device administrator.
- Profile type: Select Custom.
Select Create.
In Basics, enter the following properties:
- Name: Enter a descriptive name for the profile. Name your profiles so you can easily identify them later. For example, a good profile name is Android DA custom profile.
- Description: Enter a description for the profile. This setting is optional, but recommended.
Select Next.
In Configuration settings > OMA-URI Settings, select Add. Enter the following settings:
Name: Enter a unique name for the OMA-URI setting so you can easily find it.
Description: Enter a description that gives an overview of the setting, and any other important details.
OMA-URI: Enter the OMA-URI you want to use as a setting.
Data type: Select the data type for this OMA-URI setting. Your options:
- String
- String (XML file)
- Date and time
- Integer
- Floating point
- Boolean
- Base64 (file)
Value: Enter the data value you want to associate with the OMA-URI you entered. The value depends on the data type you selected. For example, if you select Date and time, select the value from a date picker.
Select Save to save your changes. Continue to add more settings as needed. After you add some settings, you can select Export. Export creates a list of all the values you added in a comma-separated values (.csv) file.
Select Next.
In Scope tags (optional) > Select scope tags, choose your scope tags to assign to the profile. For more information, see Use RBAC and scope tags for distributed IT.
Select Next.
In Assignments, select the groups that will receive this profile. For more information on assigning profiles, see Assign user and device profiles.
Select Next.
In Review + create, when you're done, choose Create. The profile is created, and shown in the list.
You can also monitor its status.