Hide Phone App on AirWatch Managed Device (App Profile)

To remove the Phone icon from a Workspace ONE UEM-managed device, first check its operating system, version, and enrollment mode. An app-configuration profile alone does not reliably hide a built-in app. Use a supported supervised-device restriction on Apple devices, or a managed launcher or kiosk policy on Android, then test calling, emergency access, and recovery before wider deployment.

If you are searching for an AirWatch app profile setting, the key distinction is what that profile controls. AirWatch is now called Workspace ONE UEM, and an app-configuration profile usually configures a managed app; it is not a general control for hiding built-in system apps. The right method depends on the device and on whether you need to hide an icon, block the app from opening, or prevent calls.

I approach this as an endpoint-management change, not a cosmetic setting. A hidden icon may leave other routes to calling available. A stronger restriction can affect important functions. Start with the exact outcome, validate the available controls, and test on a small group before deployment.

Planning: Identify OS, Enrollment Mode, and Desired Outcome

Planning means recording the device details and defining what “hide” should mean before changing a profile. Workspace ONE UEM menus and supported controls can vary by console version, operating system, OS version, device model, and enrollment method. These facts determine whether a supported control exists and how to test it.

Define the requested outcome

Write down which of these outcomes is required:

  • Remove the icon: The Phone app no longer appears in the home screen or managed launcher.
  • Block launch: The user cannot open the Phone app through supported routes.
  • Disable calling: Calling services are unavailable or restricted.

These are different controls. A launcher can remove an icon from its display without disabling the Phone app or the device’s calling service. Conversely, a system restriction may have effects beyond icon visibility. Do not treat these outcomes as interchangeable.

Record the device and management details

Before configuring anything, capture:

Detail to recordWhy it matters
OS, version, and device modelAvailable restrictions can vary by platform and OS release.
Enrollment modeApple restrictions may require supervision; Android controls depend on the management mode and launcher.
Workspace ONE UEM console versionMenu names and available settings can vary.
Current launcher or home-screen setupA managed launcher controls its own displayed app list.
Required calling and emergency functionsA restriction must not unintentionally disrupt approved use.

For Apple devices, confirm whether the iPhone or iPad is supervised. Supervision is an enhanced management state that can enable additional device controls; ordinary enrollment does not necessarily provide the same options. Also confirm that the target device actually has a Phone app to hide. iPads do not generally present the same built-in Phone app experience as iPhones.

For Android, identify whether the device is Android Enterprise fully managed, dedicated, or enrolled in another mode. Confirm which launcher is in use and whether it is managed by your organization. Next step: define the outcome and complete this inventory before selecting a payload.

Access and Clearances: Confirm Supported Restrictions and Calling Requirements

A supported control is one that the current platform and enrollment mode expose through Workspace ONE UEM and that the device accepts. An app profile is not a substitute for a device restriction or managed-launcher configuration. Check the options available for your exact setup rather than relying on a setting name found for another version.

Apple: Check supervised-device restrictions

On iOS or iPadOS, an app-configuration profile supplies settings to a managed app. It does not, by itself, hide a built-in system app. To control app visibility, review the supervised-device restriction options available in your UEM console and confirm whether they support the intended app and OS version.

Do not assume every built-in app can be hidden. If the console offers an app restriction or selection control, check that the Phone app is eligible within that supported interface. Do not rely on manually entering a guessed bundle identifier or on an undocumented identifier trick. A control that appears to save in the console may still be rejected, ignored, or behave differently on the device.

Before proceeding, confirm the intended effect in current Workspace ONE UEM and Apple platform documentation for your deployed versions. If the Phone app is not an eligible target, do not force the setting. Ask your UEM administrator or vendor support for a supported option.

Android: Check the managed launcher and kiosk mode

A managed launcher is an organization-controlled home screen that can show a selected set of apps. In Android Enterprise kiosk or dedicated-device setups, the launcher may let an administrator omit Phone from the displayed or allowed app list, if that device mode and launcher support it.

This typically controls access through that launcher. It does not prove that the Phone app or telephony service has been disabled. Users may have other routes to an app, and the behavior can differ by device, OS, and launcher. Test those routes on the actual hardware.

Platform and setupPossible supported approachWhat it does not prove
Supervised iPhone or iPadCheck UEM’s supported supervised-device app restriction controlsThat every system app is eligible, or that the Phone app exists on the device
Android Enterprise with managed launcherOmit Phone from the launcher’s displayed or allowed apps, if supportedThat calling or all other routes to the app are disabled
App-configuration profile aloneConfigure a managed app that supports the profileThat a built-in Phone app is hidden

Next step: confirm the control is supported for the exact enrollment and device, then document what it does and does not restrict.

Execution: Apply a Supervised Restriction or Managed Launcher Policy

Execution means applying the supported control to a limited test group, checking its effect, and preserving a clear recovery path. Do not deploy a guessed payload or broaden the restriction to solve an icon-only request. Keep the configuration focused on the intended outcome and approved device group.

Build a test configuration

  1. Create a narrow pilot group. Include devices that represent each relevant OS version, model, enrollment mode, and launcher configuration. If those factors differ, test each combination rather than assuming one result covers all devices.
  2. Choose the platform-supported control. On Apple, use an eligible supervised-device restriction surfaced by the console. On Android, configure the supported managed launcher or kiosk policy. Do not treat an app-configuration profile as the hiding mechanism.
  3. Check the app selection before assignment. Confirm that the Phone app is an allowed target in the relevant control. If it is absent or rejected, stop and verify support rather than substituting an undocumented value.
  4. Preserve calling requirements. Ask the policy owner whether ordinary calling, emergency calling, or another approved dialer function must remain available. Do not disable telephony unless that is explicitly approved and supported.
  5. Assign only to the pilot. Review the target group and policy before publishing. Use the console’s status reporting to see whether the profile or policy was delivered and applied.

Keep a record of the original configuration, the test group, the change, and the person who approved it. That makes it easier to compare results and reverse the change if the policy causes an unexpected effect.

Illustrative deployment scenarios

These are examples of how to reason about the setup, not reports of specific deployments or guaranteed outcomes.

Scenario: supervised iPhone, icon-only request. An administrator confirms that the current UEM and OS expose a supported restriction for the intended app. They test that control on a representative supervised iPhone, then check both the home screen and app behavior. If the app cannot be selected or the outcome is broader than requested, they do not deploy it as an icon-only fix.

Scenario: Android dedicated device using a managed launcher. A policy owner wants the launcher to show only work-required apps. The administrator checks that the launcher supports an app allowlist, omits Phone in the pilot, and tests whether calling remains possible through other routes. The result is documented as launcher visibility control, not as proof that telephony is disabled.

Next step: assign only after the supported control and its limits are clear to the policy owner.

Verification: Test Visibility, Functionality, and Rollback

Verification is a device-side check, not just a green status in the UEM console. A delivery status indicates that a configuration reached or was processed by a device; it does not, by itself, prove the Phone icon disappeared or that calling behavior matches the policy. Test the exact user experience on each relevant device type.

Use a repeatable test checklist

On each pilot device, record the result for these checks:

  • Policy status: Is the relevant restriction or launcher configuration reported as applied?
  • Visible access: Is Phone absent from the home screen or managed launcher, as intended?
  • Other access routes: Can the app still be reached through search, a shortcut, another launcher screen, or a supported system route?
  • Calling behavior: Do approved calling functions still work? Test emergency-related behavior only under an approved, safe test process; do not place an unnecessary emergency call.
  • Recovery: Can the administrator remove or revise the policy, and does the device return to the expected state?
  • Exceptions: Do any device models or OS versions behave differently?

For each check, mark pass, fail, or not tested, and add the device model, OS version, enrollment mode, and test date. This creates a useful comparison without pretending there is a universal success threshold.

Know when to roll back

Remove or revise the pilot policy if it hides more than intended, disrupts required functions, fails on a supported device, or cannot be recovered as planned. Confirm the device receives the rollback and returns to its prior expected state. If a profile remains pending or reports an error, investigate that status before expanding deployment.

A launcher change should be described accurately: it may hide the Phone entry in that launcher, but it does not necessarily disable the app or calling service. A system restriction may have wider effects. Keep the policy description and user guidance aligned with the behavior you actually verified.

Next step: expand only after the device-side checks pass, the policy owner approves the result, and rollback has been tested.

Conclusion and FAQ

The reliable path is to identify the device and desired outcome, confirm a platform-supported restriction or launcher control, and validate it on representative devices. An app-configuration profile alone is not a dependable way to hide a built-in Phone app. Treat icon visibility, app launch, and calling as separate questions, and preserve approved emergency and recovery functions.

Can an app profile hide the built-in Phone app?

Usually, an app-configuration profile configures a managed app; it is not a general control for hiding built-in system apps. Check the supported restriction or launcher controls for the device’s platform and enrollment mode.

Is AirWatch the same product as Workspace ONE UEM?

AirWatch is the former name associated with Workspace ONE UEM. Confirm the console version and available settings in the environment you manage, since screens and capabilities can vary.

Can I hide Phone on a supervised iPhone?

Possibly, if the current OS and UEM configuration expose a supported supervised-device restriction for that app. Confirm eligibility in the console and test on the target device before deployment.

Does supervision guarantee that Phone can be hidden?

No. Supervision can enable additional management controls, but it does not mean every built-in app is eligible for hiding. Verify the supported control for the OS version and device.

Can a managed Android launcher hide the Phone icon?

A supported managed launcher may omit Phone from its displayed or allowed apps in an appropriate Android Enterprise setup. That does not necessarily remove the app or disable calling.

Does hiding the icon block calls?

Not necessarily. Hiding an icon can remove one access point while leaving other routes or calling functions available. Test actual behavior on the target device.

Should I enter a Phone app bundle identifier manually?

Do not rely on a guessed or undocumented identifier. Use the app selection or restriction controls supported by the console, and confirm the option for your platform and version.

What should I test before wider deployment?

Check policy status, icon visibility, other routes to the app, required calling behavior, and rollback. Repeat tests across the OS versions, models, enrollment modes, and launchers in scope.

What if the restriction is not available in Workspace ONE UEM?

Do not substitute an app profile or unsupported workaround. Verify the feature against current product and platform guidance, then consult your UEM administrator or vendor support about supported options.

Can I disable the Phone service instead of hiding its icon?

That is a different and more significant change. Disable calling only when explicitly approved and supported, after assessing required functions and testing recovery.

(This article was written by one of our staff writers, Samuel Thornton. Visit our Meet the Team page.)

Similar Posts

Leave a Reply

Your email address will not be published. Required fields are marked *