Apple Business Manager is gone, your account already moved itself, and nothing is broken. Here is what actually needs your attention.
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 there was no deadline and no manual step anyone missed. What did change is the terminology in your runbooks, a new configuration model called Blueprints, and a built-in device management capability you now hold for free. We review Indian organisations' accounts, fix the documentation, and give a straight answer on whether anything else should change.
- 14 April 2026Consolidation date
- AutomaticExisting accounts migrated
- 200 plusCountries served, India included
- BlueprintsThe new configuration model
Eight changes, and only three of them need you to do anything.
Three services became one, automatically
Apple Business Manager, Apple Business Essentials and Apple Business Connect are now a single platform called Apple Business. Existing accounts moved without any administrator action: same devices, same purchases, same people. There was no migration project to run and no deadline anybody missed, which is the single most reassuring fact about the whole change.
Blueprints, the new configuration model
A Blueprint is a preconfigured bundle of settings and apps assigned to devices or to a user group, described by Apple as configure once, deploy everywhere. Assign a group to a Blueprint and everyone in it receives its apps and configuration, which is what makes zero-touch setup work for new joiners. This is the one new concept genuinely worth learning.
Device management built in, at no cost
Apple Business now includes a built-in device management service using Configurations and Blueprints. For a small Apple-only Indian business with straightforward needs, this can genuinely be enough on its own, which was not true before April 2026. It does not make an existing MDM redundant, and Apple has not published a comparison between them, so we do not invent one.
Managed Apple IDs are now Managed Apple Accounts
The name changed; the concept did not. These remain the organisation-owned identities that separate work from a personal Apple Account and keep company data under company control. Every onboarding checklist, policy document and support script that still says Managed Apple ID now references a term that no longer appears in Apple documentation.
Federation with the directory you already run
Managed Apple Accounts can be provisioned from your existing identity provider, with Google Workspace and Microsoft Entra ID named explicitly. For Indian organisations on Microsoft 365, which is most of the market, the Apple identity layer connects to the directory you already operate instead of becoming a second set of accounts to administer.
App purchasing, under new names
What administrators knew as Apps and Books now appears as Get Apps and Get Books on the business side. The function is unchanged: the organisation buys licences, assigns them, and recovers them when someone leaves. The practical issue is that anyone following a pre-2026 procedure will hunt for a menu item that is no longer called that and conclude something is broken.
One account layer across every country you operate in
Apple states the platform is available in over 200 countries and regions. For Indian groups with offices in the Gulf, Singapore, the UK or the US, the account layer behaves consistently everywhere, which makes it one of the few parts of a multi-country estate that needs no regional variation. Procurement channels per country are the part that still needs care.
Your existing MDM stays connected
Apple documentation is explicit that Apple Business allows more than one device management service to be connected, with devices assigned between them as needed. Intune stays connected, Jamf stays connected, and the built-in service can run alongside them for a subset of devices. Nobody is being forced to choose, which is the most common misunderstanding we correct.
What we can tell you, and what we will not pretend to know.
A lot of confident writing about this change goes well beyond what Apple has published. Knowing which claims are verified and which are invented is more useful than a longer answer.
- Verified from Apple: the three services are consolidated into Apple Business, existing accounts migrated automatically, availability spans over 200 countries and regions, built-in device management provides Configurations and Blueprints, Managed Apple Accounts federate with Microsoft Entra ID or Google Workspace, and multiple device management services can be connected at once.
- Not published by Apple: a feature-by-feature comparison of the built-in device management service against a full third-party MDM. We will not invent that list, and you should be sceptical of anyone presenting one as authoritative.
- What we can compare is the other side, which is concrete: Intune manages Windows devices and ties device compliance into conditional access on your Microsoft 365 data; Jamf provides deep scripting and patch workflows for macOS. If you need those named things, the built-in service is not the whole answer, because those capabilities belong to those platforms.
- The practical advice for most Indian organisations is unexciting and correct: verify the account, learn Blueprints, update the terminology in your documents, and change nothing else without a reason. A consolidation that migrated your account for you is not an occasion to re-platform your device management.
Four reasons to have somebody look at this once.
Verified against Apple documentation, not commentary
Everything we tell you about this change is traceable to Apple's own published guidance, and where Apple has not published something, we say so instead of filling the gap with a confident guess. That distinction matters 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 surfaces the same findings: an administrator who left the company, devices in daily use that were never registered, app licences still assigned to former staff, and a reseller link nobody has checked in years. None were caused by the consolidation. All are worth finding before they matter.
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 a short list of documentation fixes and one recommendation about Blueprints. We do not use a free Apple capability as a pretext to propose re-platforming device management that already works, because that would be a bad trade for you.
We support the estate afterwards, not just the review
The review is short. What follows is the ordinary work of running an Apple estate: enrolment for new devices, leaver processing, licence recovery, keeping the account accurate. We do that remotely from Hyderabad under a managed arrangement with a 30 minutes response SLA and a named contact rather than a queue.
Six situations, and what the change means for each.
You used Apple Business Manager alongside Intune or Jamf
The most common position and the least affected. Your account migrated, the MDM connection is intact, and the change is terminology plus a free capability you can adopt or ignore. The work is a short verification and a documentation pass, not a project. Do not let anyone sell you a migration you do not need.
You used Apple Business Essentials to manage devices
The group that genuinely needs to pay attention: the product you administered no longer exists separately, and its function now sits inside Apple Business. Your devices did not stop being managed, but the administration surface and the concepts have moved, and that deserves a proper walkthrough rather than reverse-engineering from support articles.
You used Apple Business Connect for your brand presence
The service that handled how your business appears in Apple Maps is now part of the same platform as device management. Practically, a marketing function 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
The group that gained the most and mostly does not know it. Built-in device management with Blueprints for zero-touch setup, at no additional cost, is a real improvement in what a ten-person Mac-only firm in Bengaluru or Mumbai can do without buying anything. If you manage devices by walking over to them, this is worth an hour.
You are regulated, and documentation is evidence
For firms answering to a regulator or handing security documentation to enterprise clients, policies referring to retired product names read as unmaintained, and an assessor who notices tends to look harder at everything else. The terminology fix is quick, and worth doing before someone else finds it.
You operate in India and abroad
The platform serves over 200 countries and regions, so the account layer behaves the same across your Indian, Gulf and overseas offices. Where multi-country estates actually stumble is procurement: devices bought locally through channels that cannot register them to your organisation. That fragmentation is worth fixing once, centrally.
Where Indian organisations actually stand after the consolidation.
| Feature | Migrated and reviewed | Migrated and ignored | Never had an account |
|---|---|---|---|
Account exists and works | |||
Administrators are current employees | Often not | Not applicable | |
Documentation uses current terminology | Not applicable | ||
Blueprints understood and in use | |||
Identity federation considered | |||
Unused app licences reclaimed | Not applicable | ||
Devices bought outside the account identified | All of them | ||
Zero-touch deployment working | Usually | No | |
New starter setup is hands-off | Partly | Manual every time | |
Typical position in the Indian market | Uncommon | The default | Smaller firms |
Apple built-in management against the platforms you may already run.
| Apple built-in | Microsoft Intune | Jamf Pro | |
|---|---|---|---|
| Cost to an existing Apple Business account | Included | In most Microsoft 365 plans | Separate licence |
| Manages Mac, iPhone, iPad | Yes | Yes | Yes |
| Manages Windows devices | No | Yes | No |
| Configuration model | Blueprints and Configurations | Policies and profiles | Policies, profiles, scripts |
| Zero-touch deployment | Yes, via Blueprints | Yes | Yes |
| Scripting and custom automation | Not published | Limited on macOS | Yes, extensive |
| Third-party patch management workflows | Not published | Yes | Yes |
| Device compliance gating access to company data | Not published | Yes, native with Entra | Through integration |
| One console across every platform you own | Apple only | Yes | Apple only |
| Connectable to Apple Business alongside others | Yes | Yes | Yes |
| Sensible for a small Apple-only team | Yes | Yes | Often more than needed |
| Sensible for a mixed Windows and Apple estate | Apple side only | Yes | Apple side only |
Five steps, and most estates are done within days.
- 1
Verify the account and its people
Day 1
Sign in, confirm the migration took effect, check that administrators are current employees and that there is more than one, and verify the reseller relationship zero-touch depends on. This is also where we find the administrator who resigned in 2024, which happens more often than anyone expects.
- 2
Reconcile devices against reality
Day 1-2
What the account holds versus what your people actually carry. The gap is nearly always devices bought outside the enrolment channel, usually retail purchases made during a hiring push. We list them and say honestly which can be brought in and which practically cannot.
- 3
Fix the terminology across your documentation
Day 2-3
Managed Apple ID becomes Managed Apple Account, Apps and Books becomes Get Apps and Get Books, and references to Apple Business Essentials come out. We work through onboarding, offboarding, support scripts and policy documents, because those are what people follow literally.
- 4
Build one Blueprint and show how it works
Day 3-4
The fastest way to understand the new configuration model is to watch a real Blueprint apply to a real device. We build one for your most common role, apply it, and walk through what happened, so adopting it further is an informed decision rather than a theoretical one.
- 5
Give you a written position on what to change
Day 5
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 exactly that. If the built-in service suits part of your estate, we say which part and why.
What Indian organisations are actually asking about this change.
Fifteen things worth verifying now that the dust has settled.
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 accounts are a standing risk, unrelated to this change.
- Is the administrator contact someone who still works for you?The most common finding on any Apple account review.
- Is your reseller still linked and registering devices?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 IDThe term is now Managed Apple Account, and new staff will not find the old one.
- Update references to Apps and BooksNow Get Apps and Get Books on the business side.
- Update descriptions of automated enrolmentApple now frames it as zero-touch deployment through Blueprints.
- Remove mentions of Apple Business EssentialsIt no longer exists as a separate product.
- Walk the onboarding and offboarding runbooks end to endThese are the procedures a new hire follows literally.
Take the opportunity most will skip
- Learn what a Blueprint is and build oneThe most useful new concept, and the fastest to demonstrate.
- Review whether identity federation is worth enablingManaged Apple Accounts provisioned from your Entra or Google directory.
- Reclaim app licences held by people who leftAlmost every account we review is carrying some.
- List Apple devices in use that are not in the account at allRetail purchases are the usual gap, and the usual surprise.
- Decide whether the built-in service suits any part of your estateMultiple services can be connected. It is not all or nothing.
The pages around this one.
Apple Business Manager
The foundation-layer explainer: what the organisation account does and why where you buy a Mac decides whether you can ever fully manage it.
Learn moreApple device management in India
The whole estate picture: the account layer, the platform choice, and the operating disciplines that keep an Apple fleet managed over time.
Learn moreManaged Apple Accounts
The organisation-owned identity these changes renamed, and the published service exclusions worth reading before rollout.
Learn moreA short review, and you will know exactly where you stand.
Your account already moved and nothing is broken. What a review adds is confirmation of that, documentation that matches reality, a list of devices that were never in the account, and a straight answer on whether the new built-in capability is worth anything to you. For most organisations the recommendation is to change very little, and we will say so in writing. Enquiries answered within 4 business hours.