Three years ago, we described how to create organizational contacts in user mailboxes with Graph API requests. In this iteration, we read the contacts from a Microsoft list and use Microsoft Graph PowerShell SDK cmdlets to update user mailboxes. The techniques explained in the article can be used in many scenarios.
Microsoft plans a transition of the current Exchange Server licensing and support model to Exchange Server subscription edition (SE) starting in 2025. Organizations must prepare for the transition by upgrading servers to the latest cumulative updates of Exchange 2016 and Exchange 2019. The transition is unlikely to be seamless, but glitches can be avoided by good planning and careful monitoring of community discussions.
Microsoft Lists are a powerful tool for end users to store and manage data stored in SharePoint Online sites. The Microsoft Graph PowerShell SDK includes cmdlets to work with Microsoft Lists and this article explains how to use the cmdlets to add new lists, add items to lists, retrieve data from lists, and remove items from lists.
Dynamic watermarking is a new feature for sensitivity labels that's intended to provide a visual deterrent to screen captures of confidential documents. The feature works by using the email address of the signed-in user as a watermark. Everything works and the feature seems effective, but this isn't something to use with every sensitivity label.
Microsoft released the initial implementation of a cloud-based message recall feature last year. Now they're back with a set of enhancements to take the rough edges off, like explaining to users why messages disappear from the inbox and enabling support for external services like email hygiene and mail autosignature providers.
Sometimes sensitivity labels defined for use within a Microsoft 365 tenant turn out to be unnecessary. The question then is what to do with these unwanted sensitivity labels. The answer is to pause for thought, gather information, and then make an informed decision, all of which we discuss here.
Exchange Online mail folders and messages are a very important resource for Microsoft 365 tenants. This article discusses how to use cmdlets from the Microsoft Graph PowerShell SDK to retrieve information about mailbox folders and mail messages together with some performance tips for dealing with folders that store thousands of messages.
Market analysts question if companies like Microsoft will ever generate a return on their AI investment. That hasn't stopped Microsoft spending $19 billion in FY24 Q4, so they must be hopeful. Meanwhile, at Black Hat USA 2024, a presentation exploring some vulnerabilities in Copilot should make all Microsoft 365 tenants with Copilot consider how to secure their organization better.
If you're looking for an email service capable of handling large volumes of email to external recipients, Microsoft will propose Email Communication Services (ECS). Built on top of Exchange Online, ECS shares some characteristics with the High Volume Email (HVE) solution. After testing both, HVE is probably a better solution if you have a Microsoft 365 tenant.
The new Outlook for Windows client is generally available, which means that Microsoft supports it for product usage. That's all fine for those who want to use the new client once they understand that a considerable functionality gap still exists between the new Outlook and Outlook classic. Fortunately, Microsoft will support Outlook classic until "at least 2029."
The Exchange Online High-Volume Email (HVE) solution handles up to 100,000 internal messages and 2,000 external messages daily. It's intended to replace on-premises Exchange servers that organizations keep just to service email submission from devices and applications. In this review of the preview version, we discovered that almost everything works just fine, if you keep within the throttling limits.
Entra ID classifications don't seem very exciting because they're text-only visual markers for Microsoft 365 groups and teams that don't come with any of the intelligence built into sensitivity labels. However, classifications can do a useful job for Microsoft 365 tenants that don't have the necessary licenses for sensitivity labels or who don't want to implement sensitivity labels.
