Blog Post

Microsoft Intune Blog
4 MIN READ

What’s new in Microsoft Intune – July

ScottSawyer's avatar
ScottSawyer
Icon for Microsoft rankMicrosoft
Jul 28, 2026

Ask an IT admin what a good day looks like, and it usually comes down to one word: control. Control means you push a change and know it landed. It means you have a clear view into your device fleet, from compliance status to sync health. That certainty is what helps IT stay ahead and deliver.

Still, endpoint management gets harder as fleets grow across locations and device types. More devices and policies rarely mean fewer admin hours. This month's updates focus on giving IT clearer visibility and more confident action.

Demystify Windows device sync status

When admins troubleshoot a device, they need visibility into what’s happening. The updated per-device sync experience in the Intune admin center now shows progress, making it easier for admins to confirm actions are running and understand where they are in the process.

The updated sync action also triggers both the mobile device management check-in and the Intune Management Extension (Windows only) check-in. One sync can now pull-down policy, app, and script changes in a single pass. For admins working through a single-device issue, this makes sync more transparent, more complete, and easier to trust as a troubleshooting step. Learn more about sync actions for Windows and how to use them to troubleshoot and validate device state.

 

Figure 1: The Sync status pane tracks each step live, from notifying the device to calculating compliance.

Want a deeper story about how we delivered this change? Read the blog about how Intune helps IT prioritize time-sensitive actions or catch the recent Microsoft Technical Takeoff video on Intune timing demystified.

Help ensure compliance for macOS

This month, custom compliance settings for macOS became generally available. Admins can use these settings to apply organization-specific requirements that built-in compliance settings don’t cover. This extended coverage helps reduce risk and unblock macOS deployments by aligning compliance and Conditional Access requirements with the Intune security policies organizations need to manage them. To learn more about compliance policies and what they do, see "Use compliance policies to set rules for devices you manage with Intune."

Additionally, using discovery scripts and JSON rules, admins can inspect many macOS device attributes and conditions. Think about installed software, running processes, app versions, or security posture that no Apple built-in setting captures. Now macOS devices report compliance the same way Windows and Linux devices do, giving you one consistent view instead of three different ones. Read more about how to set up the custom compliance settings documentation for Microsoft Intune.

More control over Samsung firmware updates

Keeping firmware current becomes harder as your mobile device fleet grows. For example, a new version may need testing against line-of-business apps before reaching production devices. In a Zero Trust environment, every unpatched device can become a compliance gap waiting to happen.

The Samsung Knox Enterprise Firmware-Over-The-Air (E-FOTA) integration brings precise control over firmware and OS updates across their Galaxy devices into the Microsoft Intune console. Existing Intune device groups determine which devices receive each version. If group membership changes, the firmware assignment follows.

Admins can keep production devices on their current version while testing an update. After validation, they can roll it out gradually during planned maintenance windows. Battery requirements and postponement limits provide more control over installation timing. This helps maintain consistent firmware and compliance across the fleet.

Intune: Myth vs. reality

Myth: Windows Autopilot requires device registration for new PCs.

Reality: Device registration is not required in all Windows Autopilot scenarios. Many IT admins associate Windows Autopilot with device registration because the original Windows Autopilot solution uses registration to identify devices. Today, organizations can choose from multiple Autopilot approaches depending on their deployment needs.

Windows Autopilot helps IT remotely provision devices at scale across a range of deployment scenarios, including existing devices, pre-provisioning, self-deploying deployments, and remote users.

Windows Autopilot device preparation helps streamline Windows 11 provisioning without requiring Windows Autopilot registration. It uses enrollment-time grouping to deliver selected apps and scripts during setup, with near real-time deployment reporting.

How to choose the right Autopilot approach: If you need registration-based deployment scenarios, such as pre-provisioning, self-deploying deployments, or existing device provisioning, use the original Windows Autopilot solution. Use Windows Autopilot device preparation when you want to streamline Windows 11 onboarding without Windows Autopilot registration and deliver selected apps and scripts during setup before users reach the desktop.

Windows Autopilot in action: Watch Microsoft MVP Jonathan Edwards walk through remote, at-scale onboarding with Intune. You will get a step-by-step look at both Windows Autopilot and Autopilot device preparation in action, along with guidance on choosing the right approach for your environment.

 

Keep the conversation going

Control rarely arrives as one big feature or capability. It shows up in the smaller updates admins lean on daily. A sync they can watch, a compliance rule they can shape, or a firmware update they can run with confidence. Together, these capabilities add more certainty and give time back. That is how modern endpoint management should work.

In that same spirit, staying in control means staying current as threat response speeds up. Read our recent post by Jason Roszak for practical guidance on building a patch strategy with Microsoft. Let us know in the comments what you think of these new capabilities and stay tuned for more next month.

 


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

Updated Jul 28, 2026
Version 3.0

9 Comments

  • MScommTime's avatar
    MScommTime
    Brass Contributor

    This is a helpful update. However, I wanted to raise a related issue with the Sync button functionality: it is only partially success when a device is on the login screen prior to a user logging in. That is, there's no user-authenticated session. I think one of the timed syncs (maybe at 8 hours) that is eventually fully successful, but the Sync button should be capable of that, even if it is the fallback functionality of it when it is not successful. Even Restart commands from Intune do not go through with the Sync button. The device is connected to the internet, connected to a power adapter, and is kept awake. I have an open MS Support case about why it was not successful on the login screen, but I suspect that either ScottSawyer​ or Iris_Yuning_Ye​ already knows the difference between how the timed events work compared to the Sync button.

    The new Sync Status shows this when I first press Sync:

    Rebooting from the login screen (or maybe pressing Sync again?) shows this:

    In case you're wondering about the use case, our automated offboarding steps apply a configuration profile targeting the device (not the user) which enables the "Exclude credential providers" policy so that the user is not able to log in with username - password/WHfB. This works fine. However, there are times when a user's employment contract is extended, but their account wasn’t properly updated. So, we need to re-enable their ability to log in. The steps to reverse this also target the device. However, the current process requires the user to keep the computer awake, and takes many hours for the device to fully sync, which results in downtime. It would be really helpful if the sync button was able to be fully successful while on the login screen.

  • MScommTime's avatar
    MScommTime
    Brass Contributor

    Deleting duplicate post. Apologies for any confusion.

  • RyanMSov's avatar
    RyanMSov
    Copper Contributor

    This doesn't seem to be working in my environment yet despite a ton of blogs around it. Any idea why I'm not seeing the new Sync experience? I have a mix of Hybrid and Cloud joined devices. 

    • AltimitWIll's avatar
      AltimitWIll
      Copper Contributor

      Click on Devices > Windows Devices. From there you should see in the top right of the screen Preview new device view and make sure it is turned on in order to see the preview.

       

  • Hi team, I have some questions

    1, Are multiple compliance discovery scripts executed each in its own isolated process/subshell, or are they sourced/evaluated within a shared shell context? (We need to know whether exit, readonly, or shared variable names across scripts can interfere with one another.)

    2, Where on the device is the discovery script staged and executed from during a compliance check-in? What is the working directory and the exact interpreter/invocation used?

    3, Which log contains the actual STDOUT/return value and failure reason for a compliance discovery script (as opposed to a Shell Script deployment)? Is the script's STDOUT/JSON output logged anywhere, or only pass/fail + PolicyID?

    4, Do macOS custom compliance discovery scripts run in root/system context or in the signed-in user's context?

    Thank you team!

    • Iris_Yuning_Ye's avatar
      Iris_Yuning_Ye
      Icon for Microsoft rankMicrosoft

      Hi TinTrungNguyen​ 

      1. Based on my understanding to your concern, since only one discovery script is allowed per compliance policy, and policies run sequentially in the agent's evaluation loop — so cross-script interference isn't a concern at the shell level.
      2. It should be under /Library/Intune/Scripts directory just like where other Intune agent scripts are run. The script is required to start with #!/bin/bash effectively does the equivalent of /bin/bash <staged_path> and captures STDOUT + exit code. We have detailed doc to discuss what format of script is required: custom compliance settings documentation for Microsoft Intune.
      3. Just like Windows and Linux that policy is deployed via Intune agent, the primary log is Intune agent log. And it's up to admin's discretion to make sure the scripts used are correct since we report the results of your scripts. 
      4. Since it's launched by the IntuneMdmAgent LaunchDaemon, it has same access with agent, full access to /Library, system config, MDM plists, etc.

      • TinTrungNguyen's avatar
        TinTrungNguyen
        Brass Contributor

        I have a new issue with this. Yesterday, the detection script ran and returned a status of RUNNING; however, today, the Company Portal is showing an error: 65007 (Script returned failure). After syncing, the device is still compliant, and the status in Compliance Settings is now 'Compliant'. In the known issues made by Microsoft, I belive that my script included return value. Could you please help me in checking this? Thank you!