Decide which domain to federate 2. Connect to Azure to verify identity/ownership 3. View Apple ID conflicts on your domain 4. Resolve Apple ID conflicts on your domain 5. Notify end users of conflicts 6. Turn on and test federation
at Azure’s capabilities, we realized we could add ANY domain that we control to our Azure accounts, and (with a little bit of work) in the Microsoft console. Examples: lsc.k12.in.us apple.lsc.k12.in.us ipadatlsc.org
Our goal = single, securely-managed set of user creds for student-facing services. For better or worse, we chose federating our root domain (lsc.k12.in.us)
ANY truly does mean ANY! All personally created staff Apple IDs Old student Apple IDs Purchasing Apple IDs (ecommerce.apple.com) GSX Apple IDs (Service) Apple Developer Apple IDs Old Apple Configurator Apple IDs EVEN YOUR APNs CERT FOR MDM!
with your staff before you get “Why did I get this email?” work tickets! Outline future benefits (Schoolwork, backup, single set of credentials, etc…) Instruct users where they can get help resolving conflicting Apple IDs.
After 30 days, Apple nudges conflicted accounts by deactivating FaceTime and iMessage. After 60 days, Apple resolves conflicts by migrating them to temporary Apple IDs. For example: [email protected] becomes [email protected]
everyone thinking, “I’m not moving our mission critical Apple IDs to a Gmail account.” Use a second un-federated domain your organization controls for these Apple IDs.
upload to Apple School Manager https://support.apple.com/en-us/HT207029 Connect your SIS to Apple School Manager https://support.apple.com/en-us/HT207409
updating a previous ASM integration, consider how changing a users email address may impact Jamf smart groups. Duplicate matching criteria: Managed Apple ID = Email (Jamf Pro)
Federated Authentication https://apple.co/2ILVH8Q Intro to federated authentication with ASM https://apple.co/2J1Miu3 Apple School Manager User Guide https://apple.co/329qqmZ