Your Microsoft 365 environment probably doesn’t need more stuff. It needs someone to figure out what you already have, what’s broken, what’s being ignored, and what actually needs to change.
I’m Diego, an independent Microsoft 365 architect and advisor. You work directly with me to assess your environment, make sound technical decisions, and deliver focused improvements.
Where I can help
Your environment has grown without a plan
Sites, Teams, and Microsoft 365 Groups have accumulated, ownership is unclear, and nobody knows what is still being used. I assess the architecture, health, configuration, and dependencies, then help decide what to keep, fix, consolidate, or retire.
People cannot find what they need
I organize SharePoint sites, libraries, navigation, metadata, and permissions around how people work. That includes information architecture, intranet modernization, and deciding how Teams and SharePoint fit together, so people know where work belongs.
Governance lives in someone’s head
I help define who can create resources, who owns them, how access and sharing work, and when content or workspaces should be retired. Microsoft 365 governance needs clear responsibilities, usable guidance, and settings that support both.
Copilot is moving faster than your preparation
I assess content, permissions, ownership, and governance, then help identify useful Copilot scenarios and plan adoption. Workshops connect AI to actual tasks, including responsible use and reviewing results. Buying licenses is only one part of the work.
Apps and workflows are becoming difficult to maintain
I review legacy SharePoint and Microsoft 365 solutions and help decide what to modernize, simplify, replace, or retire. For Power Platform, that includes governance, environment strategy, ownership, and application lifecycle management, from development and testing to deployment and maintenance.
You need an experienced architect in the conversation
I provide architecture reviews, technical advisory, discovery workshops, and stakeholder facilitation. I help IT teams and business owners clarify requirements, challenge assumptions, and agree on a roadmap, with ongoing advisory when you need continuity.
I also support thought leadership through executive briefings, customer workshops, and speaking. I translate Microsoft 365 and AI developments into practical decisions, helping leaders and customers understand the tradeoffs and question the hype.
People need more than a launch announcement
Organizational change management belongs in the plan from the start. Whether you are introducing Copilot or replacing a familiar system, I help involve affected teams early, plan communications and practical training, and use feedback to adjust the rollout. People need to understand what is changing, why, and where to get help.
What working together looks like
We agree on scope, deliverables, responsibilities, and budget before starting. Depending on the engagement, the work can include:
- Understand the situation. Review the environment and speak with the people who administer, own, and use it. Agree on the problem, constraints, and desired result.
- Make the decisions. Document findings, explain options and tradeoffs, and build a prioritized roadmap, including dependencies, communications, training, and adoption support. Separate immediate needs from work that can wait.
- Carry out the agreed work. Deliver targeted changes, guide your team, or review work with your delivery partners. Use pilots and validation before a broader rollout.
- Hand it over properly. Provide documentation, walkthroughs, and knowledge transfer so your team understands what changed, why, and how to maintain it.
Who I work best with
I work with IT leaders, Microsoft 365 administrators, business owners, and delivery partners who need senior architecture support alongside their team. That might mean untangling an inherited environment, preparing for Copilot, or getting a second opinion before committing to a design.
The best engagements include people who can explain how work happens and help make decisions. Technical access matters. So does having someone who can decide who owns the site.
What I will push back on
I will push back on buying technology before defining the problem, unnecessary rebuilds, and complexity your team cannot maintain. I favor existing Microsoft 365 capabilities where they fit and explain when a limitation justifies something else.
Why work with me
I bring more than 20 years in technology, including 17+ years with SharePoint and the Microsoft collaboration stack. My work spans development, administration, architecture, governance, workshops, and adoption. That helps me connect technical decisions with the people who need to understand and use them.
I’m a Microsoft MVP for SharePoint and Microsoft 365 Copilot, a community leader, speaker, and the person behind UnsuckM365. My community work keeps me close to the people implementing these tools and the problems they encounter.
For a sense of how I think, start with these:
- The arc of a SharePoint scar: how small architecture decisions become long-term problems, and how to break the pattern.
- The day I stopped fighting SharePoint users: why adoption starts with understanding how people actually work.
- Copilot will expose your SharePoint mess: why AI readiness depends on content, permissions, and ownership.
Start with what is getting in the way
Received an expensive intranet modernization proposal and unsure what you are actually paying for? Get a second opinion before committing. I can help you understand the scope, question the assumptions, and decide what is necessary, what can wait, and whether a simpler approach would work.
Work directly with me on a focused review or a clearly scoped first phase. Start small, solve a specific problem, and build on what works. You do not need a finished project brief to start the conversation.
Looking for personal career or community guidance? I also offer free, informal mentorship when availability allows.