In my first part of Exchange Online Automation with EXOv2 module, I covered how you can use Dave’s PowerShell module for cutting down the Azure AD application registration and configuration. Also, how and why you should store your secrets in Azure Key Vault.
M365 - Exchange Online Center
ENow Software's Microsoft Exchange Online blog built by Microsoft MVPs for IT/Sys Admins.
How can EXO recipient management be done without the need of administrative accounts? This question has been asked for a long time.Microsoft Graph does not cover the entire recipient management in Exchange Online and Microsoft customers have been asking for a solution for a long time. Now as Microsoft turns off Basic authentication, it looks like there is some movement.
Microsoft postponed deprecation of Basic Authentication in Exchange Online for existing tenants. Jaap Wesselius (MVP) wrote about this topic already here and explained what Modern Authentication means and how you can monitor existing usage of legacy auth (which Basic authentication basically is).
When it comes to collaboration, Outlook is still the most in common tool. It’s not only an e-mail client, it allows you also managing your appointments, tasks etc.
Especially the manager-delegate scenario, Outlook is THE tool to be used. But even we have great features, supporting our daily work and many scenarios, there are always limits. And these limits can cause a lot of trouble.
In my previous blogpost, I wrote about how crucial it is to have all of your domains registered, Access Control Entries (ACE) on mailbox and folder level in a row and a reminder to keep things simple and you might revisit your architecture and the need of resource forests.
There are several ways outlined by Microsoft that can be found here. This blogpost goes over migrating from an integrated Exchange server infrastructure to Exchange Online with a hybrid deployment. I will not cover third-party migrations, as this is not relevant for the topics mentioned in this post.