Intune Migration (SCCM will be discontinued)

Huxley Haroldo dos Santos 20 Reputation points
2023-05-16T23:06:56.1+00:00

We have a client that will have a SCCM Server (Version 2303) discontinued. They have configured co-management (SCCM+Intune) hybrid model having On-Prem SCCM with the agents installed.

All clients machines already are on Intune.

The correct change to workload is to follow the steps below? Setting all workloads to Intune?

https://docs.microsoft.com/en-us/configmgr/comanage/how-to-switch-workloads

If we set this option above, new devices can be automatically assigned to Intune normally?

Other question, about the agents installed on machines...we could keep on it?

PS: In advance, we have changed the option above from de link, in other words, we set to only Intune, but there still show manager by co managment and not to just Intune. Should I worry about this? (If a click on device, I look that the workload are managed by Intune).

That is all!

Thank you!

Microsoft Security | Intune | Configuration
0 comments No comments
{count} votes

Accepted answer
  1. Crystal-MSFT 53,991 Reputation points Microsoft External Staff
    2023-05-17T06:05:25.56+00:00

    @Huxley Haroldo dos Santos, Thanks for posting in Q&A. From your description, I know you want to move from configuration manager to Intune. And the SCCM will be discontinued.

    I notice co-management is configured. After that, we can set the MDM Authority to Intune and switch all workloads from SCCM to Intune. You can try the steps in your link. After the workloads are switched, we can go to one device side to confirm if the workloads are all switched to Intune as below:

    User's image

    And then we can uninstall the Configuration Manager client. Devices will be ready to apply the app or policy from Intune. Here is a link with more details for your reference:

    https://learn.microsoft.com/en-us/mem/intune/fundamentals/deployment-guide-intune-setup#option-3---move-from-configuration-manager-to-intune

    For new device, as SCCM is not used any more, then we can consider other enrollment method to enroll into Intune. You can choose one according to your situation. Here are some enrollment methods for your reference:

    BYOD: Enroll their personally owned devices via company portal.

    DEM: It is a special service account have permissions that let authorized users enroll and manage multiple corporate-owned devices. These types of devices are good for point-of-sale or utility apps, for example, but not for users who need to access email or company resources.

    Automatic enrollment via MDM: Joins the device with Azure Active Directory and enables users to sign in to Windows with their Azure AD credentials. If Auto Enrollment is enabled, the device is automatically enrolled in Intune.

    Automatic enrollment via Group Policy: Configure Active Directory group policy to automatically enroll devices that are hybrid Azure AD joined. (Join on-premise domain, register to Azure AD device to enroll into Intune. Mainly for existing domain joined device.)

    Windows Autopilot: Set up and pre-configure new devices, getting them ready for productive use.

    Bulk enrollment: lets an authorized user join large numbers of new corporate-owned devices to Azure Active Directory and Intune. non-user affinity, can use device license.

    https://learn.microsoft.com/en-us/mem/intune/fundamentals/deployment-guide-enrollment-windows

    For your question, I think you need to uninstall Configuration Manager client after the workloads are all switched.

    Hope the above information can help.


    If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.


0 additional answers

Sort by: Most helpful

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.