Managed Apple Accounts in Reserved Domains and TestFlight

Do Managed Apple Accounts in reserved domains now fail TestFlight testing

Yes. Apple now states that Managed Apple Accounts created in reserved domains can’t be used to test builds in TestFlight, so those accounts fail at the point where testing should start. The important part is not the invite, it is the account type attached to the email address.

The part people get wrong is assuming every Managed Apple Account behaves the same. Apple separates reserved domains from custom domains in Apple Business Manager and Apple School Manager. Reserved domains are created automatically for the organization, while custom domains are verified domains that the organization owns and manages. Apple’s TestFlight help ties the restriction specifically to accounts created in reserved domains.

That means a tester can have a valid Managed Apple Account and still be blocked from TestFlight if the account email sits in the reserved domain. Apple’s wording is direct: Managed Apple Accounts created in reserved domains can’t be used to test builds. The failure is about eligibility, not about whether TestFlight is working.

Apple’s domain guidance explains why this happens. A reserved domain is automatically created for an organization, and it is based on the website entered during sign-up. Apple also says a custom domain can be used instead of the reserved domain to create Managed Apple Accounts. In practice, that is the path that avoids this specific TestFlight problem.

The inconvenient part is that this is easy to miss until someone actually tries to test. A team can set up a clean beta flow, send invitations, and only then find that a subset of internal users cannot complete the TestFlight step because their Managed Apple Accounts were created under the reserved domain. The result is not a vague Apple warning, it is a hard stop for those accounts.

For teams using Apple Business Manager, the fix is organizational, not technical. Apple’s documentation points to using a custom domain, or managing accounts through domain verification and domain capture when the goal is to ensure accounts on that domain are Managed Apple Accounts. If the account stays on the reserved domain, Apple’s TestFlight page says it cannot be used to test builds.

This is also separate from the question of how many testers TestFlight supports. Apple says TestFlight supports external testing and that Managed Apple Accounts, except users with the Student role, can use TestFlight, but the email address can’t be the reserved domain. Internal team workflows and external beta workflows are different, and the reserved-domain rule applies to the account email either way.

A concrete example helps. If your company signs up with a reserved domain like name.appleaccount.com and creates qa@name.appleaccount.com as a Managed Apple Account, that account cannot be used to test builds in TestFlight. If the same person is moved to a verified custom domain account, TestFlight can work again as long as the account meets Apple’s other service rules.

If you are checking a beta group now, look at the email domain before you look at the app, the invitation, or the build. That is usually where the issue is. Apple’s current documentation makes the rule explicit, and the reserved-domain restriction is the first thing to clear when Managed Apple Accounts fail TestFlight testing.