Office 365 offers different ways to apply encryption to important messages. When those messages hold sensitive data known to Office 365, like credit cards or passport numbers, we can define a transport rule or DLP policy to protect outbound email automatically. And while you can define rules and policies through the GUI, PowerShell is available too.
If you run a hybrid Exchange deployment, you probably have some on-premises distribution lists that you’d like to move to the cloud. Office 365 offers no way to do this, so it’s up to PowerShell. Instead of starting from scratch, you can use a script created by Tim McMichael of Microsoft and amend it to meet your needs. PowerShell is just great.
Tony spoke about “Can Teams Replace Email” at the Modern Workplace Conference in Paris on October 17. Here’s a sketch note about what he said and a copy of the slides.
Microsoft issued Message Center update MC151582 to tell Exchange Online administrators about a new default value for automatic processing of events sent to room mailboxes. Unfortunately, the PowerShell code in the update contains an error, so here’s some fixed code to check existing values and to set them to the new default, if you want to do that.
Microsoft has confirmed that they will not release a free hybrid license for Exchange 2019. That’s OK, because if you want to use Exchange 2019 as the HCW host, you simply assign the server one of your licenses. After all, the server won’t simply be running hybrid connectivity, will it?
Microsoft has a new OWA user interface in targeted release. So far it all looks good even if some features are still missing, Expect to see the new UI generally available in late 2018 or early 2019.
Exchange 2019 has a recommended minimum of 128 GB of memory. Just what does that recommendation mean?
Exchange Online sends its mailbox audit records to the Office 365 audit log. You can search the log to discover who deleted messages from mailboxes, normally only an issue when delegates are involved.
Search-Mailbox is a very useful cmdlet but running the cmdlet can be very dangerous as you might end up permanently removing some data that you’d prefer to keep. And in the cloud, there’s no backups…
A new Exchange feature rolling out inside Office 365 allows meeting organizers to block people forwarding their meetings to all and sundry. The latest versions of OWA and Outlook 2016 click to run support the UI for the feature and blocks are built into Exchange Online and Exchange on-premises servers to stop blocked meetings sneaking through.
Have you ever tried to use SSDs with Exchange Server only to be told that it’s a really bad idea and that you should concentrate on JBOD. Well, Microsoft has made some changes in Exchange 2019 and will talk about them at Ignite, and you can learn about it on Wednesday, Sept 26 in-person, online, or afterwards.
Hanging on to old email habits is a bad idea, especially if you use a cloud service like Office 365 where Microsoft introduces a steady stream of new features. The worst bad habit is password sharing. It’s time to stop this now.
Microsoft has published some statements about not allowing older Office clients to connect to Office 365 from October 2020. Well, the word “allow” should really be read as “support.” Or so we hear.
Microsoft thoughtfully provided Office 365 tenants with a Data Loss Prevention template for GDPR personal data. The only problem is that the rules in the template were too sensitive and started to block email.
Teams won’t take over from email anytime soon, but it is much better at organizing face-paced conversations.
A recent post by MVP Mark Vale describes how to use synchronization transformation rules in AADConnect to change the last name, first name format (for example, Smith, James) for display names to a more user-friendly first name last name format (our example becomes James Smith) for accounts as they synchronize to Azure Active Directory from an …