Outbound email: Migration to modern Microsoft 365 authentication (OAuth)

February 26
Enhancement
VSA 10, Kaseya 365 Endpoint

This release replaces legacy username/password SMTP authentication with Microsoft’s OAuth authorization code flow when integrating outbound email with Microsoft 365. The new method eliminates the need to store user credentials and aligns with Microsoft’s planned deprecation of basic authentication, improving security and long-term compatibility.

When configuring outbound email using OAuth, administrators only need to provide the Application ID, Directory ID and Client Secret. Existing configurations using the legacy method will continue to function temporarily, but administrators will see a persistent banner prompting them to migrate. The banner will also notify admins if an issue occurs when refreshing the SMTP OAuth access token.

Important: Migration should be completed before Microsoft begins deprecating basic authentication — currently expected to start December 31, 2026 — to ensure uninterrupted outbound email functionality.

Learn more about OAuth for outbound email in VSA 10 here.

One complete platform for IT & security management

Kaseya 365 is the all-in-one solution for managing, securing, and automating IT. With seamless integrations across critical IT functions, it simplifies operations, strengthens security, and boosts efficiency.

SIEM Integration: Types, Benefits and Best Practices

SIEM integration connects your security tools to a central system for unified threat detection. Learn how it works and best practices for getting it right.

Read blog post

Cloud SIEM: A guide to features, advantages and deployment models

The way organizations manage security has changed permanently. Infrastructure that used to sit behind a firewall now spans cloud platforms,

Read blog post

AI SIEM: How AI is transforming threat detection and security operations

Security teams have always faced an information problem. The data needed to catch threats exists somewhere within the environment, but

Read blog post