Supervised restrictions, UAE

You cannot turn off Apple Intelligence writing tools on an unsupervised iPhone.

Supervision denotes that the device is owned by the organisation, and it unlocks a set of restrictions that unsupervised management simply does not have. The Apple Intelligence controls are the newest and most consequential example.

Supervised Apple device restrictions for UAE organisations
  • Supervised onlyWhere the strongest restrictions live
  • iOS 18Where the Apple Intelligence controls start
  • AutomaticDevices enrolled through ADE are supervised
  • DisclosedThe user is told the device is supervised
The failure mode

A restriction policy that looks configured and enforces nothing.

This is an unusual kind of problem because everything appears correct from the management console. The only way to find it is to look at a device.

  • Somebody writes the policy, the management platform accepts it without complaint, and the console reports it as assigned. Every signal available from the administrative side says the control is in place, and none of those signals are checking the device.
  • On the device, nothing changes. The restriction is supervised only, the device is not supervised, and the setting is simply ignored. There is no error, no warning and no indication that a control the organisation believes it has does not exist.
  • The gap can persist for a long time, because nobody tests a restriction that was never expected to fail. It usually surfaces during an incident or an audit, which are the two worst moments to discover that a control was decorative.
  • The test takes five minutes. Pick one restriction you believe is applied, and check it on an actual device. If it is not enforced, supervision is almost always the reason, and the fix is an enrolment question rather than a policy one.
What supervision means

Eight things that decide whether your restrictions actually apply.

Organisations regularly configure a restriction, see no effect, and conclude the management platform is broken. The usual explanation is that the restriction is supervised only and the devices are not supervised.

Supervision means the organisation owns it

Apple states that supervision generally denotes that the device is owned by the organisation, which provides additional control over its configuration and restrictions. It is a statement about ownership first and a technical mode second.

Some restrictions exist only under supervision

Apple is explicit that certain restrictions are available only for Apple devices that enrol in a device management service and are supervised. A policy that assumes those settings will apply to an unsupervised device will silently fail to do anything.

The Apple Intelligence controls are supervised only

Allow writing tools and Allow Image Playground from iOS 18, and Allow Safari summary, Allow Mail smart replies and Allow Apple Intelligence reports from iOS 18.4. On macOS 15.2 there is also Allow external intelligence integrations, which prevents cloud based intelligence services with Siri.

Automated Device Enrolment supervises automatically

Devices enrolled that way become supervised without any additional step, from iOS 13, iPadOS 13.1, macOS 10.14.4, tvOS 13, visionOS 3 and watchOS 10. That is the cleanest route and the reason registration at procurement matters so much.

Apple Configurator supervises, but erases

You can also supervise iPhone, iPad and Apple TV manually using Apple Configurator for Mac. The device has to be physically connected and it is erased during the process, so retrofitting supervision onto devices already in use is disruptive rather than transparent.

The user is told, in plain language

Device settings show wording of the form: this device is supervised, and the named organisation can monitor your internet traffic and locate this device. Supervision is disclosed by design, which is worth knowing before it appears on somebody screen unannounced.

App usage can be restricted to a list

Restrict app usage, available from iOS 9.3, places any apps other than Settings or Phone on an approved list or a disapproved one. For single purpose and frontline devices that is the control that actually determines what the device is for.

Availability varies by management platform

Apple notes that not all restrictions are available in all device management services, and that services can change the default state for any restriction. What your platform exposes is therefore a question to answer against your platform, not against the Apple list.

The current question

Most UAE organisations asking about supervision this year are asking about Apple Intelligence.

The generative features on Apple devices raised a governance question, and the answer sits behind supervision.

  • Allow writing tools prevents Apple Intelligence writing tools, and Allow Image Playground prevents users from using Image Playground. Both are available from iOS 18 and both are supervised only, so an unsupervised estate has no way to apply them.
  • From iOS 18.4 there are three more: Allow Safari summary prevents the ability to summarise content in Safari, Allow Mail smart replies prevents smart replies in Mail, and Allow Apple Intelligence reports prevents Apple Intelligence reports.
  • On the Mac side, Allow external intelligence integrations from macOS 15.2 prevents the use of external, cloud based intelligence services with Siri. For organisations whose concern is corporate content reaching a third party model, that is the specific control.
  • None of this is a judgement about whether these features should be off. It is that the decision should be yours to make, and without supervision it is not a decision you are able to implement at all.
Ask us about the AI feature controls
How we approach it

Four things that stop a restriction policy being decorative.

The failure mode here is unusual: everything looks configured and nothing is enforced. Verification on a real device is the only thing that catches it.

We confirm supervision before writing policy

Certain restrictions are available only for devices that enrol in a device management service and are supervised. Establishing which devices are actually supervised, and how, is the first step, because it determines what the policy is even able to say.

We treat the Apple Intelligence decision as a governance one

Writing tools, Image Playground, Safari summaries, Mail smart replies, Apple Intelligence reports and external intelligence integrations with Siri are all controllable and all supervised only. The organisation should decide, deliberately, rather than inherit a default.

We verify on device, never in the console

Apple notes that not all restrictions are available in all device management services. A setting your platform does not expose, or a device version does not support, produces a policy that reads correctly and enforces nothing.

We are honest about the retrofit cost

Supervising an existing device through Apple Configurator requires a physical connection and erases it. Where a population is unsupervised and in daily use, the realistic plan is usually to supervise at the next refresh rather than to wipe working devices.

How an engagement runs

Three phases across roughly three to five weeks.

The length depends almost entirely on how many devices are currently unsupervised and in daily use, since supervising those through Apple Configurator erases them.
  1. 01
    Week 1

    Establish supervision state

    Which devices are supervised and which are not, and how each became so. Devices enrolled through Automated Device Enrolment are supervised automatically, and anything else needs either a re-enrolment or an erase through Apple Configurator.

    • Supervised and unsupervised populations identified
    • Enrolment route documented per population
    • Devices requiring erase to supervise listed
    • OS version distribution recorded against restriction floors
  2. 02
    Week 2

    Decide the restriction policy

    Which supervised only restrictions the organisation actually wants, with a reason recorded for each. The Apple Intelligence controls usually dominate this conversation, and they deserve a deliberate decision rather than a default.

    • Restriction policy drafted with rationale per setting
    • Apple Intelligence position decided explicitly
    • App usage approach agreed for frontline devices
    • Availability confirmed against your management platform
  3. 03
    Weeks 3 to 5

    Apply, verify and communicate

    Restrictions applied and then verified on a real device rather than in the console, because a setting that a platform does not expose or a device version does not support fails quietly. Users informed, since supervision is disclosed in device settings anyway.

    • Restrictions applied and verified on device
    • Version floor exceptions documented
    • User communication issued about supervision
    • Review cadence agreed as Apple adds restrictions
Where this matters

Six situations where supervision is the deciding factor.

Each of these is an organisation that wanted a specific control and found that the control existed but their devices could not receive it.

A regulated firm restricting generative features

Where policy or regulation requires control over what content reaches an AI feature, the relevant restrictions all sit behind supervision. Allow external intelligence integrations on macOS 15.2 specifically prevents cloud based intelligence services with Siri.

A retail estate locking devices to a task

Restrict app usage places any apps other than Settings or Phone on an approved or disapproved list. For a device that exists to run one or two applications, that restriction is the difference between a work tool and a general purpose device.

A school controlling what students can reach

Supervision is the norm in education for exactly this reason, and the supervised only list is where the meaningful controls live. Devices enrolled through Automated Device Enrolment arrive supervised, which is why registration at purchase matters.

An organisation that cannot prevent hidden apps

Allow apps to be hidden, from iOS 18, prevents users from hiding apps. Where support or compliance depends on being able to see what is installed and visible on a device, that restriction is only available under supervision.

A business wanting to prevent iCloud Private Relay

From iOS 15, the restriction prevents the user from turning on iCloud Private Relay. For organisations whose network controls depend on seeing and filtering traffic, this is a common requirement and a supervised only one.

A team whose restrictions appear to do nothing

The most common support case in this area. The configuration is right, the platform accepted it, and the device ignores it, because the setting is supervised only and the device is not supervised. Diagnosing that takes minutes once you know to look.

Three positions

What you can actually control, by device posture.

The middle column is the uncomfortable one, because it looks managed in the console while the strongest settings quietly do nothing.
Supervised only restrictions apply
Supervised, corporate ownedYes
Enrolled but not supervisedNo
UnmanagedNo
Apple Intelligence features controllable
Supervised, corporate ownedYes
Enrolled but not supervisedNo
UnmanagedNo
App usage restricted to a list
Supervised, corporate ownedYes
Enrolled but not supervisedNo
UnmanagedNo
iCloud Private Relay preventable
Supervised, corporate ownedYes
Enrolled but not supervisedNo
UnmanagedNo
Apps can be prevented from being hidden
Supervised, corporate ownedYes
Enrolled but not supervisedNo
UnmanagedNo
Configuration and app deployment
Supervised, corporate ownedYes
Enrolled but not supervisedYes
UnmanagedNo
Supervision disclosed to the user
Supervised, corporate ownedYes
Enrolled but not supervisedNot applicable
UnmanagedNot applicable
Appropriate for personally owned devices
Supervised, corporate ownedNo
Enrolled but not supervisedYes
UnmanagedYes
How it is achieved
Supervised, corporate ownedADE, or Configurator with an erase
Enrolled but not supervisedProfile or account enrolment
UnmanagedNothing
Suitable for frontline and shared devices
Supervised, corporate ownedYes
Enrolled but not supervisedPartially
UnmanagedNo
A representative selection

Supervised only restrictions and where they start.

Taken from the published supervised restrictions documentation. This is a selection rather than the full list, and availability varies by management platform.
RestrictionFromWhat it does
Allow writing toolsiOS 18Prevents Apple Intelligence writing tools
Allow Image PlaygroundiOS 18Prevents users from using Image Playground
Allow Safari summaryiOS 18.4Prevents summarising content in Safari
Allow Mail smart repliesiOS 18.4Prevents smart replies in Mail
Allow Apple Intelligence reportsiOS 18.4Prevents Apple Intelligence reports
Allow external intelligence integrationsmacOS 15.2Prevents cloud based intelligence services with Siri
Allow apps to be hiddeniOS 18Prevents users from hiding apps
iCloud Private RelayiOS 15Prevents the user turning on iCloud Private Relay
Allow App ClipsiOS 14Users cannot add App Clips, existing ones are removed
Restrict app usageiOS 9.3Approved or disapproved list beyond Settings and Phone
How an engagement runs

Five steps, and the first one usually explains the problem.

Where somebody arrives saying restrictions are not applying, the supervision audit answers it in the first hour, before any policy work begins.
  1. 1

    Audit supervision across the estate

    Which devices are supervised and by which route. Automated Device Enrolment supervises automatically from iOS 13, iPadOS 13.1, macOS 10.14.4, tvOS 13, visionOS 3 and watchOS 10, and Macs on macOS 11 or later also supervise through account-driven or profile-based enrolment.

  2. 2

    Map required controls against the supervised list

    Every control the organisation wants, checked against whether it is supervised only, which OS version it starts at, and whether your management platform exposes it. Apple is explicit that availability varies between services.

  3. 3

    Take the Apple Intelligence decision deliberately

    Writing tools and Image Playground from iOS 18, Safari summary, Mail smart replies and Apple Intelligence reports from iOS 18.4, and external intelligence integrations from macOS 15.2. A recorded reason for each position is what makes this defensible later.

  4. 4

    Apply and verify on real devices

    Each restriction confirmed as actually enforced on a device of each platform and version in scope. This step is not optional, because the failure mode is silent and looks identical to success from the management console.

  5. 5

    Communicate and set a review cadence

    Users are told about supervision, which device settings disclose anyway. And a review each major release, since Apple adds supervised restrictions regularly and the useful ones tend to be the newest ones.

Straight answers

What organisations ask about supervised restrictions.

Policy checklist

Twelve questions to answer before you write the restriction policy.

The first group is the one that determines whether any of the rest is achievable at all.

Supervision

  • Are corporate devices supervised?
    Otherwise the list does not apply.
  • Were they enrolled through ADE?
    That supervises automatically.
  • Would supervising require an erase?
    Configurator erases the device.
  • Are new devices registered at purchase?
    The clean route.

Apple Intelligence

  • Do we have a position on writing tools?
    iOS 18 and supervised only.
  • What about Safari summaries and Mail replies?
    iOS 18.4.
  • Do we want external Siri integrations off?
    macOS 15.2.
  • Is the estate on iOS 18 or later?
    The floor for these controls.

Operational

  • Does our platform expose these settings?
    Availability varies.
  • Have we verified on a device?
    Not just in the console.
  • Have users been told?
    Supervision is disclosed anyway.
  • Who reviews new restrictions?
    Apple adds them each release.
Next step

Pick one restriction you believe is applied, and check it on an actual device.

Tell us about device models, OS versions, supervision state and the restrictions you need. We will confirm the requirements and proposed scope with you.