0% found this document useful (0 votes)
77 views

Getting Started with Intune Migrations Framework

The document outlines a structured approach for migrating to Microsoft Intune, divided into four main phases: Assess, Design & Plan, Test & Verify, and Deploy. Each phase includes specific tasks related to evaluating current systems, designing migration processes, testing device onboarding and migration, and executing the deployment strategy. Key considerations include user change management, operational models, and ensuring device eligibility and prerequisites are met before migration.

Uploaded by

indiakalkine
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
77 views

Getting Started with Intune Migrations Framework

The document outlines a structured approach for migrating to Microsoft Intune, divided into four main phases: Assess, Design & Plan, Test & Verify, and Deploy. Each phase includes specific tasks related to evaluating current systems, designing migration processes, testing device onboarding and migration, and executing the deployment strategy. Key considerations include user change management, operational models, and ensuring device eligibility and prerequisites are met before migration.

Uploaded by

indiakalkine
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 1

Migrating to

Microsoft Intune
Project Work Breakdown Structure

1. ASSESS
Assess 3rd party MDM & Operations Assess current Intune and Azure AD state

• Capabilities • Management mode & • Users & groups • User identity • Existing Intune usage
• Inventory enrollment process • Reporting • Licensing • Policies
• Operations • Apps, config • Integrations • Existing Integrations • Conditional access
• RBAC

2. DESIGN & PLAN


Mobile devices Windows devices Others… Common foundations

Assess gaps between current vs target desired state & define the migration
scope (devices, policies, apps, groups to be migrated) • Core Intune setup • Network infrastructure (VPN, NAC,
• Identity & Azure AD Proxy, etc.)
Use case A: Implement use-case for onboarding new or unmanaged devices • Roles & scopes • Printing
(enrollment, apps, configuration, compliance, updates, conditional access, • Operational support model • Resources access
remote actions) • 3rd party integrations • Reporting
• Certificate management
• Conditional access policies
Use case B: Design the migration process and tools for existing devices

Operations and Target Operating Model

• Devices lifecycle & update management • Administration & Support model


• RBAC model definition • Reporting requirements
• Devices provisioning process

User change management & communication

• User adoption kit & training • Pilots’ communication and feedbacks tools
• Communication strategy
• Ambassadors program

3. TEST & VERIFY


Mobile devices Windows devices Others… Operations

Use case A:Test onboarding new or unmanaged devices (enrollment, apps, RBAC & operational model
configuration, compliance, updates, conditional access, remote actions,
access to resources, all common foundations, etc.) Reporting

Support
Use case B: Test migration of existing devices to Intune

4. DEPLOY

Prepare and verify prerequisites and user eligibility Deploy progressively

1. Prepare user prerequisites: Azure AD accounts, licensing, group 1. Depending on the platform and your migration strategy, initiate
memberships, policies & apps assignments either device wipe operations or unenroll/enroll operations. Those
operations can be done either by the end-user or by central IT
2. Prepare for device migration: move device to your Zero Touch portals
if necessary, whitelist corporate device identifiers, assign enrollment 2. Deploy your migration solution in progressive waves and plan for a
profiles to target devices, push migration tools if necessary rollback solution if any problem occurs
Classified as Microsoft Confidential

You might also like