IGEL + Microsoft | Spike Partner Playbook

1 - Overview

A joint field-ready playbook for Windows 365 and Azure Virtual Desktop.

Microsoft delivers Windows from the cloud; IGEL removes risk and drift at the endpoint. Combine Windows 365 Cloud PC or Azure Virtual Desktop (AVD) with IGEL OS, Microsoft Entra ID, Conditional Access, Microsoft Intune, and IGEL Universal Management Suite (UMS) for a prevention-first posture.

When to lead with this

Cloud PC or AVD rollout at scale
Endpoint risk or audit objections
Device reuse and refresh pressure

The 30-second joint pitch

Microsoft delivers Windows from Azure. IGEL ensures nothing risky happens at the workspace access layer by replacing local Windows with an immutable OS that connects users to Windows 365 or AVD securely and consistently.

One-click helpers

2 - Architecture

How IGEL + Microsoft fit together in a prevention-first design.

Cloud workspace layer

Deliver Windows from Azure with Windows 365 Cloud PC or Azure Virtual Desktop. Keep user data and apps centralized, and validate performance with pilot baselines.

Identity and access controls

Use Microsoft Entra ID with Conditional Access and MFA to enforce identity-driven access. Align device requirements with the endpoint posture you want to prove.

Endpoint hardening layer

Replace local Windows with IGEL OS so endpoints are immutable and consistent. Policies, updates, and approved apps stay controlled through a standardized image and management.

Management story

Microsoft Intune manages cloud and identity controls; IGEL Universal Management Suite (UMS) manages IGEL OS fleets. Use co-management to keep responsibilities clear and auditable.

3 - Sales Plays

Five joint motions you can run immediately.

Each play includes triggers, a clear promise, and proof points to validate during a pilot. Keep claims grounded and use Spike to draft talk tracks and emails fast.

4 - Objections

Tackle the top objections before they stall the deal.

Use this matrix to respond without overpromising, and capture proof to validate.

5 - Field Guide

Position IGEL without adding complexity.

What IGEL is

IGEL is a hardened endpoint OS: a lightweight, read-only layer that replaces local Windows on the device and connects users to Windows desktops in Azure. Use it to remove drift, reduce attack surface, and standardize the workspace access layer.

Signals to bring IGEL in

Ransomware, endpoint risk, or audit concerns
Device reuse questions for Cloud PCs
Patching fatigue or high ticket volume
Citrix/VDI exit paired with AVD or Windows 365
Shared devices or frontline workflows

Your move

When you hear these signals, position IGEL as the way to remove endpoint objections so the cloud desktop motion closes faster and stays consistent at scale.

6 - Outcomes

Outcome framing that stays grounded.

Security

Reduce local-data exposure on endpoints
Enforce identity-driven access policies
Standardize endpoint posture across fleets

Operations

Faster rollouts with consistent device images
Fewer rebuilds and less endpoint troubleshooting
Cleaner handoffs between identity, cloud, and device teams

Cost and sustainability

Extend device life via safe reuse where appropriate
Reduce the operational overhead of Windows endpoints
Shift effort from rebuilds to governance and control

7 - Talk Tracks

Draft talk tracks tuned to the audience.

Executive / CIO

Keep it outcome-first: reduce endpoint risk, simplify operations, and accelerate Cloud PC adoption without expanding the attack surface.

EUC / Workspace engineering

Lead with architecture clarity: identity policies, Cloud PC delivery, and an immutable endpoint layer that reduces drift and speeds deployments.

8 - One-Pager

Summarize the joint story with a crisp one-pager.

Use this to recap outcomes, proof points, and next steps after discovery.

The joint IGEL + Microsoft story is about secure simplicity.

Together, we deliver Windows from Azure via Windows 365 Cloud PC and Azure Virtual Desktop to any device running the Immutable Endpoint OS from IGEL.

All execution and data stay in the cloud while the endpoint remains stateless, hardened, and centrally governed.

The result: lower cost of ownership, faster onboarding, and stronger Zero Trust security.

IGEL's Preventative Security Model and Microsoft's identity and cloud controls combine to simplify operations and accelerate hybrid work everywhere.

Proof points

Co-engineered Teams optimization
Intune + Universal Management Suite integration
Zero-touch provisioning
Reference wins across healthcare, finance, and public sector.

9 - FAQ

Answer the most common questions without overpromising.

Use this FAQ to stay consistent across security, operations, and deployment readiness questions.

FAQ

Q: Does IGEL work natively with Windows 365 and Azure Virtual Desktop?: A: Yes. IGEL endpoints use Microsoft's RD Client SDK with first-party app IDs for full Cloud PC and AVD access, including Teams media offload and Conditional Access support.
Q: How does IGEL improve security?: A: By design, the Immutable Endpoint OS runs read-only, with no local data and enforced TPM-based trust. Combined with Microsoft Entra ID, Conditional Access, and FIDO2 authentication, it forms a true Zero Trust posture.
Q: What does management look like?: A: Centralized policy and configuration through Microsoft Intune and the IGEL Universal Management Suite. Both tools interoperate to give IT unified control and audit-ready visibility.

Objection handling

Objection: We already have laptops.: IGEL extends their life, reduces patching and attack surface, and lowers support load by shifting compute to Azure Cloud PCs.
Objection: Isn't this another management layer?: No. IGEL simplifies the endpoint layer while integrating natively with Microsoft management, removing complexity, not adding it.
Objection: What if performance drops?: Performance is driven by Azure compute, not endpoint specs. IGEL's optimizations (Teams offload, GPU pass-through, smart peripheral handling) ensure consistency even on aging hardware.
Objection: What if Azure goes down?: The joint architecture supports multi-region failover, persistent Cloud PCs, and validated BCDR patterns through IGEL BCDR.

10 - Pilot Plan

Build a 30-day pilot plan with clear owners and success criteria.

Align on scope, validate readiness, and capture proof points in one motion.

11 - Next Steps

A simple motion: qualify, validate, expand.

1) Qualify

Identify endpoint risk and drift
Confirm Windows 365 or AVD motion
Define success criteria and CTA

2) Validate (pilot)

Baseline onboarding, support, and security posture
Prove policy alignment (Entra, Intune, UMS)
Capture audit-ready evidence early

3) Expand

Roll out by persona or workflow
Standardize images, apps, and support runbooks
Keep messaging grounded and repeatable