Can reserved-domain managed Apple Accounts test TestFlight?

Are managed Apple Accounts in reserved domains allowed to test TestFlight builds

No. Managed Apple Accounts created in reserved domains cannot test TestFlight builds, whether you are adding them as internal testers or inviting them as external testers. Apple states this in TestFlight help, and repeats it in the internal and external tester setup pages. Managed Apple Accounts are not the problem, the reserved domain is.

The part people get wrong is simple: they see that Managed Apple Accounts can use TestFlight and assume every Managed Apple Account works. Apple’s documentation separates those cases. A managed account in a custom verified domain can be used, but an account created in a reserved domain cannot test builds. That distinction matters before you set up a tester list.

For internal testing, Apple lets you add up to 100 internal testers, meaning App Store Connect users with access to your content. The internal tester limit is separate from the reserved-domain rule. A reserved-domain Managed Apple Account still cannot be added, even if you have room left in the 100-slot limit.

For external testing, Apple lets you invite external testers by email or by public link. External groups can include up to 10,000 people, and they may require TestFlight review before testing starts. That larger external limit does not override the reserved-domain restriction. If the tester’s Managed Apple Account was created in a reserved domain, it is still blocked.

Apple Business Manager explains why the reserved-domain detail exists. A reserved domain is automatically created for an organization, and Apple says you can use a custom domain instead of the reserved domain to create Managed Apple Accounts. In practice, that means a business or school can move to a verified custom domain if it wants those accounts to participate more broadly in Apple services.

A useful way to check the rule is to ask how the account was created, not just what kind of account it is. If the email address belongs to a Managed Apple Account made under a reserved domain, that tester cannot use TestFlight. If the account uses a custom verified domain, TestFlight can be available, subject to the rest of Apple’s testing setup.

If you are setting up testers for a real release, start by sorting addresses into three buckets: personal Apple Accounts, Managed Apple Accounts from custom domains, and Managed Apple Accounts from reserved domains. The third bucket is the one to exclude from TestFlight invitations. That avoids the common failure where invitations are sent, then the tester cannot join.

The inconvenient part is that Apple does not give a workaround inside TestFlight for reserved-domain Managed Apple Accounts. You do not fix it by switching from internal to external testing, by using a public link, or by waiting for review. The account itself is the blocker. If you need those people to test, they need a different eligible Apple Account.

For teams that want a place to coordinate testers for other platforms, DevConnect is free to use and stays free, and it is built around reciprocal testing rather than paid tester buying. For Apple TestFlight specifically, though, the eligibility rule comes from Apple, not from any third-party tool.

The cleanest setup is to verify tester emails before you send invites, especially in schools and businesses that use Apple Business Manager or Apple School Manager. If the organization uses reserved domains by default, expect those accounts to fail TestFlight access. If the organization has a custom verified domain, test one account first before building the whole tester list.

When this goes wrong, the failure usually looks like an invite that cannot be accepted or a tester who never appears in the group. That is not a TestFlight bug, it is the reserved-domain restriction doing exactly what Apple documents. Fix the account type first, then invite again.

In short: managed Apple accounts can test TestFlight only when they are not created in a reserved domain. Reserved-domain accounts are blocked outright, and Apple’s own help pages say so directly.