Modern Workplace Architect · Mumbai
Hi, I'm Jignesh.
I make Microsoft 365 just work at enterprise scale.
I'm a Microsoft 365 architect in Mumbai. Banks, insurers and large enterprises call me when they want to move to the cloud, tighten identity and device security, or migrate tenants without anyone losing a day of work. Half a million people use what I've built. Most never notice. That's the point.
- Security by design
- Cloud done right
- Tenant migrations at scale
- AI with guardrails
What I design
Digitization, security, cloud and AI. One standard: it has to survive production.
Identity and device architecture
Entra ID design, Conditional Access models, Intune device management across Windows, macOS and Linux, and Autopilot provisioning that scales past the pilot.
Tenant migrations and modernization
Tenant-to-tenant moves, Exchange and Teams transitions, and SharePoint restructuring, planned in milestones with rollback paths and zero surprises for end users.
Security and compliance
Purview information protection, Defender workloads and Zero Trust baselines built for regulated environments, with BFSI audit expectations designed in from day one.
AI for the modern workplace, grounded in governance
Copilot for Microsoft 365 readiness done in the right order: Purview data governance first, licences second. Azure OpenAI assistants grounded on tenant knowledge for IT operations. AI-generated media (video walkthroughs, adoption visuals, end-user campaign assets) that cuts the cost of change management. Every experiment here targets a deployment problem I have met in the field.
Teacher and traveller
Guest lecturer on cloud computing at Mumbai engineering colleges. Travel writing at Roaming Footprints. Both make the architecture diagrams better.
How I work
The habits behind eleven years of designs that did not come back broken
Design for the worst day
Every architecture assumes an auditor, an outage and an attacker will all show up eventually. The design has to answer all three before go-live, not after the incident review.
Decisions over documents
Architecture documents record the trade-offs, not just the outcome. The client's own engineers should be able to operate, extend and defend the design without me in the room.
End users are the real SLA
A migration nobody noticed is a successful migration. Pilot rings, rollback paths and plain-language communication are part of the architecture, not an afterthought.
Field notes
Writing from real deployments
Configuration patterns, migration lessons and security baselines, written after they worked, not before.
No Results Found
The page you requested could not be found. Try refining your search, or use the navigation above to locate the post.