Exchange Online

As you know Exchange Online has some limits in place to ensure performance and stability of the service (see https://docs.microsoft.com/en-us/office365/servicedescriptions/exchange-online-service-description/exchange-online-limits to know more about). As part of these limits, there is one restricting the number of emails received per hour – set to 3600 emails (see https://docs.microsoft.com/en-us/office365/servicedescriptions/exchange-online-service-description/exchange-online-limits#receiving-and-sending-limits). Starting April 2021 this limit will be enforce.

Microsoft has identified that one of the Reply-URL used by Exchange Online for authentication and authorization is unsafe. As result, the Reply-URL list is going to be updated by end of March 2021. The Reply-URL being removed from the list is ietf:wg:oauth:2.0:oob. This will impact Exchange Online PowerShell modules earlier than 1.0.1, automation with ModernAuth

As you know, Exchange Online can be managed by either PowerShell or the Exchange Administration Portal (Exchange ECP). Few months ago, Microsoft has introduced an incoming new administration portal (see https://t.co/6KFYzwcqQU). Well, you can now use this new portal by default (you can still access the ‘old’ portal for settings not yet available). I recommend

As you know, there has been an option for Exchange administrator but also for end user to automatically forward incoming email to another email address – either internal or external – for a very long time. As end user can automatically forward incoming email either by setting a server-side rule or using the option available