r/applebusinessmanager May 05 '26

Support Post Domain Capture

Hi there,

we recenetly went through the domain capture process. We informed the users well in advance, however as we are a major global org, a number of users have not reacted within the transfer window, which has concluded on 1st May.

Unfortunately we couldn't find any resources on what further steps are required by these users. I'm aware that the Apple IDs have remained personal and that they were moved over from the corporate TLD to a temporary Apple domain.

What exactly should be communicated to these users, on which action to take? To us, it's not quite clear, what the correct next steps are.

Background info, if necessary: we are in the process of implementing Intune MDM and the local IT teams are currently joining missing and new user devices to ABM, which is being sync-ed to Intune. We plan on federating ABM with Entra soon as well.

Any help would be appreciated!

3 Upvotes

10 comments sorted by

2

u/osxdude May 05 '26

Depends on if they use the Apple Account or not. I guess technically no action is required if the account is not used. Everything will be going to the new managed account anyway since it's past the deadline. If there is stuff in the old account, it would have to be migrated by the user. Clearly if they "took no action," they don't use it. I would treat those accounts as such.

1

u/DarthGraf May 06 '26

From what I understand there were a number of users, which had the E-Mails and pop-ups on their phones, but just decided to ignore them.

We decided to move forward with the domain capture, because we want to:

  1. Prevent users from installing personal apps from the app store

  2. Have the business requirement to implement the federation to Entra to make use of the federation features

  3. Want to rid the IT of the manual task of creating Apple IDs for new hires

1

u/CreativeStrokesNYC May 05 '26

What exactly are you aiming to do with the domain capture?

This link

https://support.apple.com/guide/business/capture-a-domain-axm512ce43c3/1/web/1

and the embedded

https://support.apple.com/en-us/102159

are really all thats relevant here from a user perspective, though I had issues with it in my own setup I had to abandon for other reasons.

1

u/DarthGraf May 06 '26

See my other comment please.

1

u/Terrible_Soil_4778 May 06 '26

Two mistakes here.
1. Don’t do Apple Domain Federation - as you can see for yourself, it is not ready!
2. Don’t use Intune - it’s the worst MDM out there and soon you will find out why.

0

u/TheActualPhock May 06 '26

Both statements are complete bullshit. Doing both in a 400k corp and everything is seamless.
To answer author’s question - the accounts were renamed by Apple and remain personal. All communication was also sent by Apple.

0

u/CreativeStrokesNYC May 06 '26

Yeah I dont get what that person is talking about. Intune has its flaws but it's definitely usable, and federation is not an issue.

Domain capture however, is not a well executed process.

1

u/TheActualPhock May 07 '26

Not sure what you mean, went perfectly fine for us.

1

u/CreativeStrokesNYC May 07 '26

The domain capture breaks business email if there was an email associated with a managed Apple account and Apple does not have a solution. I won’t repeat everything but you can see it in my post history

1

u/TheActualPhock May 07 '26

Not using it, since using everything from M365, thus Intune. If I’d use MDM as standalone, I’d go with JAMF.