Dear colleagues,

As previously communicated on July 8, 2025, Microsoft is retiring Basic authentication for Client Submission using Simple Mail Transfer Protocol Authentication (SMTP AUTH) in Exchange Online starting March 1, 2026. Microsoft will require modern authentication using OAuth. This retirement is part of Microsoft’s security improvements across all Microsoft 365 services. 

What is changing 

Basic authentication is a legacy authentication method that sends usernames and passwords in plain text over the network, making it vulnerable to credential theft, phishing and brute-force attacks. To improve the protection of users and institutional data, Microsoft is retiring Basic authentication for Client Submission (SMTP AUTH) and encouraging the use of modern, more secure authentication methods such as OAuth. 

After the retirement, connection attempts using Basic authentication will fail with the following error: 

550 5.7.30 Basic authentication is not supported for Client Submission. 

Who is affected
Any user, device or application that sends email through Exchange Online using Basic authentication with SMTP AUTH.
Microsoft has confirmed that Basic authentication activity was detected in our tenant between October 20 and October 24, 2025. Targeted emails will be sent to mailbox owners identified with Basic Auth activity.  

Action required 

• • If you manage applications, devices, or scripts that send email using SMTP AUTH, confirm whether they use Basic authentication. 

• • If the application supports OAuth, update the configuration to use OAuth. 

• • If the application does not support OAuth, you must transition to an alternative method of sending email, such as: 

• • Using Microsoft 365 High Volume Email for internal-tenant email. 

• • Using an on-premises Exchange relay if you operate in a hybrid configuration. 

• • Using a supported third-party solution if neither option is suitable. 

• • Please review the official Microsoft announcement for detailed recommendations and available resources related to this change.    

Timeline 

• • March 1, 2026 – Microsoft begins gradually rejecting a percentage of Basic authentication SMTP AUTH connections. 

• • April 30, 2026 – Microsoft completes retirement. All Basic authentication SMTP AUTH connections will be rejected. 

If you have any further questions or concerns, please submit a ticket to the Enterprise Service Centre at (https://uoft.me/m365help). 

Kind regards, 

Enterprise Applications & Solutions Integration (EASI)
Information Technology Services, University of Toronto
 

Microsoft has completed the rollout of several Teams collaboration and meeting enhancements. All features below are now broadly available across Microsoft Teams for the University of Toronto community.

1. Organizer Controls for in-meeting management (Now Available)

Microsoft Teams has introduced Organizer Controls, a consolidated fly-out menu in the meeting toolbar.
This update reorganizes existing meeting management tools to improve usability and security. 

Key capabilities 

• • Centralized access to: 

• • Lock Meeting 

• • Lobby bypass 

• • Participant moderation (mute, screen sharing restrictions) 

• • Replaces the previous “Meeting Options” entry point 

• • No admin configuration required 

2. Collaborative Notes in group chats (Now Available)

Collaborative Notes (powered by Microsoft Loop) are now available in group chats.
Users can co-create meeting notes, agendas, and action items directly in the chat interface without switching contexts. 

Key capabilities 

• • New Notes tab automatically available in group chats 

• • Real-time co-editing of Loop components 

3. Loop Pages in Teams channels (Now Available)

Teams channels now support Loop Pages as tabs, offering a flexible canvas for documentation, planning, and collaboration. 

Key capabilities 

• • Create, edit, and share Loop Pages directly within a Teams channel tab 

• • Mobile viewing supported 

• • Users receive activity notifications when mentioned 

• • Pages inherit channel permissions, but can be shared externally if allowed 

• • Useful for team documentation, project planning, and shared workspaces 

If you have any further questions or concerns, please submit a ticket to the Enterprise Service Centre at https://uoft.me/m365help.

Kind regards,

Enterprise Applications & Solutions Integration (EASI)
Information Technology Services, University of Toronto

As previously communicated, support for Microsoft Office 2016 and Microsoft Office 2019 ended on October 14, 2025. Looking ahead, support for Microsoft Office LTSC 2021 (Long-Term Servicing Channel) will end next year on
October 13, 2026.

What is changing 

• • Office LTSC 2021: Support ends October 13, 2026.  

• • Using unsupported software means: 

• • • No security updates → increased vulnerability to malware, phishing, exploits. 

• • • No bug fixes or compatibility assurances → potential disruptions in workflows. 

• • • Compliance risks (especially for regulated data) and integration problems with newer services. 

Action required 

• • Review inventory 

• • Plan upgrade: Schedule migration ahead of October 2026 to avoid falling into unsupported status. Options include: 

• • • Move to Microsoft 365 Apps (subscription-based) 

• • • Or upgrade to Office LTSC 2024 if you require a disconnected/one-time purchase model. 

Timeline 

• • October 13, 2026: Projected end of support for Office LTSC 2021.  

Resources 

• • Upgrade guidance and migration resources from Microsoft – Prepare for Office LTSC 2021 End of Support Next Year 

If you have any further questions or concerns, please submit a ticket to the Enterprise Service Centre at (https://uoft.me/m365help). 

Kind regards, 

Enterprise Applications & Solutions Integration (EASI)
Information Technology Services, University of Toronto