We'd like to stagger Windows Feature Updates in a ring over a 6-month period, somewhat similar to how consumer devices update.

Our goal is that over these 6 months, machines will randomly start to download and perform the feature update, rather than the entire group getting the policy at once.

The reason being, when you have 15,000 endpoints, you can't have 5000+ devices begin the download of the feature update at once. Ultimately we don't care what order they go in, but we don't want to manage groups, and Dynamic Groups in InTune is still very limiting.

Currently enrolling a device in Intune completely blocks the ability to install an Optional Windows Update (e.g. KB4541335) on the given device. While often not installing these optional updates is fine, there are times when they may be necessary. Allowing control over these updates would be helpful.

Until a device registers with the MSFT Update service for the Feature Update Rings (Preview), we run the risk of Autopilot devices updating to the latest Feature Update even if the ring is frozen at a previous Feature Update build. I assume this is because the regular update rings must be set to 0 for the Feature Updates and the device can request that feature update before being fully registered. Would be great to have this working otherwise the Feature Update rings cannot be successfully relied upon for Autopilot devices.

Today I can see that the latest update proposed in Windows update for business is 18363.720 because it is a mandatory update

18363.752 released a week before is not proposed because it is an optional update

please add an option to allow optional updates to be proposed in windows update for business through Intune software update rings.

Thank you

We are using Windows Update for Business (WUfB) in our environment including driver updates. Problem: Driverupdates are distributed outside from the Microsoft patchdays so our endusers geting too much update messages to reboot the computer. Idea: Implement please a Group Policy to configure when driver updates are distributed to the clients.

An option should be available for newly enrolled devices to install all updates, (temporarily bypassing defined update rings)

Keeping Windows endpoints up to date is critical.
The current infrastructure with using Azure Logs / Windows Update Solution is just ugly, and not intuitive.

I'd like to have WSUS-like functionality in Intune - at least from a reporting side of things. I want to see which updates are needed where. Which computer hasn't installed updates in some time, etc.

When using Intune Windows Update Feature it does not provide real-time information on
1.What version of Windows it is on?
2.Update from 1809 to 1909 does not update on the portal. And makes it difficult to identify if you deployment is successful or not.

Hello,
Please allow pausing specific KB quality updates.

I'd like to be able to put my Windows 10 machines enrolled in Intune on an annual update channel that updates machines to the xx09 update that comes out in the fall. Since that update has a much longer support cycle, I'd like to be able to set my machines to automatically take advantage of that cycle and update only once a year within Windows Update for Business.

add option to import a custom software update catalog to allow 3rd party updates to be deployed to managed devices. integration with already existing CAB files from Dell, Adobe, PatchMyPc or internal developed catalog (via SCCM/SCUP) would be ideal

We want our customers to have a notice of the time an update will take. For instance if its a big update that they should consider updating in after hours, at home.

Using Intune Update rings (WUfB), it would be helpful to allow a duplicate or copy/paste option for an update ring. If I want to create a phased approach to deployments I need to currently open 2 tabs so I can copy from one to the other manually and I only want to change one or two values for a different assignment group. This adds scope for error.

Is there a way that you can choose which feature update can be installed via WUFB

We would love to use the new InTune but can't because we would lose control over what specific updates are sent to our systems. The ability to control deployed updates on a granular level is critical to our business, without that, we will not be switching to the new InTune. If it was a feature in legacy InTune, why is it not in the new version? That's beyond me.

Have the ability to trigger a software update check (scan and deploy) as an on-demand action from the device blade. Currently the option to sync settings or trigger various Windows Defender actions are available but not to trigger an update. This would be useful for an admin to force clients to check in to Windows/Microsoft update and enforce any updates outside of maintenance windows.

When creating Windows 10 Update rings in the Intune portal UI you also have to define the active hours which are then enforced at the client. So as result the users are not able to define the "real" maintenance hours reflecting their needs by themselves.
So instead of having to create dozens of update rings respecting the needs of different maintenance windows (active hours) it should be possible to NOT enforce Active Hours in the Intune portal.

Here's an idea: Let users pick their preferred update ring themselves. This way the user is in control of how soon the quality and feature updates are rolled out to their devices.