Microsoft has released details of an Exchange Online transport rule to encrypt outbound email containing sensitive data types like credit card numbers. The rule works (after fixing the PowerShell), but needs to be reviewed and possibly adjusted to meet the needs of Office 365 tenants.
A new report commissioned by Microsoft explains how Exchange Online and the Security and Compliance Center meet the electronic records requirements of regulatory bodies like the SEC and FINRA. Within the report, there’s some news about changes to the way that Office 365 handles Teams compliance records stored in Exchange Online. And after all that, we consider how some backup vendors treat Teams compliance records as equivalent to the data stored in the Teams Azure services.
The internet makes it easy to find material to read about technical topics. Unfortunately, a lot of content is rubbish. In this post, we compare two recent technical articles and explain why we think one marketing post is good and the other isn’t up to scratch.
The new version of OWA is maturing and new features are turning up on a weekly basis. You can now schedule a Teams meeting from OWA and the prospect of joyful animations hang in the air. But only for Office 365 users as there’s no sign that the new OWA will come to Exchange on-premises servers.
A change made to fix a problem in Exchange Online introduced another problem in that service domains started to show up as prefixes in the data returned by PowerShell cmdlets. Microsoft has reversed the change, but the way things happened creates some questions.