BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//KBY Technologies//Admin Deadlines//EN
CALSCALE:GREGORIAN
METHOD:PUBLISH
X-WR-CALNAME:KBY admin deadlines (macOS)
X-WR-CALDESC:Microsoft and Apple retirements\, deprecations\, enforcement d
 ates and end-of-support dates for endpoint and identity admins. Each date 
 is quoted from the vendor's own page.
X-WR-TIMEZONE:UTC
REFRESH-INTERVAL;VALUE=DURATION:P1D
X-PUBLISHED-TTL:P1D
URL;VALUE=URI:https://www.kbytechnologies.com/deadlines
BEGIN:VEVENT
UID:intune-macos-15-minimum@kbytechnologies.com
DTSTAMP:20261109T000000Z
LAST-MODIFIED:20261109T000000Z
DTSTART;VALUE=DATE:20261001
DTEND;VALUE=DATE:20261002
SUMMARY:Intune moves to macOS 15 and later (Q4 2026)
DESCRIPTION:Date: Q4 2026. The vendor has not published an exact day\, so t
 his event sits on the first day of that quarter.\n\nMicrosoft · End of su
 pport\n\nWho is affected: Organisations enrolling Macs with Intune. New Ma
 cs on macOS 14 or earlier will not be able to enrol\; Macs already enrolle
 d stay enrolled but are no longer supported.\n\nWhat to do:\n1. Filter Dev
 ices > All devices by macOS and add the OS version column to find Macs on 
 macOS 14.x or earlier.\n2. Upgrade those Macs to macOS 15 or later\, or re
 place hardware that cannot run it.\n3. Upgrade spare and new-stock Macs be
 fore they are handed out\, so enrolment does not fail.\n\nSources:\n- In d
 evelopment for Microsoft Intune (Microsoft Learn): https://learn.microsoft
 .com/en-us/intune/intune-service/fundamentals/in-development\n  "Later in 
 calendar year 2026\, we expect macOS Golden Gate 27 to be released by Appl
 e. Microsoft Intune\, the Company Portal app\, and the Intune mobile devic
 e management agent support macOS 15 and later."\n- In development for Micr
 osoft Intune (Microsoft Learn): https://learn.microsoft.com/en-us/intune/i
 ntune-service/fundamentals/in-development\n  "Microsoft Intune will update
  its minimum supported macOS version after Apple releases macOS 27. Intune
 \, the Company Portal\, and the Intune management agent will support macOS
  15 and later."\n\nChecked 2026-11-09. Dates move\; check the source befor
 e you act.\nhttps://www.kbytechnologies.com/deadlines/intune-macos-15-mini
 mum
URL;VALUE=URI:https://www.kbytechnologies.com/deadlines/intune-macos-15-min
 imum
CATEGORIES:Microsoft,End of support
TRANSP:TRANSPARENT
STATUS:CONFIRMED
END:VEVENT
BEGIN:VEVENT
UID:intune-ade-setup-assistant-legacy-ended@kbytechnologies.com
DTSTAMP:20261109T000000Z
LAST-MODIFIED:20261109T000000Z
DTSTART;VALUE=DATE:20261026
DTEND;VALUE=DATE:20261027
SUMMARY:Intune ends Setup Assistant (legacy) authentication for Apple autom
 ated device enrollment
DESCRIPTION:Microsoft · Retirement\n\nWho is affected: Organisations using
  Apple automated device enrollment (ADE) profiles with user affinity that 
 still authenticated with Setup Assistant (legacy). Existing profiles move 
 to modern authentication\; enrolled devices stay enrolled.\n\nWhat to do:\
 n1. Open each ADE profile with user affinity and confirm it now shows Setu
 p Assistant with modern authentication.\n2. Enrol one test iPhone and one 
 test Mac to check MFA and Conditional Access prompts during Setup Assistan
 t.\n3. Update enrolment guides and helpdesk scripts that describe the old 
 sign-in screens.\n\nSources:\n- What's new in Microsoft Intune (Microsoft 
 Learn): https://learn.microsoft.com/en-us/intune/intune-service/fundamenta
 ls/whats-new\n  "Intune has ended support for Setup Assistant (legacy) aut
 hentication for iOS/iPadOS and macOS automated device enrollment (ADE) wit
 h user affinity to align with modern authentication standards."\n\nChecked
  2026-11-09. Dates move\; check the source before you act.\nhttps://www.kb
 ytechnologies.com/deadlines/intune-ade-setup-assistant-legacy-ended
URL;VALUE=URI:https://www.kbytechnologies.com/deadlines/intune-ade-setup-as
 sistant-legacy-ended
CATEGORIES:Microsoft,Retirement
TRANSP:TRANSPARENT
STATUS:CONFIRMED
END:VEVENT
BEGIN:VEVENT
UID:intune-legacy-apple-software-update-removed@kbytechnologies.com
DTSTAMP:20261109T000000Z
LAST-MODIFIED:20261109T000000Z
DTSTART;VALUE=DATE:20261026
DTEND;VALUE=DATE:20261027
SUMMARY:Intune removes legacy Apple MDM software update policies
DESCRIPTION:Microsoft · Retirement\n\nWho is affected: Intune admins who s
 till manage iOS/iPadOS or macOS updates with legacy MDM software update po
 licies or the update-delay restriction settings. Apple removed the underly
 ing commands and payloads in OS 27.\n\nWhat to do:\n1. Recreate update rul
 es as declarative device management (DDM) software update policies in the 
 settings catalog.\n2. Check that every Apple device group is covered by a 
 DDM update policy before deleting the old policies.\n3. Re-check deferral 
 settings: the legacy restriction keys for delaying updates were removed in
  OS 27.\n\nSources:\n- What's new in Microsoft Intune (Microsoft Learn): h
 ttps://learn.microsoft.com/en-us/intune/intune-service/fundamentals/whats-
 new\n  "Microsoft Intune is removing legacy Apple MDM software update work
 loads after Apple retired the underlying commands and payloads in OS 27. A
 dmins should use Apple declarative device management update policies to co
 ntinue managing software updates."\n- apple/device-management CHANGES.md (
 Apple\, GitHub): https://raw.githubusercontent.com/apple/device-management
 /release/CHANGES.md\n  "Removed: mdm/commands/system.update.schedule.yaml"
 \n\nChecked 2026-11-09. Dates move\; check the source before you act.\nhtt
 ps://www.kbytechnologies.com/deadlines/intune-legacy-apple-software-update
 -removed
URL;VALUE=URI:https://www.kbytechnologies.com/deadlines/intune-legacy-apple
 -software-update-removed
CATEGORIES:Microsoft,Retirement
TRANSP:TRANSPARENT
STATUS:CONFIRMED
END:VEVENT
BEGIN:VEVENT
UID:apple-developer-id-sub-ca-expiry@kbytechnologies.com
DTSTAMP:20261109T000000Z
LAST-MODIFIED:20261109T000000Z
DTSTART;VALUE=DATE:20270201
DTEND;VALUE=DATE:20270202
SUMMARY:Original Apple Developer ID Sub-CA expires: affected .pkg installer
 s stop installing
DESCRIPTION:Apple · Retirement\n\nWho is affected: Mac admins who deploy i
 nstaller packages signed with a Developer ID certificate issued by the ori
 ginal Sub-CA\, including in-house packages and older third-party packages 
 in Intune\, Jamf or other MDM. Notarised apps with a secure timestamp keep
  working.\n\nWhat to do:\n1. Run pkgutil --check-signature on every .pkg y
 ou deploy and note which ones chain to the original Developer ID Certifica
 tion Authority.\n2. Re-sign in-house packages with a certificate from Deve
 loper ID Certification Authority (G2) and re-upload them.\n3. Ask vendors 
 for re-signed packages and replace cached copies in your MDM before Februa
 ry 1\, 2027.\n\nSources:\n- Upcoming expiration of Developer ID Certificat
 ion Authority (Sub-CA) (Apple Developer News): https://developer.apple.com
 /news/?id=w4atic4c\n  "The original Developer ID Certification Authority (
 Sub-CA) expires on February 1\, 2027. Certificates issued by this authorit
 y will stop working on that date."\n- Upcoming expiration of Developer ID 
 Certification Authority (Sub-CA) (Apple Developer News): https://developer
 .apple.com/news/?id=w4atic4c\n  "Installer packages (.pkg): Starting Febru
 ary 1\, 2027\, .pkg files signed with an affected certificate will no long
 er install."\n\nChecked 2026-11-09. Dates move\; check the source before y
 ou act.\nhttps://www.kbytechnologies.com/deadlines/apple-developer-id-sub-
 ca-expiry
URL;VALUE=URI:https://www.kbytechnologies.com/deadlines/apple-developer-id-
 sub-ca-expiry
CATEGORIES:Apple,Retirement
TRANSP:TRANSPARENT
STATUS:CONFIRMED
END:VEVENT
END:VCALENDAR