Apple Business migration, UAE

Apple Business Manager is gone, and your account already moved itself.

On 14 April 2026 Apple consolidated Apple Business Manager, Apple Business Essentials and Apple Business Connect into one platform called Apple Business. Existing accounts migrated automatically, so nothing broke and there was no deadline to miss. What did change is your terminology, your runbooks, and what you now get for free.

Apple Business migration and review for UAE organisations
  • 14 April 2026Consolidation date
  • AutomaticExisting accounts migrated
  • 200 plusCountries served, UAE included
  • BlueprintsThe new configuration model
What actually changed

Eight changes, and only three of them need you to do anything.

Most of what you will read about this consolidation overstates the disruption. The account move was automatic and silent. The things that genuinely need attention are the new free capability, the terminology, and the assumptions your existing processes were built on. This page covers what moved, what to verify, and what it means for whatever MDM you already run, which for most organisations turns out to be very little indeed.

Three services became one, automatically

Apple Business Manager, Apple Business Essentials and Apple Business Connect are now a single platform called Apple Business. Apple states it brings all three together, and existing accounts moved without administrator action. If you had an Apple Business Manager account, you have an Apple Business account, with the same devices, the same purchases and the same people. There was no migration project to run and no deadline anybody missed.

Blueprints, the new way configuration is expressed

A Blueprint is a preconfigured bundle of settings and apps that you assign to devices or to a user group. Apple describes the model as configure once, deploy everywhere, and it is what enables zero-touch deployment for employees. Assign a user group to a Blueprint and everyone in it receives the apps and the configuration it contains. This is the single most useful new concept to learn, and it is where most of the practical value sits.

Device management built in by Apple, at no cost

Apple Business now includes a built-in device management service giving access to Configurations and Blueprints. For a small Apple-only organisation with straightforward needs, this genuinely can be enough on its own, which was not true before. It does not make your existing MDM redundant, and Apple has not published a feature comparison between them. We say more about that below rather than inventing a list.

Managed Apple IDs are now Managed Apple Accounts

The name changed and the concept did not. These are still the organisation-owned identities that separate work from a personal Apple Account, and they are still what gives you control over company data on an Apple device. Every internal document, onboarding checklist and support script that says Managed Apple ID is now using a term that no longer appears in Apple documentation, which is a small but real source of confusion for new staff.

Federation with your existing identity provider

Managed Apple Accounts can be provisioned from your existing directory so people sign in with the credentials they already have. Apple names Google Workspace and Microsoft Entra ID explicitly, alongside other identity providers. For UAE organisations running Microsoft 365, which is most of them, this means the Apple identity layer connects to the directory you already operate rather than becoming a second set of accounts to manage.

App and book purchasing, under new names

What administrators knew as Apps and Books now appears as Get Apps and Get Books. The function is unchanged: the organisation buys licences, assigns them to devices or people, and recovers them when somebody leaves. The reason this matters is purely practical. Anyone following a procedure written before April 2026 will be looking for a menu item that is no longer called that, and will conclude something is broken when nothing is.

Available across the UAE, and everywhere you operate

Apple states the platform is available in over 200 countries and regions. For UAE organisations with offices in other GCC states, in India, or in Europe, this matters because the device account layer works consistently across all of them rather than being a per-country arrangement. It is one of the few parts of a multi-country IT estate that genuinely does not need regional variation.

You can still connect the MDM you already use

Apple documentation is explicit that Apple Business allows you to connect more than one device management service and assign devices to different services as needed. So Intune stays connected, Jamf stays connected, and you can run the built-in service alongside them for a subset of devices if that suits you. Nobody has to choose between Apple Business and their existing platform, which is the most common misunderstanding we are correcting at the moment.

The honest version

What we can tell you, and what we will not pretend to know.

There is a lot of confident writing about this change that goes well beyond what Apple has actually published. Here is the line between the two, because knowing which is which is more useful than a longer answer.

  • Verified from Apple: the three services are consolidated, existing accounts migrated automatically, the platform covers over 200 countries and regions, built-in device management provides Configurations and Blueprints, Managed Apple Accounts can federate with Microsoft Entra ID or Google Workspace, and more than one device management service can be connected at once with devices assigned between them.
  • Not published by Apple: a feature-by-feature comparison of the built-in device management service against a full third-party MDM. We are not going to invent that list, and you should be sceptical of anyone who presents one as authoritative. What we can do is compare against capabilities we can verify on the other side, which is what the table below does.
  • What we know from the other direction is concrete and useful. Intune manages Windows devices and connects device compliance to conditional access on your company data. Jamf Pro provides scripting, extension attributes and patch management workflows for macOS. If you need any of those specific things, the built-in service is not the whole answer, because those capabilities belong to those platforms.
  • The practical advice for most UAE organisations is unexciting and correct: verify the account, learn Blueprints, update your documentation for the new terminology, and change nothing else until you have a reason. A consolidation that migrated your account for you is not an occasion to re-platform your device management.
Ask us what applies to your estate
How we handle this

Four reasons to have somebody look at this once.

This is a small piece of work with a disproportionate payoff, mostly because it surfaces things that were already wrong and that the consolidation gave everybody a reason to finally look at.

We verify against Apple documentation, not against commentary

Everything we tell you about this change is traceable to Apple own published guidance, and where Apple has not published something we say so rather than filling the gap with a confident guess. That distinction matters more than usual here, because the volume of secondhand writing about this consolidation is high and a fair amount of it is wrong.

We find the problems that predate the change

Almost every Apple account review we do surfaces the same things: an administrator who left the company, devices in daily use that were never in the account, app licences assigned to former staff, and a reseller relationship nobody has checked in three years. None of these were caused by the consolidation. All of them are worth finding.

We will tell you to change nothing, when that is right

If you run Intune or Jamf and it works, the correct outcome of this review is usually a short list of documentation fixes and one recommendation about Blueprints. We are not going to use a free Apple capability as a reason to propose re-platforming your device management, because for an organisation that already has working management that would be a bad trade.

We support the estate afterwards, not just the review

The review is a couple of hours. What tends to follow is the ordinary work of running an Apple estate properly: enrolment for new devices, leaver processing, licence recovery, keeping the account accurate. We do that as part of a support arrangement, with priority response tiers, P1 within 5 minutes, and a named contact rather than a queue.

Who this affects and how

Six situations, and what the change means for each.

The consolidation lands differently depending on what you were using. These are the six positions we see across UAE clients, roughly in order of how much attention each one needs.

You used Apple Business Manager alongside Intune or Jamf

The most common position and the least affected. Your account migrated, your MDM connection is intact, and the change is essentially terminology plus a new free capability you can ignore or adopt as you choose. The work here is a short verification and a documentation pass, not a project. Do not let anybody sell you a migration you do not need.

You used Apple Business Essentials as your management platform

This is the group that needs to pay attention, because the service you were using no longer exists as a separate product and its function now sits inside Apple Business. Your devices did not stop being managed, but the way you administer them has moved and the concepts changed. This is worth a proper walkthrough rather than working it out from a support article.

You used Apple Business Connect for your brand presence

Apple Business Connect handled how your business appeared to customers in Apple Maps and related surfaces, and it is now part of the same platform. Practically this often means a different team inside your organisation now shares a platform with IT, which is an internal ownership question more than a technical one. Decide who administers what before it becomes an argument.

You are a small Apple-only business with no MDM at all

This is the group that gained the most and mostly does not know it. Device management built in at no additional cost, with Blueprints for zero-touch setup, is a genuine improvement in what a ten person Apple-only firm can do without buying anything. If you have been managing devices by walking over to them, this is worth an hour of your time.

You are regulated and your documentation is evidence

For DIFC, ADGM or DFSA-supervised firms, and for anyone who hands security documentation to enterprise clients, out-of-date terminology is a small but real credibility problem. A policy document referring to services that no longer exist reads as unmaintained, and an assessor who notices tends to look harder at the rest. Updating it is a quick fix and worth doing before somebody else finds it.

You operate in the UAE and elsewhere in the region

Apple states availability in over 200 countries and regions, so the account layer behaves the same across your UAE, wider GCC, Indian and European operations. Where organisations run into trouble is not the platform, it is procurement: devices bought locally in different markets through channels that cannot register them to your organisation. That fragmentation is worth fixing once, centrally.

Three positions organisations are in right now

Where UAE organisations actually stand after the consolidation.

The middle column is by far the most common and it is not a crisis. Nothing broke, because the migration was automatic. What it costs is the value nobody collected, and a documentation set that is quietly wrong.
Account exists and works
Migrated and reviewed
Migrated and ignored
Never had an account
Administrators are current employees
Migrated and reviewed
Migrated and ignoredOften not
Never had an accountNot applicable
Documentation uses current terminology
Migrated and reviewed
Migrated and ignored
Never had an accountNot applicable
Blueprints understood and in use
Migrated and reviewed
Migrated and ignored
Never had an account
Identity federation considered
Migrated and reviewed
Migrated and ignored
Never had an account
Unused app licences reclaimed
Migrated and reviewed
Migrated and ignored
Never had an accountNot applicable
Devices bought outside the account identified
Migrated and reviewed
Migrated and ignored
Never had an accountAll of them
Zero-touch deployment working
Migrated and reviewed
Migrated and ignoredUsually
Never had an accountNo
New starter setup is hands-off
Migrated and reviewed
Migrated and ignoredPartly
Never had an accountManual every time
Typical position in the UAE market
Migrated and reviewedUncommon
Migrated and ignoredThe default
Never had an accountSmaller firms
Where the built-in service fits

Apple built-in management against the platforms you may already run.

Every row here is stated from the side we can verify. Where the entry for Apple built-in reads not published, that is an accurate statement of what Apple has documented, not a claim that the capability is absent. Judge it on the rows where the other platforms have something specific and named.
Apple built-inMicrosoft IntuneJamf Pro
Cost to an existing Apple Business accountIncludedIn most Microsoft 365 plansSeparate licence
Manages Mac, iPhone, iPadYesYesYes
Manages Windows devicesNoYesNo
Configuration modelBlueprints and ConfigurationsPolicies and profilesPolicies, profiles, scripts
Zero-touch deploymentYes, via BlueprintsYesYes
Scripting and custom automationNot publishedLimited on macOSYes, extensive
Third-party patch management workflowsNot publishedYesYes
Device compliance gates access to company dataNot publishedYes, nativeThrough integration
One console across every platform you ownApple onlyYesApple only
Can be connected to Apple Business alongside othersYesYesYes
Sensible for a small Apple-only teamYesYesOften more than needed
Sensible for a mixed Windows and Apple estateApple side onlyYesApple side only
How the review runs

Five steps, and most estates are done in a morning.

This is deliberately small. The objective is to confirm the account is healthy, fix the documentation, and tell you whether anything else is worth doing. It is not a device management project.
  1. 1

    Verify the account and its people

    Sign in, confirm the migration took effect, check that administrators are current employees, confirm there is more than one of them, and check the reseller relationship that zero-touch depends on. This is also where we find the administrator who left in 2024, which happens more often than anyone expects.

  2. 2

    Reconcile devices against reality

    Compare what the account holds against what your people are actually carrying. The gap is nearly always devices bought outside the enrolment programme, usually from a retail store during a hiring push. We list them, and we tell you honestly which can be brought in and which practically cannot.

  3. 3

    Fix the terminology across your documentation

    Managed Apple ID becomes Managed Apple Account, Apps and Books becomes Get Apps and Get Books, Automated Device Enrolment becomes zero-touch deployment, and any reference to Apple Business Essentials comes out. We work through onboarding, offboarding, support scripts and policy documents, because those are the ones people follow literally.

  4. 4

    Build one Blueprint and show you how it works

    The fastest way to understand the new configuration model is to see a real one applied to a real device. We build a Blueprint appropriate to one of your user groups, apply it, and walk through what happened. Whether you adopt it further is then an informed decision rather than a theoretical one.

  5. 5

    Give you a written position on what to change

    One page: what is healthy, what we fixed, what we recommend, and what we specifically recommend against. For most organisations already running Intune or Jamf, the recommendation is to keep doing so. If we think the built-in service suits part of your estate, we say which part and why.

Straight answers

What people are actually asking about this change.

Post-consolidation review

Fifteen things to verify now that the dust has settled.

None of these are urgent and all of them are worth doing once. The first group is the account itself. The second is the documentation debt the rename created. The third is the opportunity, which is the part most organisations will skip.

Verify the account

  • Can you sign in and see your devices, purchases and people?
    The migration was automatic. Confirming it took effect takes two minutes.
  • Do you still have at least two administrators?
    Single-administrator Apple accounts are a standing risk, unrelated to this change.
  • Is the administrator contact somebody who still works for you?
    The most common finding we make on any Apple account review.
  • Is your device reseller still linked and supplying devices to the account?
    Zero-touch depends on this and nothing else.
  • Are your existing MDM connections intact?
    They should be. Confirm rather than assume.

Pay down the documentation debt

  • Update every reference to Managed Apple ID
    The term is now Managed Apple Account and new staff will not find the old one.
  • Update references to Apps and Books
    Now Get Apps and Get Books.
  • Update references to Automated Device Enrolment
    Now described as zero-touch deployment.
  • Update any mention of Apple Business Essentials
    The service no longer exists as a separate product.
  • Check your onboarding and offboarding runbooks end to end
    These are the procedures a new hire follows literally.

Take the opportunity most will skip

  • Learn what a Blueprint is and build one
    The most useful new concept, and the fastest to demonstrate value.
  • Review whether identity federation is worth enabling
    Managed Apple Accounts from your existing Entra or Google directory.
  • Reclaim app licences held by people who have left
    Almost every account we review is paying for some of these.
  • List Apple devices in use that are not in the account at all
    Retail-bought devices are the usual gap, and the usual surprise.
  • Decide whether the built-in service suits any part of your estate
    Multiple services can be connected. It does not have to be all or nothing.
Next step

One morning, and you will know exactly where you stand.

Tell us about your organisation account, connected MDM services, identity integrations and enrolment issues. We will confirm the requirements and proposed scope with you.