This blog is the second of three that details our recommendation to adopt cloud native device management.
A common thread through the customer stories was how they achieved greater security, cost savings, and readiness for the future through their cloud transformations.
In this blog, I will focus on how you can accelerate your transition to cloud native endpoint management.
Many of my customer conversations are centered on how best to transition, with the value of a cloud first approach already understood.
Third, for new Windows devices, go straight to cloud native.
Enabling all management workloads from the cloud is the fastest way to reduce the complexity and cost of current technology and get closer to a single pane of glass.
The first are management functions that you move from ConfigMgr to the cloud, such as updates, app deployment, and policy configuration.
In general, you should start by enabling the net new cloud workloads discussed above, then move the existing workloads from ConfigMgr.
With security policies in place, we often see customers next move updates workloads to the cloud to take advantage of the Microsoft modern approach to updating devices on any network, anywhere in the world.
Of course, in some instances, there may be one or two workloads that can't immediately be moved to the cloud.
Our recommendation here is not to let one or two laggard workloads stop you from gaining the rest of the benefits from moving to the cloud.
It takes time to transition to the cloud and modernize your directory and management solutions.
By taking this first step of enrollment and hybrid Entra join, you receive the benefits of the cloud workloads and can transition away from dual management-such as existing devices receiving workloads from on-premise ConfigMgr, and new devices from the cloud.
Microsoft has many partners with deep expertise in migrating Windows to the cloud who have seen success using this approach.
As you refresh or reset Windows devices, our recommendation is to manage them as fully cloud native.
Many customers opt to skip the co-management phase of migration completely, bringing new devices on as cloud native.
These customers use their hardware refresh cycle as the catalyst to move to cloud native.
Existing devices remain with on-premises management while new devices are deployed as fully cloud native.
After a full hardware refresh cycle over 2-3 years, all Windows devices will eventually be managed exclusively in the cloud.
We are excited to be seeing more and more companies move to a fully cloud native approach for endpoint management, so I hope if you're not there already, this blog helps you identify the proper steps to get there.
This Cyber News was published on www.microsoft.com. Publication date: Mon, 29 Jan 2024 23:43:03 +0000