Skip to main content
Apple Business migration, India

Apple Business Manager is gone, your account already moved itself, and nothing is broken. Here is what actually needs your attention.

Three separate services became one platform in April 2026, and the whole thing happened without asking you. No deadline to miss, no manual step for anyone to forget, and your account came out the other side intact. Three things genuinely did change: the vocabulary your runbooks are written in, a configuration model called Blueprints that did not previously exist, and a device management capability you now own at no charge. We audit Indian organisations' accounts, repair the documentation, and tell you plainly whether anything further deserves attention.

Book an Apple Business reviewSee what changed
  • 14 April 2026Consolidation date
  • AutomaticExisting accounts migrated
  • 200 plusCountries served, India included
  • BlueprintsThe new configuration model
What actually changed

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

A great deal of the commentary on this change has been considerably more dramatic than the change itself. Your account moved quietly and without involving you. Three things do deserve some of your time: the capability you have gained for nothing, the words that no longer mean what your documents think they mean, and the assumptions baked into procedures written before any of this. For an Indian organisation already running an MDM, the honest scope is a verification pass and an afternoon spent fixing documents.

Three services became one, automatically

What used to be three products is now one, under the name Apple Business. Nobody had to lift a finger for it: your devices came across, your purchases came across, your people came across. There was never a project to staff and never a cut-off to miss, and of everything on this page that is the fact worth leading with when somebody senior asks what happened.

Blueprints, the new configuration model

Think of it as a bundle you prepare once, containing settings and applications, and then point at either devices or a group of people. Attach a group and every member picks up whatever the bundle carries, which is the mechanism behind a new joiner opening a laptop that already knows what it is for. Of everything introduced here, this is the concept actually worth an hour of your time.

Device management built in, at no cost

There is now a management service inside the platform itself, built around Configurations and Blueprints. A small Indian business running nothing but Apple hardware, with requirements that are not exotic, may find this sufficient on its own, and that genuinely was not the case a year ago. It does not obsolete your existing MDM. No feature comparison between the two has been published, and we are not going to write one and pass it off as authoritative.

Managed Apple IDs are now Managed Apple Accounts

A rename, nothing more. The idea is untouched: identities the business owns, keeping work separate from whatever personal account somebody signed up for years ago, with company data staying on the company side. The practical consequence is that every onboarding checklist, policy PDF and support script in your organisation is now using a phrase that appears nowhere in current documentation.

Federation with the directory you already run

Those accounts can be created straight from the directory you already run, with both Google Workspace and Microsoft Entra ID supported by name. Since most of the Indian market sits on Microsoft 365, that generally means the Apple identity layer attaches to something you already administer rather than becoming a second list of people for somebody to keep in step manually.

App purchasing, under new names

The section administrators knew by one name now carries another on the business side. Nothing about how it works has moved: you purchase licences, you allocate them, and you take them back when people leave. The problem is entirely human. Somebody working from a procedure written in 2025 will search for a menu entry that no longer goes by that name, fail to find it, and raise a ticket saying the console is broken.

One account layer across every country you operate in

Availability spans over 200 countries and regions. So an Indian group with people in the Gulf, Singapore, London or the United States gets identical account behaviour in each of them, which makes this one of the very few components of a multi-country estate needing no regional variation at all. Where care is still required is procurement, because the buying channel differs country by country.

Your existing MDM stays connected

The documentation is unambiguous that several management services may be attached at once, with hardware allocated between them however you need. Your Intune connection persists, your Jamf connection persists, and the built-in service is free to handle some subset of machines beside them. There is no forced choice here, and correcting that assumption is probably the single most frequent conversation we have on this topic.

The honest version

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

There has been a fair amount of very assured writing about this that runs a long way past anything actually published. Being able to separate the documented from the imagined is worth more to you than a longer article would be.

  • Documented and checkable: three products became one, accounts moved themselves, coverage runs past 200 countries and regions, the built-in management service works through Configurations and Blueprints, identities can be federated from Entra ID or Google Workspace, and several management services may be connected simultaneously.
  • Not documented anywhere: any line-by-line capability comparison between the built-in service and a full third-party MDM. We decline to manufacture that list, and we would encourage a healthy scepticism toward anybody who hands you one and calls it definitive.
  • The comparison that can honestly be made runs the other direction, because those products have named, specific capabilities. Windows management and compliance-gated access to your Microsoft 365 data on one side, deep scripting and patch workflows for the Mac on the other. Need any of those by name and the built-in service is not your complete answer, since those things belong to those platforms.
  • For most organisations the correct advice here is dull and accurate. Check the account works, spend an hour on Blueprints, fix the vocabulary in your documents, and leave everything else exactly where it is unless you have a reason. A consolidation that quietly migrated your account for you is not an invitation 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.

The effort involved is modest and the return is out of proportion to it, largely because the exercise turns up problems that were already sitting there and that nobody had a reason to go looking for until now.

Verified against Apple documentation, not commentary

Anything we assert about this change can be traced back to the official guidance, and wherever the official guidance is silent, we tell you it is silent rather than papering over the gap with something plausible. That distinction earns its keep here, because an enormous amount of secondhand material has been written about this consolidation and a good deal of it is simply incorrect.

We find the problems that predate the change

The findings repeat with remarkable consistency across these reviews. An administrator who resigned two years ago. Hardware people use daily that was never registered anywhere. Licences still sitting with former colleagues. A reseller relationship nobody has confirmed since it was set up. The consolidation caused none of them, and every one is better discovered now than during an incident.

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

Running Intune or Jamf successfully? Then the right output from this piece of work is a brief list of documents to update plus a single suggestion about Blueprints. A capability that arrived free is not a reason for us to propose tearing out management that already does its job, because you would be worse off and we would rather keep the relationship.

We support the estate afterwards, not just the review

A review takes days. Everything after it is the unglamorous ongoing business of operating an Apple estate: getting new hardware enrolled, processing departures, pulling licences back, and keeping the account reflecting reality. That runs remotely out of Hyderabad on a managed arrangement, with a 30 minutes response SLA and somebody whose name you know rather than a ticket queue.

Who this affects and how

Six situations, and what the change means for each.

How much this affects you depends entirely on which of the three products you were using beforehand. Below are the six positions we encounter across Indian organisations, ordered loosely by how much of your attention each one deserves.

You used Apple Business Manager alongside Intune or Jamf

Where most organisations sit, and the position that changed least. The account came across, the connection held, and what you are left with is some new vocabulary plus a free capability you may take up or leave alone entirely. Half a day of checking and an afternoon fixing documents. Anybody proposing a migration project to you here should be asked which page of the documentation calls for one.

You used Apple Business Essentials to manage devices

This is the group with genuine work to do. The product you logged into every week does not exist as a separate thing any more, and what it did now lives inside the combined platform. Nothing stopped being managed, but the console you use and the concepts you think in have both shifted, and that warrants somebody walking you through it rather than piecing it together from support articles at eleven at night.

You used Apple Business Connect for your brand presence

Whatever governed how your business shows up in Apple Maps now lives on the same platform as your device management. In practical terms that means a marketing responsibility and an IT responsibility have ended up sharing a console, which is an internal ownership problem rather than a technical one. Settle who administers which part before somebody changes something and it becomes an argument.

You are a small Apple-only business with no MDM

The biggest winners, and almost none of them are aware of it. Getting device management with Blueprint-driven setup thrown in at no extra cost meaningfully raises what a ten-person Mac shop in Bengaluru or Mumbai can accomplish without spending anything. If your current method of managing devices involves walking across the office to them, give this an hour of your time.

You are regulated, and documentation is evidence

When you are answerable to a regulator, or sending security documentation out to enterprise customers, a policy citing product names that were retired last year reads as neglected. An assessor who spots one starts examining everything else with more interest. Correcting the vocabulary takes very little time and is much better done by you than discovered by them.

You operate in India and abroad

With coverage beyond 200 countries and regions, the account layer behaves identically whether the office is in Hyderabad, Dubai or Singapore. What actually trips up multi-country estates is buying, not managing: hardware purchased locally through a channel that has no way to register it to your organisation. Sorting that fragmentation out once, centrally, saves years of irritation.

Three positions organisations are in right now

Where Indian organisations actually stand after the consolidation.

Nearly everyone is in the middle column, and it is not an emergency, precisely because nobody had to do anything for the move to succeed. The cost is subtler: value sitting there uncollected, and a set of documents that have become quietly inaccurate.
Feature
Migrated and reviewed
Migrated and ignored
Never had an account
Account exists and works
Administrators are current employees
Often notNot 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
UsuallyNo
New starter setup is hands-off
PartlyManual every time
Typical position in the Indian market
UncommonThe defaultSmaller firms
Where the built-in service fits

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

Each row is written from whichever side has published something checkable. A "not published" entry in the first column describes the state of the documentation, and should not be read as an assertion that the capability is missing. Weigh the table on the rows where the other two platforms offer something concrete 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 gating access to company dataNot publishedYes, native with EntraThrough integration
One console across every platform you ownApple onlyYesApple only
Connectable 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 within days.

We have kept this deliberately compact. Four objectives: confirm the account is in good order, repair the documents, show you the new configuration model working, and give you an opinion on whether anything further is worth your money. It is not, and should not turn into, a device management project.
  1. 1

    Verify the account and its people

    Day 1

    We log in, satisfy ourselves the move actually landed, establish that your administrators still work for you and that there is more than one of them, and confirm the reseller relationship your automated enrolment quietly depends on. This is also the step where the administrator who resigned two years ago turns up, which happens far more often than anybody anticipates.

  2. 2

    Reconcile devices against reality

    Day 1-2

    We compare what the account believes you own against what people are genuinely walking around with. The difference is almost always hardware acquired outside the proper channel, typically bought over a counter during a hiring rush when somebody needed a laptop that week. Each one gets listed, with an honest note on whether it can realistically be brought in.

  3. 3

    Fix the terminology across your documentation

    Day 2-3

    Three renames get applied and one retired product name gets removed entirely. The sweep covers joining procedures, leaving procedures, support scripts and policy documents, because those are the artefacts people follow word for word without stopping to interpret them.

  4. 4

    Build one Blueprint and show how it works

    Day 3-4

    Nothing explains the new model faster than seeing one land on an actual machine. So we construct one covering whichever role you have most of, apply it, and then talk through exactly what happened and why. Any decision you subsequently take about using them more widely is then based on something you watched rather than something you read.

  5. 5

    Give you a written position on what to change

    Day 5

    A single page covering four things: what is in good shape, what we repaired, what we suggest, and what we are explicitly advising you not to do. Where Intune or Jamf is already in place and working, that suggestion is usually to carry on unchanged. Where the built-in service does suit some portion of your estate, we name the portion and explain the reasoning.

Straight answers

What Indian organisations are actually asking about this change.

It was consolidated into a platform called Apple Business on 14 April 2026, together with Apple Business Essentials and Apple Business Connect. The name Apple Business Manager is no longer current, which is why searching for it now returns a mix of pages about a product that exists under a different name and pages written before the change. Your account was not deleted and your data did not move to a new system: if you had an Apple Business Manager account, you have an Apple Business account with the same devices, purchases and people.

No. Existing accounts migrated automatically, which is the single most reassuring fact about the change and the one most often missed. There was no deadline, no manual step, and no window anyone failed to act in. What is worth doing is a verification pass: confirm the account is healthy, that your administrators are current employees, that the reseller link is intact, and that your MDM connection carried over. That is an afternoon of checking, not a migration project, and a supplier proposing the latter should be asked which Apple documentation calls for it.

Not unless you want it to. Apple documentation is explicit that Apple Business allows more than one device management service to be connected, with devices assigned between services as needed, so your Intune or Jamf connection continues working exactly as before. The built-in service is an additional option, not a replacement, and for an organisation with working device management the sensible default is to change nothing. Where it genuinely helps is the small Apple-only Indian business that never had an MDM at all: that group gained a real capability for free.

A preconfigured bundle of settings and apps that you assign to devices or to a group of users, described by Apple as configure once, deploy everywhere. Assign a user group to a Blueprint and everyone in it receives the apps and configuration it contains, which is what makes zero-touch deployment work for new employees: the sealed box arrives, the device is powered on, and it configures itself. If you build one thing after reading this page, build a Blueprint for your most common role and watch what happens on the next new device.

For a small Apple-only organisation with straightforward requirements, plausibly yes, and that is a genuine change from the pre-2026 position. For anything more complex, the honest answer is that Apple has not published a feature comparison against third-party MDM, so anyone handing you a definitive limits list is going beyond the published record. What can be said concretely comes from the other side: if you need Windows management, Intune covers it and this does not; if you need deep scripting or patch workflows on macOS, Jamf provides those. Decide from the requirements you actually have.

The organisation-owned Apple identity for an employee, previously called a Managed Apple ID. The concept is unchanged: it separates work from personal, belongs to your organisation rather than the individual, and is what lets you keep control of company data when somebody leaves. The rename is a documentation problem rather than a technical one, but it is real: a new hire following a runbook that says Managed Apple ID will be looking for a term Apple no longer uses, and will reasonably conclude the runbook is wrong about other things too.

Yes. Apple names Microsoft Entra ID explicitly, alongside Google Workspace and other identity providers, as directories that can provision Managed Apple Accounts using existing organisation credentials. For Indian organisations on Microsoft 365, which is most of the market, this is worth serious consideration: it removes a second identity to administer, people sign in with credentials they already hold, and offboarding someone in Entra ID reaches their Apple identity instead of leaving it as a separate task somebody forgets.

It no longer exists as a separate product; its function is now part of Apple Business. This is the most affected group, because unlike account-only users, these organisations were actively administering devices through it. The devices did not stop being managed, but the administration surface and the concepts have changed, and if this is your position it deserves a proper walkthrough rather than being reverse-engineered from support articles between other work.

No, and this confusion needs correcting regularly. Apple School Manager was not part of the consolidation and continues as the education service. Schools reading the business-side coverage have repeatedly assumed the same applied to them, and it did not. If you run a school, coaching institute or university in India, your Apple School Manager account and the way you administer it are unchanged by anything on this page. Our Apple School Manager page covers what is worth checking in an education account for its own reasons.

Yes. Apple states availability in over 200 countries and regions, and Indian organisations use the platform routinely. For groups operating across India, the Gulf, Singapore or beyond, the account layer behaves consistently everywhere, which makes it one of the simpler parts of a multi-country estate. Where regional differences genuinely bite is procurement: whether a device bought in a particular market can be registered to your organisation depends on the channel it came through, so the purchasing route deserves more attention than the platform.

More than you would expect, for two reasons. New staff follow procedures literally, so a runbook naming a menu item that no longer exists produces a support call and a small loss of confidence in the documentation generally. And for regulated firms or anyone answering enterprise security questionnaires, a policy referring to retired services reads as unmaintained, and an assessor who notices tends to look harder at everything else. It is a quick fix, and it is better done before somebody else finds it.

Almost certainly yes, and it costs nothing. Without an organisation account there is no zero-touch enrolment, no organisation-owned identity, no proper app licence ownership, and no reliable recovery when a device comes back from a departing employee with a personal account attached. The one caveat is permanent: devices bought before the account existed cannot all be brought in retrospectively, so the sooner the account and the reseller link exist, the smaller that gap stays. Enquiries reach us and get a reply within 4 business hours.
Post-consolidation review

Fifteen things worth verifying now that the dust has settled.

Nothing below is urgent and everything below rewards being done once, properly. Group one is the account. Group two is the debt the renaming left in your documents. Group three is the opportunity that most organisations are going to walk straight past.

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 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 on the business side.
  • Update descriptions of automated enrolment
    Apple now frames it as zero-touch deployment through Blueprints.
  • Remove mentions of Apple Business Essentials
    It no longer exists as a separate product.
  • Walk the 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.
  • Review whether identity federation is worth enabling
    Managed Apple Accounts provisioned from your Entra or Google directory.
  • Reclaim app licences held by people who left
    Almost every account we review is carrying some.
  • List Apple devices in use that are not in the account at all
    Retail purchases 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 is not all or nothing.
Related reading

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 more

Apple 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 more

Managed Apple Accounts

The organisation-owned identity these changes renamed, and the published service exclusions worth reading before rollout.

Learn more
References

Official documentation

Next step

A 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.

Book an Apple Business reviewSee what changed