Migration Guide Intune Hybrid to Intune Standalone Configuration Manager ConfigMgr SCCM. We seriously discussed the decision-making process between Intune hybrid and standalone.
In that post, we discussed 8 Reasons to Select Intune Standalone Over Hybrid. In summary, the decision was to go with Intune standalone instead of jumping on the slow train.
This post will show the migration guide from Intune hybrid SCCM to Intune standalone.
Read the Microsoft case study sharing best practices and lessons learned from Microsoft’s SCCM Intune hybrid to standalone migration. Related Posts – 8 Reasons to Select Intune Standalone Over Hybrid.
Table of Contents
Video – What are Intune Design Decisions – Migration Guide Intune Hybrid to Intune Standalone Configuration Manager ConfigMgr SCCM
What are Intune Design Decisions | Why Intune Standalone Architecture? No Integration with SCCM?
- AVD Windows Multi-Session Intune Hybrid Azure AD Support
- Intune Report for AAD Joined Vs Hybrid AAD Joined Devices using KQL Query
- Intune Device Encryption Status Report
- Track Who Modified Intune App Deployment From Audit Logs
So what is Next?
So SCCM Intune Co-Managed devices are the option that Microsoft proposes to adopt for all organizations. The co-management will help organizations to move toward modern management
Microsoft’s Experience
During the MVP Summit in Seattle, we had a great discussion with Shitanshu Verma and his team about their experience of migrating from Intune hybrid to Intune standalone.
I didn’t find any posts on this topic from Shintanshu or his team. It would be great if he could have a post on Intune’s standalone migration topic.
NEW customers should select INTUNE STANDALONE as a preferred method
EXISTING customers should start PLANNING to MIGRATE to INTUNE STANDALONE
Microsoft wants existing customers to move to Intune’s standalone environment. Intune hybrid might die soon (this is my best guess). As I mentioned in the previous post, the existing Intune hybrid customers should start planning a migration from Intune hybrid to Intune standalone.
Following are High-Level Content Covered in this Guide
I discussed more than eight (8) reasons to choose Intune Standalone over Hybrid and performed a detailed decision-making process analysis to support this choice. This step helps to find an executive sponsor for the Intune standalone migration project.
- Convince Your Boss – Intune Standalone Decision
- Inventory – Identify Configurations, Users, and Devices to Migrate
- SCCM Prerequisite for Intune Standalone Migration
- Intune Standalone Migration Tool
- Prepare for Intune Standalone User Migration
- Phased User Migration – Intune Standalone
Convince Your Boss – Intune Standalone Decision
Microsoft has already provided detailed documentation of this decision-making process and is committed to updating the following documentation. For more details, choose between Microsoft Intune standalone and hybrid with SCCM.
Convince Your Boss = YES
Inventory – Identify Configurations, Users and Devices to Migrate
Once you decide to migrate to Intune standalone, this is the inventory phase for migrating from hybrid MDM (Intune integrated with SCCM) to a cloud experience using Intune on Azure.
The first phase is to perform an inventory on your existing Intune hybrid (SCCM) environment to understand the special configurations. This inventory task should be performed using the Intune Data Importer tool. This will help you to understand the existing setup and plan your migration.
The next step of Intune standalone migration is to identify the infrastructure dependency on your on-prem infrastructure. NDES servers could be one dependency for certificate deployment. You should build an NDES server before migrating from Intune Hybrid to standalone.
Inventory = Collected?
SCCM Prerequisite for Intune Standalone Migration
SCCM 1610 or later is the minimum requirement for Intune standalone migration. Microsoft recommends specifying the top-level site (CAS or standalone Primary) hierarchy. This is not a specific requirement from SCCM or Intune’s perspective. But this is to provide support for the Intune standalone migration tool.
Microsoft provides an Intune standalone migration tool to migrate users’ devices from SCCM to Intune. The tool only discovers objects accessible by the user running it. Ensure the user who runs the prerequisite tool has SCCM FULL admin rights on the SCCM hierarchy and service admin rights on Intune.
SCCM 1610 and Later = Ready?
Intune Standalone Migration Tool
Download the Intune Data Importer tool and run it from the top-tier SCCM server to collect the inventory details. The user with SCCM Full admin and Global admin must first run the Data Importer tool using the following intunedataimporter.exe -GlobalConsent parameter.
The Intune Data Importer tool collects data about the objects you select from your SCCM hierarchy. This details the objects you can select for import and why some things cannot be imported. It also lets you import selected objects into your Microsoft Intune tenant.
I don’t think all the objects from SCCM can be migrated to Intune with the tool. You need to do loads of manual work to complete the migration to Intune. Fix all the errors in the Intune data importer tool. This tool will help you get the inventory.
| Intune Standalone Migration Tool |
|---|
| Configuration items |
| Certificate profiles |
| Email profiles |
| VPN profiles |
| Wi-Fi profiles |
| Compliance policies |
| Apps |
| Deployments |
Intune Data Importer Tool = Downloaded and Ready to Run?
Prepare for Intune Standalone User Migration
Identify the pilot user(s) to perform the pilot migration of Intune standalone. Before the pilot user migration, make sure you complete the following steps.
- Get ready with Server infra – NDES, Exchange connector
- Communicate the change plan to all the stakeholders
- Start training support staff for Intune device management (Start Learning Intune)
- Fix all the errors of the Intune import tool
- Fix Role Based Administration for Intune admins
- Get ready with Intune (Data Warehouse) reports to replace Intune reports
- Find out the Graph API details to automate the Intune workflow
All the preparation tasks are Completed = Yes?
Phased User Migration – Intune Standalone
Don’t change tenant-level MDM authority to Intune until all the users are migrated. My recommendation is to perform phased user migration. Migrated users and their devices are managed in Intune.
When you use co-management Windows devices, they can be managed via Intune and SCCM. You can configure a mixed MDM authority in the same tenant by selecting some users to be managed in Intune. Other users continue to be managed in SCCM.
You can gradually migrate additional groups of users until you are ready to switch the tenant-level MDM authority from SCCM to Intune standalone. Tenant Level MDM Authority = Mixed Mode
Resources
- Import Configuration Manager data to Microsoft Intune
- Prepare Intune for user migration
- Change the MDM authority for specific users (mixed MDM authority)
- Change your MDM authority to Intune standalone
We are on WhatsApp now. To get the latest step-by-step guides, news, and updates, Join our Channel. Click here. HTMD WhatsApp.
Author
Anoop C Nair is Microsoft MVP from 2015 onwards for consecutive 10 years! He is a Workplace Solution Architect with more than 22+ years of experience in Workplace technologies. He is a Blogger, Speaker, and Local User Group Community leader. His main focus is on Device Management technologies like SCCM and Intune. He writes about technologies like Intune, SCCM, Windows, Cloud PC, Windows, Entra, Microsoft Security, Career etc…
Is this migration guide stil valid in 2019 july?
I think, yes. The blog post is still valid for SCCM 1902 and 1906. Do you have any specific question Rahul ?
Hi Anoop, Do you have any article for customers that wants to move from Standalone SCCM to Standalone Intune? (Not for Hybrid SCCM or Co-management or Cloud attached MCEM etc)
Hello I don’t have any specific document for that scenario. But I don’t see any automated migration options.. it should be a side by side migration from SCcm to Intune … are you planning to rebuild the machines or use the existing machines
I think some of the machines will be rebuild as hardware needs to be replace and some might be existing machines.
What would be the best approach for migration from standalone sccm to standalone intune ?. What all things need to be taken care?
I think the best way to rebuild all the machine and move to azure ad joined scenario … but this would take more efforts … the other option is domain join and intune managed … this could be bit tricky sometimes
Ok Thanks.. Also whether Intune data importer tool will be of any help in any way for such type of movement that is standalone sccm to standalone intune.. Also what issues we might face for machine with domain join and intune managed..
Hi Anoop,
Our environment use SCCM for App deployments. Now a small division is separated and formed a new company where the deployment tool is Intune. Is there any way we can use all the sccm packages directly in Intune? Any available tools to convert sccm packages to Intune compatible? If so is it a standard practice and could there be any challenges in future?
Hi, I’m not aware of any tools to do that at this point in time. There are some community tools available to convert the sccm applications to IntuneWin format. I have explained one of them https://www.anoopcnair.com/wvd-management-with-intune-windows-virtual-desktop/
Hi Anoop,
I noticed the link to the tool is no longer working? Is this path still valid?
If not is there a plan to migrate from MECM to MEM support by MS?
Thank you!
Rasheedah
Hi, I don’ think it’s still valid.
Hi Anoop,
“Data Importer Intune tool” is not valid anymore.
could you suggest any other tools for importing from SCCM Hybrid to Intunes Standalone?
Thanks
Rishi