M365

This post describes a technique to set Office365 Sensitivity Label on mails in transit using mail flow rules.

Was your M365 tenant configured securely when it was deployed? Is it still configured securely now? Update on state of SaaS security posture management (SSPM) post from 2022. This time looking at community projects too.

Face recognition on Apple iPhones has long been a trusted and secure way to sign-in to business apps on corporate phones. With the right camera hardware, it’s been available in Windows too for quite a while. This post describes deploying Windows Hello for Business (WHfB) in a Hybrid AD Joined environment.

Was your SaaS software configured securely when it was deployed? Is it still configured securely now?
This article discusses the risk to your data of misconfigured/unhardened SaaS software and the emerging products to automate security checking of SaaS.

“M365 landscape by By Aaron Dinnage”)

From the excellent feature licensing chart by Aaron Dinnage, you can see the Microsoft 365 suite has so many productivity and security components. It’s difficult to know where to start. I’d like to suggest a roadmap for implementing M365 features and getting value out of M365 licensing. The roadmap would be based on dependencies (you need X before you can deploy Y) and it should be prioritised on business value. I also wanted to experiment with the MermaidJS library for creating dependency diagrams.

Exchange Online migration is a complicated project in a large organisation. So complicated that some organisations haven’t completed this yet. There’s many technical integrations and operational processes with this service. Here’s a post about technical and operational problems that can occur when migrating email to Exchange Online. What has tripped you up in an Exchange migration? Let me know what I’ve missed!

Very niche post today. Few will need to delve into Office 365 Compliance Boundaries unless they need to unblock some regulatory compliance requirement. If your in that situation hopefully this will help you. The scenario is this: you have multiple eDiscovery teams in your organisation. Each eDiscovery team should only see content belonging to users in their own sphere of responsibility. Example requirement: eDiscovery team ACME should only be able to see content for company ACME

WinOps conference videos have been released: Videos: https://www.youtube.com/channel/UCP1OgsLk-HkEdQyhjJX_5JQ Slides: http://www.slideshare.net/WinOpsConf Future Meetups: http://www.meetup.com/WinOps/ Watch the keynote for a “state of the industry” regarding DevOps on Windows. Keynote part 1 https://www.youtube.com/watch?v=wlJo4BLtXyI Keynote part 2 https://www.youtube.com/watch?v=WQZYS5gu6CQ