cube maia

Microsoft has identified that one of the Reply-URL used by Exchange Online for authentication and authorization is unsafe.

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 you know, Exchange Online can be managed by either PowerShell or the Exchange Administration Portal (Exchange ECP).

This has been a very awaited feature: getting your Outlook signature roaming across your devices. In fact it has been waited since the first release of Exchange server.

If you have been using a Gmail account, you may be already aware about the ‘plus address’ (or ‘plus addressing’) which allows you to dynamically create a unique email address, in addition of the ‘fixed’ ones.

As you know, Exchange Online Protection (EOP) plays an important role in your mail hygiene posture by blocking unsolicited or phishing emails and malware.

By know, you should already know the Remote Connectivity Analyzer tool (https://testconnectivity.microsoft.com/) used to help investigating connectivity issue to Exchange (on-premises or online), Skype for Business/Lync, mail flow….

If you are using Exchange Online and have enabled journaling, you will be able to exclude voicemail and missed call notification from being journaled.

If you work with Exchange and Exchange Online in hybrid mode, you already know that when a mailbox is moved to Exchange Online, the on-premises Exchange redirect/notify the user to access Exchange Online Outlook Web Access URL when using the ‘old’/on-premises OWA URL.

As you know Microsoft has been recommending to turn off basic authentication protocols for some time now.