The Work
Microsoft 365 sits at the center of how my organizations communicate and collaborate. I handle the account side of things - creating users with the right licenses, managing group memberships, making sure Outlook and Teams access actually lines up with what people need. I also tie everything back to Active Directory so identity stays consistent across both systems.
When email or Teams goes down, work stops. That’s why I treat account setup and licensing like it matters - because it does. A misconfigured user can’t collaborate. Wrong permissions mean access issues that slow everything down.
Why It Matters
The day-to-day work is unglamorous: provisioning accounts, fixing sign-in issues, managing group memberships when roles change, sorting out Teams permission tangles. But it’s the foundation for everything else. Bad account hygiene creates friction that shows up in support tickets for weeks.
Most M365 problems aren’t actually in the application - they’re in identity and licensing. That’s where I spend my time. When someone can’t access Teams, I check their license and AD group membership first. Usually, that’s where the issue lives.
What I’ve Learned
Consistency saves headaches later. Same provisioning checklist every time. Same offboarding process. When you automate the boring bits and document them well, support requests drop significantly. I’ve learned that the best time to fix an access problem is the moment someone gets provisioned wrong, not weeks later when their manager asks why they’re not in the right Teams channel.