Microsoft 365 should work for you, not against you.
UnsuckM365 exists because too much Microsoft 365 guidance is written for perfect demo environments. Real tenants are messier. Permissions are inherited from decisions nobody remembers, sites multiply, governance gets written after the fact, and the people responsible for fixing it are usually doing five other jobs at the same time.
I have been working in this stack since 2009, from WSS and MOSS through SharePoint Online, Teams, Power Platform, and now Copilot. Today I work as a Microsoft 365 Solutions Architect, and I am a 2x Microsoft MVP for SharePoint and Microsoft 365 Copilot, a Microsoft Global Community Initiative Regional Leader, speaker, organizer, and community contributor. That gives me a front-row seat to both the technology and the very human ways organizations struggle with it.
What this site is for
I am not here to rewrite Microsoft Learn. The documentation already exists, and much of it is good. What I want to add is the part that usually gets left out: the tradeoffs nobody puts in the slide deck, the architectural decisions that look smart on paper but hurt in production, and the patterns that actually hold up when real users show up.
You will find practical guidance here on SharePoint, Microsoft 365 governance, Power Platform, Copilot, modernization, adoption, and the occasional problem that should have been simple but somehow became a three-week investigation. Some posts are quick fixes. Others are about the bigger decisions that determine whether a tenant stays manageable or slowly turns into chaos.
And yes, there is a lot of AI right now. Every feature is revolutionary, every demo is flawless, and every roadmap slide promises transformation. Meanwhile, plenty of organizations still have broken permissions, five versions of the same site, stale content everywhere, and a governance model living in somebody’s head. AI does not make those problems disappear. It usually makes them more visible.
The humans behind the tenant
The people I care most about are the admins, architects, developers, consultants, community members, and accidental SharePoint owners trying to do good work without unlimited budgets, giant teams, or a direct line to Microsoft. A lot of the best people in this ecosystem are solving hard problems quietly, often without the title, visibility, or confidence that matches what they actually know.
I want UnsuckM365 to help those people do more than fix technology. I want it to help them explain why something matters, challenge bad decisions, share what they have learned, submit the conference talk, ask the question everyone else is afraid to ask, and find their own voice in a community that is better when more people participate in it.
That is also why community, speaking, organizing, and mentorship matter so much to me. Knowledge should not only flow from vendors, large consultancies, or the loudest person in the room. Some of the most useful lessons come from the person who spent Tuesday night figuring out why the migration broke and decided to tell everyone else what happened.
More than the blog
If you want to know more about my professional background, community work, or the kind of Microsoft 365 work I do, the Experience page has the longer version. If you are looking for some guidance of your own, I also make time for informal mentorship when I can. For help with your organization’s Microsoft 365 environment, see Consulting.
If something here helps you fix a tenant, make a better decision, explain the tradeoff, speak up in a room where your experience matters, or help somebody else do the same, then this site is doing what I want it to do. Let’s keep the conversation going.
Diego