The mission of Practical 365 is to provide relevant, actionable advice on all things Microsoft, straight from the experts themselves including Office 365, Exchange, PowerShell, Azure, SharePoint, and more. We aim to make our news, tips and tutorials simple and applicable, helping our global community of IT professionals to optimize their Microsoft experience.
Our Team
Practical 365 is a community effort! With Microsoft MVPs like Tony Redmond, Steve Goodman and Paul Robichaux at the helm and from contributions by MVPs and other industry experts like Thijs Lecomte, Damian Scoles, Sean McAvinue, and more.
Tony Redmond runs his own consulting company and is the lead author for the Office 365 for IT Pros eBook
(office365itpros.com). He also writes a twice-weekly column covering all things Office 365 on Petri.com.
Tony is a frequent speaker at conferences and blends a mixture of executive and technology insight about
the topics he
covers.
Paul Robichaux, an Office Apps and Services MVP since 2002, leads product development for the Microsoft Platform Management group at Quest, the world leader in Office 365 migration, automation, reporting, and security products.
Paul’s unique background includes stints writing Space Shuttle payload software in FORTRAN, developing cryptographic software for the US National Security Agency, helping giant companies deploy Office 365 to their worldwide users, and writing about and presenting on Microsoft’s software and server products.
Paul’s an enthusiastic (but slow) triathlete, an instrument-rated private pilot, and an occasional blogger (at http://www.paulrobichaux.com) and Twitter (@paulrobichaux)
Connect with us
If you’re an industry expert and would like to contribute insightful content to the community, please complete our contact form and tell us your thoughts.
This article explains how to create a mailbox contents report using PowerShell and the Microsoft Graph. The list of mailbox items is exported to a workbook.
Two Exchange Day-Zero Vulnerabilities have been revealed. The Microsoft Security Resource Center has published mitigations, but the issue raises questions once again about the wisdom of running on-premises Exchange Server unless you really must.
