Event banner
Event details
Is there a way to get driver and firmware update reports for multiple policies?
this would avoid back and forth to get exported data for multiple devices.
Thks- Ryan_Williams
Microsoft
The existing Intune driver report provides a per-driver view, showing the status of each applicable device across all your policies where the driver has been offered. This allows you to see device update status without needing to pull data separately for each policy.
For more details, see: Windows Update reports for Microsoft Intune | Microsoft Learn
thank you, but I meant if we have let's say 5 different policies. Each targeting different drivers, because it's hard to know which drivers apply to which device and we want to have the installation status for all 5 policies at the same time (contrary to having to select each policy and ask for status update)
Hi, is there a way to see which driver apply to which devices without the need to go to the Windows Update catalog? This would greatly reduce the need for groups per device models
Thks- Ryan_Williams
Identifying which devices and models are targeted by a driver update is one of the most requested improvements for driver management.
Today, you can retrieve a list of applicable Microsoft Entra IDs for each driver update in a policy through the Graph API. We're investigating ways to surface this information directly in the management experience to make it more accessible.
Hi,
Is it still planned to have an option to auto align with Cumulative deployment ring configuration to avoid multiple reboots?
thks- Ryan_Williams
Could you provide more context about the experience you're asking about? I'm not sure what you mean by "Cumulative deployment ring configuration".
Just saw that you've answered this question by answering another of my questions mentioning that drivers also respect deferrals and deadline.
thks
Hi, when will the new interface that was shown during the driver demo be available in production tenants? For the align with patch Tuesday deployment/rings, is there only the option to set a specific date (if so, how should we calculate the date (end of deferal or end of grace period) to avoid multiple reboots?
Thks- Ryan_Williams
The interface shown in the demo is part of the existing Windows Autopatch experience and has been available since September of last year. This experience is used to manage drivers across your Autopatch group policies, providing a streamlined way to oversee driver updates.
Driver updates are categorized as quality updates and follow the same deferral and deadline settings. To align driver updates with Patch Tuesday deployments and avoid multiple reboots, the goal is for both the driver and quality updates to be offered in the same scan. We recommend approving the driver update so that it becomes available at the end of the deferral period.
thank you for confirming that they follow the same deferral and deadline settings. I did not know they did.
As for the UI experience, we have a slighty different UI than what was shown in the demo. We don't see the Manage drivers for Autopatch group
That's why I asked, because I thought it was a new upcoming UI change.
Do you recommend that we create a support ticket to see why it's not showing?
thks
The demo for drivers management was interesting, but focused on manual management. With Windows Autopatch, is it possible to automatically approve all drivers installation for Ring0 (i.e. labs devices), while having some gating before drivers become available to other rings?
It looks like managing drivers manually is a lot of overhead, and requires manual assignment to groups. How are we notified of new drivers being available in Windows Autopatch, so that we can proceed with assignments?
Finally, I feel that the naming convention for drivers is pretty vague. "Intel - Extension - %version%" -- how are we supposed to identify to which equipment and/or computer models such a driver targets? That is especially true when we identify a specific driver causing issue, i.e. using the local Computer Management MMC -- how can we resolve the name/version of a driver in the MMC versus the name/version being displayed in Windows Autopatch?
- Ryan_Williams
This session focused on advanced capabilities for when you need more control. If you’re looking for more details on the common driver management scenario with automatic policies, check out our other session here: aka.ms/UpdateHarmony.
Currently, there isn't a way to automatically approve drivers listed under the Other Drivers tab. This isn’t a request we’ve heard frequently, but we’d love to better understand your needs. If this is something that would benefit your workflow, please private message me with details on your use case.
To help with driver awareness, the Drivers to Review column in the Driver Updates tab shows how many recommended drivers are in the 'Needs Review' state, meaning no admin action has been taken yet (Approve, Pause, or Decline).
Regarding driver naming conventions, changing the name format to include more details isn’t straightforward since drivers often target multiple device models (CHIDs) and hardware components (HWIDs). However, we’re actively exploring ways to provide more context, including which of your devices (by model) are impacted and details on which component within the device a driver will affect. These are two of the most requested improvements for driver management, and we’re investigating solutions to enhance this experience.
Is autopatch available for EDU such as A3 and A5 licenses?
- Ryan_Williams
Windows Autopatch requires an E3+ or F3 license. To stay up to date with the latest requirements, see Prerequisites | Microsoft Learn.
This is a scenario we're investigating. If you're interested in shaping the future of Autopatch, consider joining the Microsoft Management Customer Connection Program for early preview opportunities.
- Heather_Poulsen
Community Manager
Thanks for joining today’s session on “Windows Autopatch: Your playbook for advanced update management” at Microsoft Technical Takeoff. Q&A will remain open through Friday so keep your comments and questions coming! Up next: Unified security: Intune + Microsoft Defender for Endpoint
Here are the resources we mentioned in today’s session:
- Microsoft Edge Updates: Rollback guidance - Microsoft Edge rollback for enterprises
I am more concerned about Dynamic Device Assignment. it makes more work to add manually device to correct RING.
- Ryan_Williams
With Autopatch Groups, you have the flexibility to either use Dynamic Device Assignment or manually assign devices to rings via Entra groups.
Could you share more details on the challenges you're facing with Dynamic Device Assignment? This is an area we're exploring for improvements, and your feedback would help us enhance the experience.
So this was challenge I was talking about. Support you have 10000 Devices. and it took 90% devices in Broad Ring, But I want Some device in pilot groups as I have approx. 30 devices to add in Test Group.
Now, as a solution I was wondering if I have autopatch feature where in I can add More Dynamic queries where we deicede which devices move to which RING.
example: 30 Device Contains DevTest naming Convention, No I wanted to keep in 2 wave. So if I would have option on Autopatch where i can use for device assigment.
In Result Each Office, Edge, Windows, driver update will go accordingly. I don't have play with each Autopatch group.
Been using Autopatch for managing updates in our tenant, but have concerns with how it handles Feature updates. Have some clients that upgraded to 24H2 when its not specified in Autopatch. Confirmed from Autopatch support team everything is configured correctly, yet no answer for why this is occuring.
- Ryan_Williams
Thanks for your feedback! Please send me a private message with the details, and we’ll work to get this resolved.
- Heather_Poulsen
Welcome to “Windows Autopatch: Your playbook for advanced update management” at Microsoft Technical Takeoff. Q&A is open now and throughout the week. Please post any questions or feedback here in the Comments.
