About us

Intuitive.AI is one of the fastest-growing (INC 5000, CRN) Cloud & SDx solution and services companies supporting enterprise customers on a global scale. Intuitive is an "Engineering Company" delivering measurable value and key business outcomes.

Intuitive Superpowers

- DataOps & AI/ML
- Cloud Native, AppSecOps, DevSecOps
- Cloud Migration & Transformation
- Cloud FinOps
- Cybersecurity (App/Data/Infra) & GRC
- SDx & Digital Workspace We are proud to partner with some of the world's leading enterprises and serve 200+ customers across different industry verticals. We have achieved many milestones along the way, including being recognized as a top-10 fast-growth 150 IT company in the Americas by CRN in 2022 and being named one of America's fastest-growing private companies by INC 5000 in 2022. That’s not all! Even CIO Review awarded us as the Most Promising Cloud Migration Company and Artificial Intelligence Solutions Provider in 2022. About the job:

Title – M365 Architect

Start date: Immediate

Position Type: Full Time

Location: India (Remote)

Must Have skills- Entra ID/Azure Active Directory & Active Directory On-Premises.

Microsoft Exchange (online & on premises both).

Microsoft SharePoint Online & One Drive.

Microsoft Teams.

Microsoft Defender (365, Security, Endpoint, Identity, Office apps).

Migration Architecture and experience, On-Premises to cloud, cloud to cloud, mergers, demergers, etc. Good/nice to have – Power Apps, Power Automate, Power BI.

CoPilot Studio & Agent 365.

MECM, SCCM, other MDM Tools.

Azure Security.

Entra Connect & other Identity Management Tools.

3rd Party SAML/SSO integration. Why this role exists

Enterprises are no longer buying Microsoft 365 as an email and file-sharing platform. They are buying it as their identity fabric, their security perimeter, their compliance boundary, and now their AI surface — and most of them are three or four architectural decisions away from doing it badly.

We need an architect who can walk into a discovery workshop with a CIO, CTO, a CISO, and a sceptical infrastructure lead, and leave with a defensible target-state architecture that all three of them can sign. Someone who designs for the migration and the operating model that follows it.

This is a client-facing architecture role, not a back-office design role. You will shape opportunities before they become RFPs, own the technical narrative through the deal, and stay accountable for whether the architecture survives delivery.

Our operating principle: “DWE & IAM owns delivery. You architect within established guardrails—and make those guardrails practical, actionable, and fit for purpose.”

What you'll own

Solution architecture

Design end-to-end target-state architectures across Entra ID, Exchange Online, SharePoint/OneDrive, Teams, Intune, Purview, and Defender — including HLD/LLD, integration patterns, and non-functional requirements

Architect hybrid and coexistence states that clients can live in for 18 months, not just the clean end state

Make and document the hard calls: identity model, tenant strategy,



licensing edition, migration sequencing, what stays on-premises and why Identity as the foundation

Architect Entra ID at enterprise scale: Conditional Access design, PIM, ID Protection, Entra ID Governance (entitlement management, access reviews, lifecycle workflows), hybrid sync and federation retirement

Integrate with the client's existing IAM estate — SailPoint, Saviynt, Okta, CyberArk, Ping — rather than pretending it isn't there

Design Zero Trust access patterns that survive an audit and don't generate a helpdesk queue Migration & modernisation

Own the architecture for complex migrations: on-premises Exchange and SharePoint to cloud, Google Workspace to M365, and tenant-to-tenant work driven by M&A;, divestiture, or carve-out

Design SCCM-to-Intune co-management and endpoint modernisation paths, including Autopilot, Autopatch, and Windows 365 / AVD where they fit

Security, compliance & data governance

Architect Defender XDR coverage (Office 365, Endpoint, Identity, Cloud Apps) and the Purview control set: sensitivity labels, DLP, retention, Insider Risk, Communication Compliance, eDiscovery

Design Copilot readiness properly — oversharing remediation, SharePoint Advanced Management, permission hygiene, restricted search — because Copilot exposes every governance shortcut a client ever took AI & automation

Architect Microsoft 365 Copilot rollouts and Copilot Studio agent governance, including tenant-level controls, data boundaries, and adoption instrumentation

Design Power Platform solutions where they're the right answer (ITSM, workflow, approvals, low-code front-ends) and say so when they aren't Pre-sales & practice leadership

Lead discovery workshops, technical assessments, and current-state gap analyses; convert findings into a costed roadmap

Build POV/POC frameworks, proposals, and solution decks that win on substance

Own technical scoping, estimation, BOM and licensing optimisation, and the technical sections of RFP/RFI responses and SOWs

Build reusable IP — reference architectures, assessment tooling, accelerators — so the second engagement is faster than the first

Mentor engineers and consultants into architects; act as escalation point on complex delivery First 90 days

Days 1–30 — Absorb the current portfolio and delivery estate. Map our existing reference architectures and find the gaps. Shadow two live client engagements. Form a point of view on where our M365 architecture practice is solid and where it's improvising.

Days 31–60 — Take technical ownership of at least one live opportunity end to end. Publish a target-state reference architecture for one core domain (identity, endpoint, or data governance)



that consultants can pick up and use.

Days 61–90 — Lead a client discovery workshop solo. Deliver a costed, phased roadmap that survives CISO scrutiny. Have a defensible plan for the practice IP you'll build over the next two quarters.

What we'll measure

Technical win rate on opportunities you architect

Architecture quality at handover — how much gets redesigned once delivery starts (target: very little)

Reusable IP shipped and adopted by delivery teams

Client CSAT and the number of engagements that expand rather than end

Engineers you've levelled up Must-haves

Depth (you've designed and defended these, not just read the docs)

Entra ID — Conditional Access, PIM, ID Protection, Governance, hybrid identity and Connect/Cloud Sync

Exchange Online including hybrid mail flow and migration; SharePoint Online and OneDrive at scale

Teams — collaboration and voice (Direct Routing, Operator Connect, Teams Phone, Rooms)

Intune — MDM/MAM, Autopilot, co-management with Configuration Manager, compliance and configuration baselines

Microsoft Defender XDR suite and Microsoft Purview

Microsoft Graph, PowerShell automation, and M365 tenant governance and licensing economics (E3/E5/F-SKU trade-offs) Breadth

Working knowledge of Azure landing zones, networking, and how M365 identity intersects with Azure workloads

Comfort with third-party IAM, MDM, and security tooling in a heterogeneous estate The part that's harder to hire for

You can hold a room of senior stakeholders and translate architecture into business consequence and cost

You write clearly — architecture documents, proposals, and decks that don't need rewriting

You take a position, show your reasoning, and change your mind when the evidence changes

You're direct about risk with clients, early, in writing Certifications — at least two of: SC-100, SC-300, MS-102, MD-102, SC-400, MS-700, AZ-305. Expired certs and current knowledge beat current certs and stale knowledge; we'll ask questions that tell us which you have. Nice-to-haves

Experience inside a Microsoft partner or SI — co-sell motions, Partner Center, funding programmes (CSI, ECIF), advanced specialisations

Google Workspace or Okta migration experience

Regulated-industry exposure — BFSI, healthcare, pharma — and data residency work

Infrastructure-as-code for the Microsoft cloud (Bicep, Terraform)

TOGAF or equivalent architecture framework grounding This role is probably not for you if

You want to architect from a distance and hand documents over the wall

You need a fully-formed brief before you can start

You'd rather not be in front of clients

You architect to the product roadmap instead of to the client's constraints What we offer

Architectural authority — you own the technical decisions, not a committee

Enterprise clients with genuinely hard problems, across the full Microsoft cloud surface A practice being built now, with room to shape how it works

Certification and lab funding, Microsoft partner enablement, and direct access to product teams

📌 Architect (India)
🏢 Intuitive.ai
📍 India