Zum Inhalt

Blogging about Microsoft 365, the Cloud & more ...

Always Cloud, Always Microsoft 365, ...

Exchange Online to Block Exchange Web Services (EWS) requests

Microsoft has sometime ago announced the retirement of Exchange Web Services (EWS) for Exchange Online.
Starting October 1, 2026, all EWS requests to Exchange Online will be blocked. Organizations using EWS for applications, integrations, or custom tools should begin transitioning to supported alternatives such as Microsoft Graph.

Exchange Server: No changes applied

Send E-Mails with PowerShell using Modern Auth. (OAuth)

You are currently using Send-MailMessage with Basic Auth. and want to transition to Modern Authentication?
May this PowerShell Module assists you, without having to rewriting your routine with Microsoft Graph directly.

  • Provides Send-MailMessage translation to Microsoft Graph
  • Supports SMTP with OAuth2 (Modern Auth, SASL XOAUTH2)

Send emails in PowerShell via Graph API, or SMTP (MailKit) with Modern Auth (OAuth) support.

Managed Conditional Access Policy

Microsoft Entra ID provides Managed Conditional Access Policies to help organizations enforce security best practices. These pre-configured policies simplify implementation while ensuring key protections like multifactor authentication (MFA) and blocking legacy authentication. They will be extended in February 2025 and after a 45 trial period automatically activated:

  • Block device code flow [NEW]
  • Block legacy authentication [NEW]

Exchange Server CU15: Ready for Action! (2025 H1 + WS2025)

The Cumulative Update 15 (CU15, 2025 H1) for Exchange Server 2019 is now available. This is the final CU for Exchange Server 2019 and brings several enhancements and fixes for known issues. CU15 also includes support for Windows Server 2025, allowing organizations to deploy Exchange Server 2019 on the latest server platform.

  • Ready for Action by IT-Admin to prepare sustainable for Exchange Server SE3 !

Exploring ExchangeOnlineManagement 3.7.0: Features and Changes

What's new in the Exchange Powershell Module, and what are the reasons?

ExchangeOnlineManagement 3.7.0 brings several updates and enhancements to the Exchange Online PowerShell module. This release introduces new features like extended message trace history, optional help file loading, and improvements to inbound IPv6 support. Additionally, Microsoft has updated the timeline for external recipient rate limits and introduced new cmdlets for managing these changes.

Transition to New Outlook (or Opt-out)

The New Outlook for Windows is here, delivering a seamless, productive, and familiar experience for commercial customers. This version integrates advanced productivity features and the latest innovations. Microsoft has planned a migration process (staged rollout) to ensure a predictable transition, with an opt-out option available for those not ready to switch. Early adopters can benefit from a 10–20% reduction in Outlook incidents, making this transition a win for reliability and efficiency.

Maester v1 (New Teams & Exchange Tests)

I am happy to refer to the release of Maester v1 1, a significant update that brings a bunch of new features and improvements. Since the release in March, the community has been working to build up the functionality and stability of Maester. This update includes a substantial increase in the number of tests, growing from 96 to 194, ensuring a wider usability.

Uninterrupted calls with Voice isolation (Teams)

Voice isolation, now available on both MacOS and Windows, uses AI to remove background noise, focusing primary on your voice for clear calls and meetings—wherever you are. This AI-powered enhancement focuses on your voice, ensuring only your speech is transmitted, even in busy or noisy environments.

Opt-in to Enable or Disable IPv6 in Exchange Online (without DANE)

Starting October 16, 2024, Microsoft will enable IPv6 for all customer Accepted Domains using Exchange Online. This upgrade offers improved security, scalability, and performance by utilizing IPv6.

Organizations need to update their network allow-lists (Firewall) to permit Exchange Online IPv6 endpoints and modify any IP-based inbound connectors referencing IPv4 (Connector, Rules). It is possible to stay with IPv4-only traffic, domains can be opted out over a PowerShell cmdlet. After October 16, if no preference is set, IPv6 will be enabled by default, potentially affecting inbound email traffic.