To run scripts and cmdlets in Exchange Online, you need to connect to your organization with PowerShell. If you’re still using New-PSSession
or a legacy ExchangeOnlineManagement module, you need to update your methods, and do it quick. I’ll show you how to update Exchange Online PowerShell module to EXO V3 module, why the change is needed and how much time you have left.
Author: Adam the 32-bit Aardvark
How to check Windows event logs with PowerShell (Get-EventLog)
[Update]: This article was first published on May July 25, 2018. It’s been updated and extended with more details.
Windows event logs is one of the first places an admin looks at when they analyze problems and search for their causes. But troubleshooting is not the only reason for logged events. In this article, I will show you how to use PowerShell and Get-EventLog to perform some Event Log magic. But first, a few words about the logs in general.
Move email hosting to Office 365 with IMAP migration
An increasing number of companies decide to move from their email hosting to Office 365. Mailbox migration is a complex and quite stressful project, but with the following guide you will see how to perform such migration via IMAP without great anxiety.
How to set up different email signatures for a shared mailbox and user mailbox in Office 365?
[Update]: This blog post was first published on August 7, 2018. It’s been updated to reflect the current steps required for a proper email signature setup in Exchange Online.
There are three options to choose from to add different signatures to user mailbox and shared mailbox emails. The first method is to create two separate signatures in Outlook, the second requires mail flow rules on the server side and the third involves the use of CodeTwo Email Signatures for Office 365 – an email signature management solution.
How to prevent Office 365 users from sending emails outside the organization?
[Update]: This article was first published on September 4, 2019. It’s been updated to present the current steps required for a proper configuration in the Exchange admin center.
There might be situations when it’s necessary to block the mail flow outside an organization for specific users or user groups. Let’s find out how you can use Exchange Online mail flow rules to prevent Office 365 users from sending emails to external recipients.
How to create a no-reply mailbox in Microsoft 365
[Update]: This article was first published on February 19, 2021. It’s been updated to present the current steps required for a proper configuration in Microsoft 365.
No-reply email addresses are useful in many scenarios, like sending notifications from transaction systems, shipping progress information, etc. In the case of such messages, you do not expect any user feedback and most of them are generated and sent automatically.
Even though you cannot stop users from sending emails to a no-reply address, you can create a mailbox which will block all incoming traffic, meaning you will not have to monitor it.
How to turn off suggested replies in Outlook
Outlook offers a feature that automatically suggests replies to emails. This can be a great time-saver when you need to quickly respond to yes-or-no type of questions. However, as for all new features, this one has its fans and those who could definitively live without it. If you feel like a member of the second group, here you will find the instructions on how to turn off suggested replies in Outlook across different platforms.
All you need to know about a catch all email in Exchange Online
Emails sent to non-existing business mailboxes, for example because of a typo, can be a real pain both for senders and businesses, preventing communication from taking place. Fortunately, you can equip your organization with a kind of ‘safety net’ for the emails ‘lost in the space’: a catch all mailbox. I will explain what is the true meaning of the catch all mailbox and how to set it up in Microsoft 365 (or Exchange Online to be exact).
How to migrate from Exchange 2013 to Office 365 (Microsoft 365) and why do it now?
Server migration is a very stressful task. It involves moving business-critical data between different locations. Since Exchange 2013 is nearly at the end of its road, the number of companies which are looking into migration away from it increases. While there is more than one possible target server to migrate to, Exchange 2013 to Office 365 migration seems to be one of the most popular scenarios. In this article, I’ll show you what the available methods are to migrate from Exchange 2013 and how to perform them.