Skip to main content
This guide applies to Apple devices
We encourage you to try Apple beta OS releases and share what you find. Beta operating systems aren’t supported through our normal support channels (such as live chat), so please send any beta‑related feedback to apple-beta-feedback@iru.com for direct review by our R&D team.

​
About Testing Apple Beta Releases

Apple beta programs such as AppleSeed for IT and the Apple Beta Software Program let you evaluate upcoming OS releases before they are publicly available. Organizations often enroll a limited set of devices so IT can validate apps, configurations, and workflows against pre-release builds. Iru Endpoint supports three ways to manage Apple beta program enrollments and version enforcement. Use the option that fits your goal: enrollment during Setup Assistant, a required beta build after enrollment, or an opt-in experience for users. For Managed OS enforcement details, see Understanding Managed OS for Apple Platforms. To keep devices on stable releases and block beta enrollment, see Restrict Access to Beta OS Releases. When you are actively testing betas, use apple-beta-feedback@iru.com for product feedback related to Iru Endpoint on beta OS releases.

​
Ways to Manage Apple Beta Program Enrollment

​
At enrollment, using the ADE Library Item

Use Require minimum OS version in the Automated Device Enrollment Library Item to enforce a beta enrollment and an OS upgrade or beta update before the device enrolls into Iru Endpoint. This is helpful for testing enrollment-time configurations on new OS releases. For beta targets, set Custom, select This is a beta version, and choose a Seed Token. Iru applies Software Update Settings (beta enrollment) and then Software Update Enforcement (to the specified version) during Setup Assistant. For steps, see Require Minimum OS Version in Configuring Apple Enrollment.

​
Managed OS

Use Managed OS to enforce a beta program enrollment and a specific beta release together after enrollment. Enrollment and version enforcement stay in one Library Item. Managed OS applies Software Update Settings, then Software Update Enforcement, for the Seed Token and build you configure. For behavior and configuration, see Understanding Managed OS for Apple Platforms, Configure Managed OS for macOS, and Configure Managed OS for iOS, iPadOS, and tvOS.

​
Software Update Library Item

Use the Software Update Library Item to test the end user experience of updating or upgrading manually, or to offer one or more beta program enrollments for user opt-in, without requiring a specific beta version at the same time. Under Other, in iPhone, iPad, Mac only settings, set Beta program enrollment to one of the following:
  • Not configured: Do not manage beta enrollment from this Library Item. Use this when Managed OS or ADE handles beta enrollment and version enforcement.
  • Disallow: Prevent users from enrolling in beta programs from Software Update settings. See Restrict Access to Beta OS Releases.
  • Offer: Present one or more selected beta programs so users can opt in on the device.
  • Enforce: Enroll the device in a selected beta program without requiring a specific beta OS version. To enforce a specific beta version, keep Beta program enrollment as Not configured and use Managed OS instead.
Offer and Enforce are supported on macOS 15.4+ and iOS/iPadOS 18.0+. When you choose Offer or Enforce, select the Beta programs to apply (for example, Seed Tokens synced from Apple). For full Software Update configuration, including deferrals and automatic updates, see Delay and Enforce OS Updates.
Beta seed builds are exempt from Software Update deferral on devices already enrolled in an Apple beta software program. Deferral periods also do not apply to updates deployed by MDM.

​
Request AppleCare Enhanced Log Collection (iOS and iPadOS)

AppleCare may ask you to run enhanced log collection on a device that is testing an Apple beta. On supervised iPhone and iPad devices running iOS 27+ or iPadOS 27+ beta releases, you can trigger that collection from the device record in Iru Endpoint after AppleCare provides a token.

​
Requirements

  • Supervised iPhone or iPad enrolled in Iru Endpoint
  • Device currently running an iOS 27+ or iPadOS 27+ beta release
  • AppleCare token provided for the enhanced log collection request

​
Trigger Enhanced Log Collection

1

Open the Device Record

Go to the Devices page and select the iPhone or iPad that is testing an Apple beta.
2

Open the Device Action Menu

Open the Device Action Menu (ellipsis) in the upper right corner of the device record, then select Trigger enhanced log collection.
3

Enter the AppleCare Token

In the Trigger enhanced log collection dialog, enter the AppleCare token provided by AppleCare, then click Trigger enhanced log collection.
4

Confirm the Request Status

After you submit the request, the device record shows an Enhanced log collection status banner (for example Requested) while collection proceeds.

Delay and Enforce OS Updates

Configure the Software Update Library Item, including beta program enrollment

Restrict Access to Beta OS Releases

Prevent users from enrolling devices in Apple beta programs

Understanding Managed OS for Apple Platforms

Enforce OS versions, including Apple beta builds with a Seed Token

Configuring Apple Enrollment

Enforce a beta OS at ADE before enrollment completes

AppleCare Enterprise Support

When and how to work with AppleCare Enterprise Support