I’m a Microsoft 365 and Digital Workplace Architect with over 15 years of experience in IT, specialising in enterprise collaboration, SharePoint Online, governance, security and automation.
Throughout my career, I’ve worked with Microsoft technologies to design, manage, troubleshoot and improve collaboration environments. My experience spans traditional SharePoint platforms through to modern Microsoft 365 cloud services, with a focus on building secure, scalable and manageable solutions.
I enjoy solving complex technical problems, simplifying administrative processes and using automation to improve efficiency and consistency across enterprise environments.
My Areas of Expertise
Microsoft 365 Architecture & Governance
Designing and improving enterprise collaboration environments, with an emphasis on governance, security, operational efficiency and sustainable platform management.
SharePoint Online & OneDrive
SharePoint architecture, administration, migrations, site lifecycle management, storage optimisation, permissions, information architecture and governance. Experience working with large-scale SharePoint environments and developing solutions to improve their manageability.
PowerShell & Microsoft Graph Automation
Developing PowerShell scripts and automation solutions using Microsoft Graph, PnP PowerShell and SharePoint Online PowerShell to simplify administrative tasks, support governance and manage collaboration services at scale.
Microsoft Teams & Collaboration
Microsoft Teams administration, collaboration governance, telephony solutions and integration with Microsoft 365 services.
Security, Identity & Compliance
Working with Microsoft Entra ID, Microsoft Purview, eDiscovery, legal holds, data loss prevention and sensitivity labels to support secure collaboration and information protection.
Microsoft 365 Copilot & AI Governance
Exploring and evaluating Microsoft 365 Copilot capabilities, governance controls, policy configurations and their implications for enterprise collaboration and information security.
Power Platform
Practical experience with Power Automate workflows, SharePoint-integrated business process automation and Power Platform administration.
My Approach to Technology
I believe effective technology solutions should be practical, secure, maintainable and designed around real business requirements.
My approach combines hands-on technical investigation with architectural thinking. Whether troubleshooting a SharePoint issue, developing a PowerShell automation script or evaluating a Microsoft 365 capability, I aim to understand the underlying problem, consider the wider impact and implement a solution that can be supported over time.
I also believe in documenting what works, what doesn’t and why. Sometimes the lessons learned while investigating a problem are just as valuable as the eventual solution.
About This Blog
I started My IT Experiences to document technical challenges, solutions and lessons learned while working with Microsoft technologies.
The blog has evolved alongside my career, from earlier SharePoint and IT administration topics to Microsoft 365 architecture, governance, security and automation.
Here you’ll find:
- Practical troubleshooting guides based on real technical challenges.
- PowerShell scripts and automation examples.
- SharePoint and Microsoft 365 configuration guidance.
- Technical investigations, implementation notes and lessons learned.
- Insights into governance, security and enterprise collaboration.
Some older articles cover legacy technologies and are retained as historical technical references. Where appropriate, I’ll update articles to reflect changes in Microsoft platforms and recommended practices.
My aim is to share useful, experience-based technical knowledge that helps other IT professionals understand problems, evaluate solutions and work more effectively with Microsoft technologies.
The views and opinions expressed on this blog are my own and do not necessarily represent those of any current or former employer. Technical examples are provided for educational purposes and should be reviewed and tested in a suitable environment before being used in production.
Comments