Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
To manage Microsoft Edge updates with Windows Autopatch, enable Microsoft Edge updates in each applicable Autopatch group in the Microsoft Intune admin center. Autopatch then creates group- and ring-specific policies. Confirm the option is selected and the policies exist; successful installation still depends on device eligibility, network access, policy compatibility, and restarting Edge.
How Windows Autopatch manages Edge updates
Autopatch manages Edge through update settings on Autopatch groups. The update types selected for a group determine which policies the service creates. Microsoft says the Autopatch Edge flow uses the Stable channel for ordinary eligible devices. The separate Test device group receives feature updates from Beta; that behavior should not be assumed for every group. See Microsoft’s Windows Autopatch Edge guide.
Microsoft describes Autopatch groups as a way to organize safer rollouts and automate the creation of multiple policies. Alternatively, administrators can configure and assign Edge Update policies directly, taking responsibility for their configuration and assignments.
| Approach | Policy ownership | Rollout organization | When it fits |
|---|---|---|---|
| Autopatch groups | Autopatch creates policies from group settings. | Uses group and ring structure. | Useful when you want the service to automate policy creation and organize rollout. |
| Direct Edge Update policies | Administrators configure and assign policies themselves. | Administrators manage assignments and rollout structure. | Useful when you need custom policy assignments and can manage them directly. |
How to turn on Edge updates for an Autopatch group
- Open the Microsoft Intune admin center and go to Tenant Administration > Windows Autopatch > Autopatch groups.
- Select the Autopatch group to configure and edit Update types.
- Select Microsoft Edge updates, then proceed through the group’s deployment settings and release schedules.
- Review the configuration and save it.
- Repeat these steps for every group that should receive Edge updates. The selection is group-specific, so enabling it for one group does not establish that it is enabled for others.
The group’s selected Microsoft Edge updates option is the main confirmation that Edge is included in its Autopatch configuration.
#1 Best Overall
- Instantly productive. Simpler, more intuitive UI and effortless navigation. New features like snap layouts help you manage multiple tasks with ease.
- Smarter collaboration. Have effective online meetings. Share content and mute/unmute right from the taskbar (1) Stay focused with intelligent noise cancelling and background blur.(2)
- Reassuringly consistent. Have confidence that your applications will work. Familiar deployment and update tools. Accelerate adoption with expanded deployment policies.
- Powerful security. Safeguard data and access anywhere with hardware-based isolation, encryption, and malware protection built in.
What devices need before updates can complete
Devices must be enrolled in Intune before registration with Autopatch. They also need to meet Microsoft’s current tenant- and device-dependent identity and licensing prerequisites and connect to the required Microsoft service endpoints. Check the current Windows Autopatch prerequisites rather than relying on a static eligibility checklist.
- Device availability: The device needs to be powered on and online for update checks and delivery.
- Network access: Firewalls and proxies must allow the required endpoints. Use Microsoft’s current Windows Autopatch network requirements and its dedicated Edge endpoint allowlist; endpoint requirements can change.
- No conflicting configuration: Existing Edge policies can conflict with Autopatch-managed settings. Review the effective configuration and policy assignments.
- Edge restart: If Edge is open, it may need to be restarted for an update to finish applying.
- Co-management workload routing: For co-managed devices, the Windows Update and Device configuration workloads need to be directed to Intune or Pilot Intune, as applicable.
How to verify Autopatch created the Edge policies
- In the Intune admin center, check that Microsoft Edge updates is selected in the intended group’s update types.
- Go to Devices > Manage devices > Configuration > Policies.
- Look for policies named in this format:
Windows Autopatch Microsoft Edge Update Policy - <group name> - <ring name>. The group and ring names identify the configuration the policy belongs to. - Inspect existing Edge channel profiles and customized policies before removing or changing anything. Microsoft advises removing old default Edge channel profiles when applicable to avoid conflicts, but says customized policies may be retained to avoid disruption. Confirm what is assigned in your tenant before deleting a profile.
Finding the expected policy confirms policy creation; it does not, by itself, prove every device has received or completed the update. Verify device connectivity, policy assignment and status, and whether Edge has been restarted.
Rank #2
- STREAMLIMED AND INTUITIVE UI | Intelligent desktop | Personalize your experience for simpler efficiency | Powerful security built-in and enabled.
- JOIN YOUR BUSINESS OR SCHOOL DOMAIN for easy access to network files, servers, and printers.
- OEM IS TO BE INSTALLED ON A NEW PC WITH NO PRIOR VERSION of Windows installed and cannot be transferred to another machine.
- OEM DOES NOT PROVIDE PRODUCT SUPPORT | To acquire product with Microsoft support, obtain the full packaged “Retail” version.
What update timing to expect
Microsoft’s Edge-specific Autopatch guide, last updated March 31, 2025, documents the following behavior:
- Edge checks for updates every 10 hours.
- Quality updates are weekly by default.
- Stable feature updates are progressively rolled out approximately every four weeks and become available within a few days of initial release.
- Microsoft’s Edge product group can accelerate rollout for browser updates containing critical security fixes.
These are documented service behaviors, not a guarantee that every device will install an update at a particular time. Eligibility, connectivity, policy conflicts, and an open Edge session that has not restarted can all affect completion.
Rank #3
- WINDOWS 11 PRO FOR WORKSTATIONS is for people with advanced needs such as data scientists, CAD professionals, researchers, media production teams, graphic designers, and animators.
- WINDOWS 11 PRO FOR WORKSTATIONS helps power through advanced workloads while providing server-grade data protection and performance, and includes all the features of Windows 11 Pro | Users will benefit from greater speed with faster processing and file transfers, greater resilience with server-grade storage, and the full power of high-performance hardware configurations.
- OEM IS TO BE INSTALLED ON A NEW PC with no prior version of Windows installed and cannot be transferred to another machine | Windows 11 Pro for Workstations is required licensing for systems with Intel Xeon or AMD Opteron processors.
- OEM DOES NOT PROVIDE SUPPORT | To acquire product with Microsoft support, obtain the full packaged “Retail” version.
Can you pause Edge updates in Windows Autopatch?
No. Microsoft’s Edge-specific Autopatch documentation states: “Currently, Windows Autopatch can’t pause or resume Microsoft Edge updates.” Do not treat Windows quality or feature update pause controls as Edge controls; the Edge guide says the service cannot currently pause or resume these browser updates.
Microsoft’s separate Edge Update policy reference documents policy choices including Always allow updates (1) (Recommended), manual updates only, automatic silent updates only, and updates disabled. These are general Edge Update policy settings, not the Autopatch group checkbox. If updates are disabled, Microsoft says administrators should periodically check for and distribute updates themselves. Review policy ownership and precedence carefully so a customer-managed policy does not conflict with the Autopatch configuration.
Rank #4
- MICROSOFT WINDOWS 11 PRO (INGLES) FPP 64-BIT ENG INTL USB FLASH DRIVE
Troubleshoot an Edge update that has not completed
- Confirm group inclusion: Check that the device belongs to the intended group and that Microsoft Edge updates is selected there.
- Check policy creation and assignment: Look under Devices > Manage devices > Configuration > Policies for the expected group- and ring-named policy, then review existing or customized Edge policies for conflicts.
- Check the device and network: Make sure it is powered on, online, and able to reach the required Microsoft and Edge update endpoints.
- Restart Edge: Close and reopen the browser if it was running during the update.
- Allow for rollout: A documented rollout cadence is not a device-specific installation deadline. Progressive availability and the device conditions above can affect when completion occurs.
If the configuration and device conditions look correct but the issue persists, consult Microsoft’s Windows Autopatch FAQ. Microsoft’s Edge guide directs eligible customers to submit a support request; access depends on E3+ or F licenses, so verify current licensing and support eligibility.
Quick Recap
Best Value
- Windows 11Pro for Workstations
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
