Signing up for Apple Business takes about ten minutes and is free. Proving to Apple that your organisation is real is the part with a deadline attached, and if you miss it Apple deletes everything you built. Almost none of the advice you will find online describes the current process, because almost all of it is describing a different Apple programme entirely.
I want to deal with the D-U-N-S question first, because it comes up in every engagement and because the received wisdom is wrong in a way that costs small organisations weeks. The received wisdom says you cannot enrol without a nine digit Dun and Bradstreet identifier, that obtaining one takes up to five business days plus two more for Apple to receive it, that sole traders and unincorporated businesses are excluded, and that trading names and branches are not accepted. Every one of those statements is true. None of them is about Apple Business.
They are the rules of the Apple Developer Program. Apple publishes them on a developer support page that scopes them in its second sentence, stating that your D-U-N-S number is used to check your organisation’s identity and legal entity status “as part of our enrollment verification process for joining the Apple Developer Program or the Apple Developer Enterprise Program”. Because that page ranks well and reads authoritatively, it has been absorbed into a decade of blog posts about device management, and the two programmes have been conflated in the community’s collective memory ever since. If you have been putting off Apple Business because your business does not have a D-U-N-S number, you have been solving a problem you do not have.
What Apple actually asks for
Verification in 2026 requires two methods, and you choose the first from three options that are not equally onerous. You can supply a Business ID, which Apple describes as a D-U-N-S number or an Employer Identification Number. You can prove control of a domain by adding a TXT record to your DNS. Or, if your organisation publishes an app, you can point Apple at it through App Store Connect. The second method is an uploaded document, and Apple’s accepted list is deliberately broad: a business license, a sales tax permit, a food or health or alcohol permit, a lease or property agreement, a utility bill, or a catch-all other.
Read that combination carefully, because it is the interesting part. A business with a domain name and a utility bill in its own name can satisfy both methods without producing a registry identifier of any kind. Nothing in Apple’s sign-up flow or its verification requirements imposes an entity test, which is a real and unannounced departure from the Developer Program language. The old community workaround of registering a limited company purely to obtain a D-U-N-S number so you could enrol in Apple’s device programme now looks unnecessary.
I will not pretend this is tidy on Apple’s side, and you should know what you will run into if you go looking for confirmation. The sign-up page names D-U-N-S and points you at a linked reference table of accepted Business ID types, and that table does not contain the string D-U-N-S anywhere. It defines a Business ID in tax terms, as a unique identifier assigned to organisational entities for tax purposes, and lists a single federal taxpayer identification entry for the United States. It appears to have been inherited from Apple Business Connect and repurposed without anyone reconciling it against the sentence that links to it.
The glossary is worse, and I would rather you hear it from me than find it and conclude I have oversold this. Apple’s current Apple Business glossary defines an organization as “a legal entity with a D-U-N-S number”, and defines the D-U-N-S number itself with the note that Apple cross-checks programme enrollees against the Dun and Bradstreet database. Read literally, that requires the exact thing the sign-up page makes optional. My reading is that the glossary is inherited text that nobody revised, because the operative pages, the ones that actually gate your organisation, offer three first methods and impose no entity test. But it is Apple’s own current documentation and it contradicts the flow, so if you are the sort of person who needs the written rule to match the behaviour before you commit a business decision to it, this one does not.
There is a third loose end in the same area, harmless but disconcerting. Apple still carries one sentence about verification depending on whether it can reach your provided contact, on a page that no longer has a contact field anywhere in it. The old process involved Apple telephoning a senior person at your organisation to confirm you existed, and Apple School Manager still works that way. Apple Business does not, and that sentence is what is left behind.
The clock, and what happens when it runs out
You get sixty days from creating the organisation to verify it. Apple’s review of a submitted verification takes up to five business days, and longer during high volume periods. Those two numbers should be read together rather than separately, because the second one eats the first. Submitting on day fifty-eight is not submitting on time if Apple comes back asking for a different document.
What happens if you miss it is stated by Apple without hedging: if your organisation is not approved during the verification window, your organisation, your data, and your Managed Apple Accounts are deleted. Not suspended. Not locked pending review. Deleted. This is the first of many one way doors in Apple Business and it is the cheapest one to avoid, because avoiding it costs nothing except doing the verification in the first week rather than the ninth.
Verify in week one. The sixty day window is not a grace period, it is a countdown with a five day review inside it.
The domain verification path carries its own shorter clock, and it is easy to trip over. Once you add a domain and Apple issues the TXT record, you have fourteen calendar days to complete the check or you start the domain over. Fourteen days is generous if your DNS is somewhere you have access to, and tight if your DNS is at a registrar controlled by a marketing agency who last answered an email in March. Find out which situation you are in before you start the timer.
The account you sign up with is not a normal account
The person who signs up becomes the first Organization Administrator, and Apple has firm views about who that person may be. The name must be a legal human name, and Apple states that first and last names such as IT Coordinator or iPad Deployment are returned to you to correct. If you go and check that, Apple gives the second example as Apple Deployment on the sign-up page and iPad Deployment on the requirements page, which is a trivial inconsistency but exactly the kind that makes a reader think they have caught somebody misquoting. The email address must not already be an Apple Account, must not be associated with an App Store or iCloud account, and must not belong to a domain another Apple School Manager or Apple Business organisation has already verified. It may be a public email address, and Apple says why outright: if you do not own a custom domain name, use a public email provider for this account, and every subsequent Managed Apple Account will use a reserved domain Apple sets up for you automatically.
Apple then adds a warning that is easy to skim past and expensive to ignore: do not use this new Organization Administrator account with an App Store or iCloud account or any other Apple service. This account exists to administer your organisation. The moment somebody signs into a personal iPhone with it because it was the Apple account they had to hand, you have entangled your administrative identity with a consumer service, and disentangling Apple accounts is not a five minute job.
You can hold up to ten Organization Administrators in total, the founder plus nine more, and you should create at least a second one on day one. The reason is not resilience in the abstract. It is that when Apple updates its terms and conditions, an Organization Administrator has to sign in and accept them, and until somebody does, most of the functionality in Apple Business is unavailable. A single administrator on annual leave when Apple revises its agreement is an outage with a very silly cause. Who else should hold which role, and why the answer is not simply everybody, is the subject of the next article.
What signing up buys you, and what it does not
An unverified organisation is not a working organisation. Apple’s phrasing is that after verification you can unlock all Apple Business features, which is a marketing way of saying that until then you have an account and not much else. Plan the verification as the first task, not as paperwork to be caught up with once the interesting configuration is done.
Once verified, one number is worth knowing immediately because it governs what you can recover from your purchase history. Apple keeps a record of every order your organisation placed directly with Apple after the first of March 2011, and once you enter your Apple Customer Number those devices become visible to you. Resellers and carriers may not keep records going back that far, and Apple says so, pointing you at the reseller to establish your own account’s timeline. For an organisation that has been buying Macs from Apple directly for a decade, that is a substantial fleet appearing in the register at no effort. For one that bought everything from a carrier, it is nothing at all until you do the supplier linking work in [AB 6].
What signing up does not buy you is any managed device. Apple Business is a register, and at this point it is an empty one. Nothing in it enrols anything, nothing in it configures anything, and connecting it to Intune is three articles away. That is the correct order and it is worth resisting the temptation to skip ahead, because the identity decisions in the next two articles are considerably harder to change afterwards than the Intune connection is.
The build sheet that follows takes an organisation from nothing to verified, with the checks that stop you discovering on day fifty-nine that your document was never going to be accepted.
Apple Business
‹ Previous: [AB 1] Apple Business: The System of Record Your Apple Estate Runs On
Next: [AB 2.1] Build Sheet: Sign-Up, Verification, and the Organization Profile ›
