Microsoft Intune presents a new approach to Windows patching, replacing on-prem servers with Windows Update for Business (WUfB). It offers features like Update Rings, Automatic Update Behavior, and a Deployment Service. Windows Autopatch on Intune automates patch deployment, but requires specific software/licensing. Best-in-class reporting is also available, addressing traditional reporting issues.
The article discusses securing local administrators with Microsoft Intune, covering creating the admin account, deploying the LAPS policy, protecting local administration groups, and working with Entra users and groups. It emphasizes the ease of using Intune for these purposes and shares insights on Entra user and group challenges. Overall, it advocates leveraging Microsoft’s EPM alongside Intune for robust security.
In Part 3 of transitioning from Workspace ONE to Microsoft Intune we turn our attention to application delivery. We look at the different ways we can deliver apps on Windows devices.
Part 2 delved into profiles, baselines, scripts, and product provisioning. It demonstrated how to configure Windows 10 PCs in Workspace ONE and Microsoft Intune, covering CSPs and translating profiles. Baselines and scripts in both platforms were compared, highlighting differences and capabilities. Product provisioning was briefly outlined.
The author details their transition from VMware to the Microsoft stack and introduces a series called “The Workspace ONE Admin’s Guide to Intune.” In Part 1, they discuss UEM Core components in both Workspace ONE and Intune, covering infrastructure, device compliance, and integrations. They also compare device enrollment and compliance in both platforms, highlighting their differences and similarities.
The author plans to continue the series with a focus on profiles, policies, and scripts.
The post discusses the introduction of Microsoft Cloud PKI as an alternative to SCEPman, highlighting its features, cost comparison, and user experiences. It covers the process of building a Microsoft Cloud PKI Root CA and Issuing CA, deploying certificates, and the platform’s reporting aspects. The author expresses a positive outlook towards Cloud PKI’s capabilities and future implications.
Windows Hello for Business (WH4B) is often misunderstood as complex, but Cloud Kerberos Trust simplifies it. With familiar concepts and a straightforward setup process, it allows for seamless authentication to Azure/Entra ID. Configuring Azure AD Connect and Entra Kerberos Server for Cloud Kerberos Trust is simple, elevating user and admin experience.
Microsoft recently announced new features in Public Preview, including Intune guided setup, dedicated and shared modes, fail-fast mechanism, and local PC settings management. These enhancements allow for personalized experiences and improved troubleshooting, showcasing Microsoft’s commitment to evolving Windows 365.
Microsoft Entra ID has made huge improvements over the last 12 months. Okta is the SSO marketplace leader. How close are they on core capabilities? Read part one of my Entra vs Okta battle for SSO supremacy.
Recently, I had the pleasure of working Microsoft Ignite as part of the Windows 365 MVPs (Thanks again Christiaan). During
