Microsoft announced that Exchange Online will block devices using Exchange ActiveSync protocol versions earlier than 16.1 from connecting to its services starting March 1, 2026. This change affects organizations using mobile devices with native email applications to access Exchange Online mailboxes and aims to strengthen security and reliability across the platform. Clients using basic authentication for an affected protocol will be unable to connect to Exchange Online and will receive an HTTP 401 error stating "bad username or password."

Source

Le client de messagerie Thunderbird 145 intègre le support natif d'Exchange Web Services, ce qui le rend compatible avec Exchange on-premise et Microsoft 365.

The post Thunderbird 145 ajoute le support natif des comptes Exchange, y compris via Microsoft 365 first appeared on IT-Connect.

Microsoft is rolling out Auto-Archiving for Exchange Online for public clouds and government clouds. This new threshold-based archiving feature automatically moves the oldest items from a user's primary mailbox to their archive mailbox when mailbox utilization exceeds 90% of the quota, complementing existing time-based archiving policies to prevent disruptions to mail flow.

Source

Un nouveau guide publié par la NSA et la CISA regroupe une dizaine de recommandations à appliquer sur Exchange Server pour améliorer la sécurité.

The post Les conseils de la NSA et de la CISA pour sécuriser un serveur Microsoft Exchange first appeared on IT-Connect.

Active Directory domain controllers running Windows Server 2025 with the schema master FSMO role may create duplicate schema attribute values when performing Exchange Server schema extensions, causing replication failures across the entire forest. This issue triggers this error message: Error 8418: The replication operation failed because of a schema mismatch between the servers involved. The issue affects environments attempting to deploy Exchange Server cumulative updates or Exchange Server Subscription Edition. Microsoft has acknowledged this as a known issue in KB5065426.

Source