Free for higher ed IT · no email required
Will Your Identity Scripts Break?
The Microsoft Deadline Check for Higher Ed. 16 questions, about 5 minutes. Get your next break date and a plan.
The Microsoft Deadline Check
Your answers are scored in your browser and are never sent. QuickLaunch receives your email only if you ask for the report or join the waitlist.
The Microsoft Deadline Calendar
Microsoft published every one of these dates in advance. The gap is ownership, not the vendor.
- Already passed2025MSOnline (May 2025) and AzureAD (from mid-October 2025) PowerShell modules retired; cmdlets stopped working. Legacy Azure AD Graph API retired.Who it hits: Any script usingSource: Microsoft Learn: Azure AD PowerShell migration FAQ (MSOnline retired May 30, 2025)
Connect-MsolService,Get-MsolUser,Connect-AzureAD,Get-AzureADUser, or callinggraph.windows.net - ChangedSept 30, 2026Microsoft moved the Entra Connect Sync deadline from Sept 30, 2026 to April 7, 2027, and raised the minimum from 2.5.79.0 to 2.6.84.0 (Sept 29 on its security hardening page, Oct 1 on the hardening page). Sync did not stop on Sept 30.Who it hits: Every campus syncing on-prem AD to Entra with Connect Sync below 2.6.84.0Source: Microsoft Learn: Hardening updates for Microsoft Entra Connect Sync (changed Sept 30 and Oct 1, 2026)
- Live nowSept 30, 2026Microsoft's recommended date for Entra Connect Health agents 4.5.2466.0 or higher. Below that, a subset of alerts is impacted, including the alert that reports password hash sync has stoppedWho it hits: Same populationSource: Microsoft Learn: Entra Connect security updates
- Live nowFrom Oct 6, 2026Microsoft switches off the last Azure AD Graph access for old Azure CLI and Azure PowerShell releases over about two months; they may stop working at any pointWho it hits: Automation pinned to an old Azure CLI or Az PowerShell versionSource: Microsoft Azure Tools blog: Azure AD Graph API retirement, action required for older Azure CLI and Azure PowerShell (Oct 5, 2026)
- NextOct 23, 2026Entra Connect 2.5.79.0 retires (it met the old deadline, but it is below Microsoft's new 2.6.84.0 minimum)Who it hits: Campuses that upgraded to 2.5.79.0 for the old Sept 30 deadlineSource: Microsoft Learn: Entra Connect version release history
- RollingOngoingEvery Entra Connect 2.x version retires 12 months after a newer version ships (policy since March 15, 2023)Who it hits: Everyone on Connect SyncSource: Microsoft Learn: Entra Connect version release history
- NextEnd of Dec 2026SMTP AUTH Basic Authentication disabled by default for existing Exchange Online tenants (admins can re-enable for now)Who it hits: Scripts that email new-account notices viaSource: Microsoft Exchange Team blog: Updated SMTP AUTH Basic Authentication deprecation timeline (Jan 27, 2026)
smtp.office365.comwith a stored username and password - NextApr 7, 2027Entra Connect Sync must be on 2.6.84.0 or later with application-based authentication, or all synchronization fails until you upgrade. Upgrading alone doesn't switch an existing server; run the wizard.Who it hits: Every campus on Connect Sync, including those that stopped at 2.5.xSource: Microsoft Learn: Hardening updates for Microsoft Entra Connect Sync
- AnnouncedH2 2027Microsoft announces the final removal date for SMTP AUTH Basic AuthWho it hits: SameSource: Microsoft Exchange Team blog: Updated SMTP AUTH Basic Authentication deprecation timeline (Jan 27, 2026)
- StructuralStarted April 2026, no end dateMicrosoft's Entra Connect Sync to Entra Cloud Sync transition ("plan for change"). No retirement date for Connect Sync yet. Cloud Sync lacks some Connect features (e.g., advanced sync rules, groups over 50,000 members, device writeback).Who it hits: Campuses with custom sync rulesSource: Microsoft Learn: What's new in Microsoft Entra (April 2026)
Errors and deadlines: fix them now
- Entra Connect Sync must be on 2.6.84.0 by April 7, 2027
- 550 5.7.30 Basic authentication is not supported for Client Submission
- Send-MailMessage to smtp.office365.com stopped working
- Connect-MsolService and Get-MsolUser stopped working
- Connect-AzureAD and Get-AzureADUser stopped working
- Azure AD Graph (graph.windows.net) calls are failing
- Should your campus move from Entra Connect Sync to Cloud Sync?
Questions
Is this check really free and anonymous?
Yes. Your answers are scored in your browser and are never sent. QuickLaunch receives your email only if you ask for the report or join the waitlist.
Is QuickLaunch replacing Microsoft Entra?
No. We complete it. Most of our customers run Entra. We handle what campus scripts were doing: SIS-driven account creation, OU placement, groups and deprovisioning, governed and monitored.
Microsoft announced these dates years ago. Why are campuses still getting caught?
Deprecation notices go to people. Scripts don't read email. If the person who wrote a script has left, the notice reaches nobody.
Do we have to replace every script?
No. Migrate the load-bearing flows (provisioning, deprovisioning, directory sync). Keep small, well-understood scripts, with an owner, a vault and logging.
What should we do first?
Check your Entra Connect version today. Then search your scripts for Msol, AzureAD, graph.windows.net and smtp.office365.com.
