question

The problem here is, that with Hybrid you have a computer main account placed in AD and you can't just forget about it. I am afraid, that the only way to move to cloud only, is to re-install or reset the machine and enroll it via autopilot. Sure you can disjoin the computer from AD and uninstall the sccm client, but it would the as time consuming as to re-install the machine.

Hi @yannara ,
Thanks for prompt response however Microsoft also share some high level steps . If that consideration adopt still need to re-enroll device as our main focus is to migrate devices including policies/profiles from co-management to intune standalone and disable co-management. While keep remaining infra will remain same including AD, On-Prem Servers and exchange server

Please have a look on it if this approach suitable.

https://www.microsoft.com/en-us/insidetrack/migrating-mobile-device-management-to-intune-in-the-azure-portal

so we need to migrate on Intune Standalone

Why? There is no technical reason to do this, and we (Microsoft) do not recommend this (we don't recommend not doing this either as there may be valid reasons customers want to do so).

The documentation and link you've provided are not about Windows management or co-management, instead they are specific to mobile device (aka iOS and Android) management. Thus, they have nothing to do with getting rid of co-management.

Also, co-management has nothing to do with Exchange so any discussion of Exchange here is out of place and completely unrelated to whether or not co-management is used.

Hi Jason

This is what i suppose to find out since customer have co-management and need to migrate on Intune standalone as far as go through different blogs most of that redirect me to same approach since hybrid MDM service now retire by Microsoft on Sep 2019 so all they want to manage their devices via intune currently managed by SCCM.

The url i shared although not have co-management mentioned but if you again go through blog Window 10 devices mentioned, Plus once Microsoft introduced co-management and end user configured now why don't Microsoft updated detailed document on their official doc site instead of just announcement of retiring feature and share high level workload shift. Don't you think its kind of impractical since as IT guy or company we need to deal in production environment instead of fresh installation. The reason of asking this as this is a quite helpful platform so i just share max. existing infra details so if you have any best approach it will be helpful that how can we shift devices including polices/profiles to Intune Standalone without SCCM and without end user impact.

Sorry, not sure how to respond here except that the conclusion being drawn is incorrect and if you find any sources saying anything different, please point them out.

As noted, hybrid MDM has nothing to do with Windows 10 management or co-management so any sources citing hybrid MDM retirement as a reason to move to standalone Intune for Windows management are completely incorrect.

Co-management is 100% supported for Windows management and will continue to be so for the foreseeable future; there are no technical reasons any customer would or should move away from it.

Since hybrid MDM was retired nearly three years ago, why would we have any official documentation on it? It literally no longer exists or functions in any product. There is no approach to migrating away from it because it doesn't exist anymore.

Hi Jason,

May be you take it wrong what i need to share that on different blogs there are common approach that is workloads shift from SCCM console to completely move to intune standalone. Thanks for clarification that absolutely understood but again let make it clear a customer having co-management environment and want to migrate to Intune standalone although co-management support 100% but still they want to segregate it by removing co-management due to business needs and just interested to use intune standalone then its their own choice secondly since its client own demand so we gonna guide them either its possible or not if yes then How? Ofcourse Microsoft retire Hybrid MDM model so again point comes same if client wants to remove co-management then is there any Microsoft Documentation on that as simple . Hope it clarifies my point.

What business needs? just interested to use intune standalone?

Since customer did not disclose it but again may be due to users on remote areas or some on-prem limitation they decide to migrate on Intune standalone model to utilize fully cloud based features that seems reason

However just re-confirmed client have cloud attach model where they configured co-management (SCCM+Intune)

Thanks for responding all my concern it will be helpful , So there is no such documentation and we should engage fast track team or do it manual approach.

Can you please do favor to confirm if that steps mentioned in blog will be useful against client requirement?

https://systemcenterdudes.com/sccm-mdm-authority-intune-standalone/

Since customer did not disclose it but again may be due to users on remote areas or some on-prem limitation they decide to migrate on Intune standalone model to utilize fully cloud based features that seems reason

IMO, you are not serving the best interests of your customer by not fully informing them and learning of their motivations. As noted, they could be doing this for the wrong reasons. Also, co-management does give them fully cloud-based management so that's not valid.

Can you please do favor to confirm if that steps mentioned in blog will be useful against client requirement?

Same answer as above. That's for hybrid Intune which no longer exists.

May be no one is here to put himself in disaster Jason , So if Microsoft products sorry to say is capable enough then of course client did not bother to do that plus since for your info we already and even client knows the benefits of co-management since if someone don't want to disclose then we did not impose it. Instead of asking how or point out that we are doing serving or not is other debate since it is platform to discuss real base challenges and issue that end user face so instead of deep down investigation since Principle itself know better about their products and of course here is Microsoft. Even i did not deny about capability of co-management model so every organization has different requirements and way of taking stuff although Microsoft recommend best approach but don't you know think there should be some doc on that too if someone want to revert back from Cloud Attach model co-management to Intune standalone. Is there any consequences or mandatory i believe Microsoft should share real base scenarios and share approach instead of long debate how, why? discussion , Since customer requirement is priority basis so it should be flexible if they have such requirements then to share or asking this on platform to get aware of myself and other IT guys to come to know real scenarios and challenges faced. But again Client simply wants to migrate on Intune without SCCM and you mentioned its manual way fair enough but our concern is although it is Manual approach so Microsoft even don't have such documentation like how to revert back from cloud attach co management (SSCM+Intune) model to intune model which seems strange. Even after open ticket on Intune subscription by getting support on that and asking same question so they just share link

https://www.microsoft.com/en-us/insidetrack/migrating-mobile-device-management-to-intune-in-the-azure-portal

So even Microsoft support not getting it may be and that's the reason i share same question on that platform to get better clarity. At the end they recommend to open fast track team ticket to take up this requirement.

The reason for share whole story is that why Microsoft not sharing complete stuff step by step instead of default and simple configuration like here if you go though below url there is option of switch back workload to intune but not sure its same we should apply for client environment?

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

As you know sometimes documentations is required when client asking how to do that then there should be some high level steps even manual approach available on Microsoft Doc site so that we communicate client that yes it is possible but with manual approach and these are consequences and end user impact. Instead we IT guys post on different platform and getting different respond. Hope it would clarifies my point.

I'll ignore your rant (for now) as I've answered all of your questions exactly as you've posed them.

Ultimately, this isn't a path we recommend generally and we have no tooling built today to help with it. Full stop.

I'm sorry the person at Microsoft support gave you incorrect information. You should offer that as feedback to them.

As for your rant, I disagree completely. I was a very successful consultant for 10+ years and part of that was always understanding why and correcting misperceptions. If a person brings you a car to fix and says they want you fix the transmission because it is broken but you discover that the transmission is in perfect working order, then you replacing the transmission is a disservice to the customer and dishonest IMO. The "Why" is always important.