Blog Post

Microsoft Intune Blog
3 MIN READ

What’s new in Microsoft Intune: January 2025

ScottSawyer's avatar
ScottSawyer
Icon for Microsoft rankMicrosoft
Feb 07, 2025

After any amount of time away from the office, there's a moment when my return to work becomes real: confronting my email inbox. Now, thanks to Microsoft Copilot, this is no longer the chore it once was. Rather, it's become an optimal time to reengage my work mind. This change reflects how we approach improvements to Microsoft Intune. Every new capability is meant to address the needs of the companies that rely on our service and the admins who sign in to the portal every day. This month I'm highlighting how we make that daily work more functional, user friendly, and secure.

Copilot insights for Microsoft Intune Endpoint Privilege Management

For IT professionals or help desk administrators responsible for responding to app elevation approvals with Intune Endpoint Privilege Management, granting privileges for a malicious app can have disastrous consequences. When an elevation request for a new or unfamiliar app is made, IT pros manually research whether it's safe to grant the request. Now, with the help of Microsoft Copilot in Intune, IT pros can get approval guidance to help identify potential app risks without the time and effort of a manual investigation. In addition:

  • Every IT admin, especially new IT practitioners, can make well-informed decisions.
  • Copilot will send the file hash from an elevation request to Microsoft Defender Threat Intelligence to detect possible malicious indicators.
  • When malicious files are detected, the result contains a link to Microsoft Defender Threat Intelligence so that administrators can initiate an incident response.
  • When files are determined to be safe, administrators can create rules directly from the request for future use.

See a demonstration from the 2024 Ignite Breakout session of this and other exciting capabilities of Copilot in Intune. Copilot insights for Intune Endpoint Privilege Management is now rolling out in public preview.

Beyond what's new: Windows Autopilot device preparation

As I was thinking about what we recently released in Intune that makes things more functional and user friendly, Windows Autopilot device preparation immediately came to mind. What began as a project to bring Autopilot to Government Community Cloud High (GCCH) and Department of Defense (DoD) environments grew into something much more. Based on updates made last year to address security requirements, Intune enhanced the architecture for device preparation. The team then explored what more they could do to create an experience to complement these Autopilot advancements.

What distinguishes the Autopilot device preparation experience is speed, consistency, reliability, and reporting. Users have a better onboarding experience and can be productive sooner thanks to a streamlined policy provisioning screen coupled with enrollment time grouping, which delivers configurations much sooner when compared to using dynamic device groups to enroll devices. Admins can configure critical line-of-business, Win32, and Microsoft Store applications as well as PowerShell scripts to be installed during the out-of-box experience (OOBE) to help ensure the device is secured before the user gets to the desktop. Deployment reporting is also significantly improved: deployment time, application status, and PowerShell scripts status details are now offered in near real time.

Additionally, for circumstances in which enrollment should be limited to specific company-owned devices, device preparation can use the corporate identifier enrollment feature in combination with enrollment restrictions to block personal enrollments. This helps ensure only trusted, preapproved devices are allowed to enroll in Intune.

If you would like to dive deeper into Windows Autopilot device preparation, check out the skilling snack our team put together on the Windows IT Pro Blog. Autopilot device preparation is available today for Windows 11, and it will be available for Windows 365 in the coming months. Enrollment time grouping for Windows is available today with iOS/iPadOS automated device enrollment, and Android support will release in the coming months.

Making work more engaging and reducing the amount of time and effort required for routine activities are just some of our goals for Intune. To achieve these goals, we need specific input from you about how you work and what your priorities are. I encourage you to leave comments and engage with our social handles to help us shape a product that serves you and your organizational needs.


Stay up to date! Bookmark the Microsoft Intune Blog and follow us on LinkedIn or @MSIntune on X to continue the conversation.

Updated Feb 07, 2025
Version 1.0
  • PetterHaa's avatar
    PetterHaa
    Copper Contributor

    Would really like to have pre-provisioning option for device preparation. And also being able to choose to install Windows quality updates during pre-provisioning with device preparation.

  • fjansson's avatar
    fjansson
    Brass Contributor

    I agree with the other comments when it comes to the lack of a device naming template. Once device preparation has more functions from the "v1" path it will be more interesting for us at least.

    From the FAQ I can read that "There's no need to migrate from existing Windows Autopilot profiles to Windows Autopilot device preparation policies. We expect both solutions to exist in parallel for a while as we work to improve the experience and add more functionality." Windows Autopilot device preparation FAQ | Microsoft Learn


    Are there plans in the future to support a migration path like this?

  • PuDerBaer's avatar
    PuDerBaer
    Copper Contributor

    What we really need is the option to define a predefined device name in the deployment profile. All assignments that are dependent on the device name then wait for the device to be restarted because a reboot is always required for a rename. In addition, all software installation processes are interrupted during a reboot, which leads to an unsatisfactory user experience. It should be possible to create the device directly with the correct device name! 

    • rgommers's avatar
      rgommers
      Iron Contributor

      Indeed, setting up a correct device name leaves much to be desired. When a device is joined to Autopilot, it even skips the device name step during the OOBE of a fresh installation. This, combined with the lack of predefined device name options, makes it really cumbersome to change device names. Additionally, all devices will show up in portals once as DESKTOP-XXXXXX and stay like that if we don't change it.

      Additional device name settings for Autopilot deployments would be more than welcome.

  • Paul Whitman's avatar
    Paul Whitman
    Copper Contributor

    Any news on when Intune Endpoint Privilege Management for macOS will be available?