Microsoft Intune service release 2611, published for the week of November 16, 2026, adds event-driven Android automation, Windows update windows, broader script targeting, faster macOS check-ins, configurable compliance intervals, new settings, protected apps, Google Workspace authentication expansion, and richer Windows Autopatch guidance.

For Intune administrators, the signal is clear: this release is about reducing deployment latency while tightening control over when automation, scripts, updates, and compliance checks run. Your team should review assignments and pilot the new controls before changing production baselines.

1. Android Enterprise Local Actions Automate Device Tasks

Microsoft’s release notes say Intune now supports local actions on Android Enterprise fully managed and dedicated devices. These actions run in response to device restarts, Managed Home Screen sign-in or sign-out, power connection changes, and scheduled times.

Each event can invoke up to five actions. Supported examples include launching an app activity, sending a broadcast intent, and signing out of Managed Home Screen.

Microsoft’s local-actions documentation identifies activity, broadcast, and direct API operations as supported action types. Activity and broadcast actions require explicit target packages; Microsoft also says an action fails silently when its target package is absent.

What you can control: Administrators can connect supported device events to local workflows on:

  • Fully managed devices: Corporate-owned Android Enterprise devices assigned for broad organizational use.
  • Dedicated devices: Corporate-owned endpoints used for kiosk, task, or shared-device scenarios.
  • Event responses: Automated tasks following restart, user-session, power, or schedule triggers.

Microsoft’s documentation says activity actions require Android overlay permission through OEMConfig. The relevant packages are com.microsoft.intune for the Intune app and, when Managed Home Screen is installed, com.microsoft.launcher.enterprise.

Why this matters: This is not remote scripting. It is device-side event automation for tightly managed Android endpoints. A missing target package or permission can produce a silent failure, so app deployment and OEMConfig prerequisites must precede the local-actions profile.

Admin action:

  1. Identify supported devices. Limit the initial assignment to fully managed or dedicated Android Enterprise test devices.
  2. Map each trigger. Define the required response to restart, sign-in, sign-out, power, or scheduled events.
  3. Validate target packages. Confirm every referenced application is installed before the local action runs.
  4. Configure permissions. Grant the required overlay permission through the appropriate OEMConfig policy when launching activities.
  5. Pilot all branches. Test success and failure conditions before assigning the profile broadly.

2. macOS Gains New Edge, Defender, and EWS Settings

Microsoft says the Intune settings catalog now includes additional controls for Exchange Web Services retirement alerts, Microsoft Edge browsing and Copilot experiences, and Microsoft Defender for Endpoint AI agent protection.

Under Declarative Device Management > Account > Account Settings, devices running macOS 27.2 and later gain Allow EWS Retirement Alerts.

The Microsoft Edge additions are extensive:

  • Copilot and feeds: Allow browsing with Copilot, Browsing with Copilot allowed URLs, Browsing with Copilot blocked URLs, Enable Copilot address bar suggestions, Allow Cowork to take actions on your behalf, Enable the Copilot new tab page, Configure Discover/Work feed tab visibility, and Set default Copilot new tab feed to Work or Discover.
  • Address bar and navigation: Enable clipboard suggestions in the address bar, Allow Back/Forward Cache for WebSockets, Enable standardized browser zoom behavior, and Show a warning before quitting.
  • Identity and profiles: Enforce Edge guest mode, Enable editing profile in settings, Allow M365 authentication popups in work profiles, and Enable Edge sign-in using non-Microsoft accounts.
  • Network controls: Allow sites to make network requests to the local device, Block sites from making network requests to the local device, Allow sites to make requests to local network endpoints, Block sites from making requests to local network endpoints, Allow Local Network Access in subframes without explicit delegation, and Override IP address space mappings.
  • Proxy and routing: Allow socket pool size randomization for proxies, Use KDC policy to delegate credentials, Set IPv4 route-probe address for PAC scripts, and Set IPv6 route-probe address for PAC scripts.
  • Permissions: Allow Local Fonts permission on specified sites, Block Local Fonts permission on specified sites, Default Local Fonts permission, Allow idle detection on specified sites, Block idle detection on specified sites, and Default idle detection permission.
  • Downloads and documents: Set default download directory, Enable service-based extraction for Reading Mode, and Allow specified sites to access file URLs in the PDF Viewer.
  • Runtime behavior: Enable opaque origins for data URLs in Web Workers, Enable strict MIME type checking for worker scripts, Enable extended lifetime for SharedWorkers, Force foreground priority for specific URLs, Force foreground priority for all tabs, and Background automatic relaunch when all browser windows are closed.
  • Browser capabilities: Enable saving passkeys to the password manager, Control Microsoft Edge Safe Hosting Extension, Make storage quota APIs return static values, Enable user web app installation from the browser, and Control availability of XSLT.

Microsoft Defender adds AI Agent Network Inspection and AI Agent Protection.

What this means: Intune can now express more of the macOS browser and AI control plane through the settings catalog. The settings span user experience, identity, local-network access, permissions, runtime behavior, and AI agent protection—not merely Copilot enablement.

Why this matters: Several settings can materially alter browser access to local devices, local network endpoints, file URLs, fonts, identity popups, and Copilot workflows. Treat them as security baseline changes rather than convenience preferences.

Admin action: Inventory existing Edge and Defender profiles, identify overlapping controls, and test the new settings against representative macOS devices before merging them into production baselines.


3. PowerShell Assignments Add Exclusions and Built-In Groups

Microsoft says Intune now supports group exclusions and the built-in All Users and All Devices groups for Windows PowerShell script assignments.

Administrators can assign a script broadly and then exclude selected groups. Microsoft’s PowerShell script documentation recommends the built-in groups instead of custom groups intended to represent every user or device.

What you can control: Script assignments can now use broad built-in targeting with explicit exceptions, bringing assignment behavior closer to other Intune workloads.

Why this matters: Broad script deployments previously required more fragmented group design when specific populations needed protection from the assignment. Exclusions make the exception visible in the workload itself.

This does not make a broadly assigned script low risk. It makes its scope easier to express.

Admin action:

  1. Review broad assignments. Identify scripts currently assigned through custom tenant-wide groups.
  2. Document exclusions. Record devices or users that must not receive each script.
  3. Pilot built-in targeting. Test All Devices or All Users with representative exclusion groups.
  4. Check overlap. Confirm that include and exclude group design produces the intended effective assignment.
  5. Monitor execution. Validate script results before retiring existing assignment structures.

4. Google Workspace Authentication Expands on Android

Microsoft says Intune can require users to authenticate with a managed Google Account from the organization’s Google Workspace domain on supported Android Enterprise devices. The policy does not change the Microsoft Entra account associated with the Intune-managed device.

The capability already covered corporate-owned, fully managed devices and corporate-owned devices with a work profile. Release 2611 extends it to personally owned devices with a work profile managed through the Android Management API.

What you can control: Set Require users to authenticate with a Google Workspace account to True in an Android Enterprise settings catalog policy. Microsoft says the policy can be assigned before enrollment or to devices that are already enrolled.

Prerequisites include a managed Google domain, a verified Google Workspace domain, and managed Google Accounts for targeted users.

Why this matters: Organizations using both Microsoft and Google identity systems can require an organizational Google account inside the managed Android context without replacing the device’s Microsoft Entra association.

Admin action: Coordinate with the Google Workspace team before assignment. Verify domain status and account provisioning, then test both pre-enrollment and existing-device behavior on personally owned work profiles.


5. macOS Agent Check-Ins Move to an Hourly Cadence

Microsoft says newly enrolled macOS devices now use an accelerated Intune management agent schedule. During onboarding, the agent checks every three minutes for 15 minutes, then every 15 minutes for two hours.

After enrollment, the regular cadence changes from approximately eight hours to one hour. Microsoft says the service-controlled schedule helps newly assigned apps, scripts, and dynamic-group updates reach devices sooner without administrator or user action.

1 hour Regular macOS Intune management agent check-in cadence Microsoft Intune release 2611 notes

What this means: The normal maximum waiting period between agent check-ins is materially reduced. Onboarding also receives a concentrated period of more frequent communication.

Why this matters: Faster delivery changes operational expectations. Help desks and deployment teams should no longer build routine macOS instructions around an approximately eight-hour agent cadence, although assignment processing and device connectivity can still affect when a change appears.

Admin action: Update macOS deployment runbooks and support scripts to reflect the new cadence. Monitor onboarding traffic and confirm that app and script dependencies arrive in the intended order.


6. Windows Maintenance Windows Control Update Timing

Microsoft says Intune now supports maintenance windows for Windows operating system and driver updates. Administrators can select which update operations run during a window and configure its start date, time, duration, and repeat schedule.

The profile path is Devices > Manage devices > Maintenance windows > Create profile.

What you can control:

  • Update scope: Choose which supported update operations run within the window.
  • Start point: Define the date and time for the maintenance period.
  • Duration: Set how long the window remains available.
  • Recurrence: Configure a repeating schedule for planned update activity.

Why this matters: This closes an operational gap between approving an update and controlling the period in which update work occurs. Maintenance windows should become part of change calendars for device groups that have defined service periods.

A maintenance window is not a substitute for update policy design. It is an execution boundary.

Admin action: Map maintenance-window profiles to existing update groups, confirm that the duration is sufficient for the selected operations, and test operating system and driver behavior separately before combining them.


7. Compliance Script Intervals Become Configurable

Microsoft says Intune administrators can configure evaluation frequency for custom compliance scripts on managed Windows and macOS devices.

Available intervals are 15 minutes, 30 minutes, or one to eight hours.

Custom compliance script evaluation choices

Evaluation intervalOperational use
15 minutesFaster detection for higher-priority compliance conditions
30 minutesResponsive checking with less frequent execution
One to eight hoursLower-frequency checks for less time-sensitive conditions

What this means: Your team can align each custom compliance check with its required detection speed instead of accepting a single cadence for every script.

Why this matters: A shorter interval increases compliance responsiveness but also repeats script execution more often. The correct interval depends on the importance and execution cost of the check.

Admin action: Classify scripts by risk and resource demand. Pilot shorter intervals on a limited device group, then measure device behavior before assigning them tenant-wide.


8. Windows Autopatch Reports Add Remediation Guidance

Microsoft says Windows Autopatch now provides additional reporting data, remediation guidance, and guardrails for configuration issues.

Administrators can use the expanded information to identify configurations requiring attention and determine an appropriate next step.

What this means: Autopatch reporting is moving beyond issue visibility toward guided operational response. Microsoft’s release notes do not enumerate the individual report fields or guardrails, so administrators should validate the changes directly in their tenant.

Why this matters: More guidance can shorten triage, but it does not remove the need to review the affected configuration and its assignment scope before remediation.

Admin action: Add the expanded Autopatch reports to routine update reviews. Compare each recommendation against current maintenance windows, update assignments, and exception groups before applying changes.


9. Ten Protected Apps Join the Intune Catalog

Microsoft lists 10 protected app entries in service release 2611. Platform availability varies by application:

  • EnGlobe Mobile: Corporatek Inc., iOS.
  • Everbridge 360: Everbridge, Inc., iOS and Android.
  • Hypergate Files for Intune: Hypergate, Android.
  • Newcode: Newcode.ai, iOS.
  • Ramp: Ramp Business Corporation, iOS.
  • Reliaquest GreyMatter: Reliaquest, iOS and Android.
  • Rogo AI: Rogo Technologies, Inc., iOS.
  • Rogo AI Intune Wrapped: Rogo Technologies, Inc., iOS.
  • ShareCRM: FORSHARE PTE. LTD., iOS and Android.
  • Zoho Mail - Intune: Zoho Corporation, iOS and Android.

What you can control: These entries can now be considered when designing Intune app protection coverage for their listed platforms.

Why this matters: A protected-app listing enables policy work, but it does not prove that an existing policy is automatically assigned or that each app behaves identically under the same controls. The separate Rogo AI and Rogo AI Intune Wrapped entries also require administrators to select the intended application variant.

Admin action: Confirm the exact app and platform used by your organization, add it to a pilot app protection assignment, and test access and data-transfer behavior before production rollout.

The Bigger Picture

  1. Treat Android local actions as workflow code. Package availability, permissions, triggers, and action order all require controlled testing.
  2. Revisit deployment timing assumptions. Hourly macOS check-ins and configurable compliance intervals change how quickly administrators can expect state to converge.
  3. Connect maintenance windows to change governance. Windows update timing should align with documented service periods and exception handling.
  4. Reduce assignment sprawl. Built-in PowerShell targeting with exclusions can simplify broad deployment structures without weakening scope controls.
  5. Review AI controls as security settings. The new Edge and Defender catalog entries govern network, identity, browser, Copilot, and AI agent behavior.

Stay tuned for more Intune updates, and as always, test thoroughly before deploying to production!