Event banner
Windows Autopatch: Simplifying the update management story
Event details
So, WUfB will now be under the AutoPatch tab/blade, even if our tenant is not enrolled in AutoPatch?
- Harman_ThindNov 27, 2023
Microsoft
Hi all, AriaUpdated is correct that there is no change right now.
However, when the unified product goes live, then there will be a change to the admin experience. All update experiences will live under a single node in Microsoft Intune, that being Devices -> Windows Autopatch. Here is where you will find the experience for Update rings for Windows 10 and later, Feature Update, Quality Update, and Driver Update policies. See the image below for reference.
Reports will of course live under the Windows Autopatch section under reports.
Depending on your licensing, you will have access to specific features within this new unified Windows Autopatch portal, as discussed in the session. For applicable licenses, there are optional opt in only features.
- EricOhlinNov 27, 2023Iron Contributor
Hey Harman_Thind, Thank you for clarifying. My question was in reference to when the product being shown goes live, not the console at this exact moment.
So, my original question/theory is true? "WUfB will now be under the AutoPatch tab/blade, even if our tenant is not enrolled in AutoPatch?"
This seems confusing. Everything under AutoPatch, even if we're not enrolled in the AutoPatch service? Why? Jere said it best... "There's gonna be many confused admins after this. 1 more not needed name change, IMO."
FYI
- Harman_ThindNov 28, 2023
Microsoft
Yes, understood. All customers (WUfB and WUFB-DS included) will become Windows Autopatch customers. Unlike today for existing Windows Autopatch customers, we will not require a full tenant enrollment process. This is all part of simplifying update management so that customers don't need to figure out which product to use between WUfB, WUfB-DS or Windows Autopatch. In the new unified UX, depending on the licensing an organization holds, will determine how many features in the Windows Autopatch portal they will have access to, while ensuring that we aren't taking away any functionality and the experience is just under a new brand. We will make it extremely clear what features a tenant has access to depending on the licenses they hold, this will be clearly shown in the UX and documented in public docs.
To give you an example, current WUfB-DS customers that hold E3/E5 or F3 licenses that have not enrolled in Autopatch today, will have the same experience as they do today and can opt-in to additional optional features that are shown in the new unified experience. I.e. They will have access to all the features they have today with WUfB-DS, with the option to opt into features like Autopatch groups. Check out the photo below for an idea of some additional features that will be accessible with the right licensing.
Let me know if any further clarifications can be made! Appreciate the feedback from this group.
- JereSepNov 27, 2023Copper Contributor
There's gonna be many confused admins after this. 1 more not needed name change, IMO.
Edit. Now I'm more confused after reading Aria's comment. 😄
- AriaUpdatedNov 27, 2023
Microsoft
Right now the blades in Intune will not be moved. So if you're using the Update Rings Page / Feature Update Deployments page, then you can continue to use those. They are not moving at this time. 🙂- EricOhlinNov 27, 2023Iron Contributor
Hey AriaUpdated , thanks for the response. So, what is this console blade view? Does this only activate if your tenant is enrolled in AutoPatch? Thanks!
- Christopher HolschuhNov 27, 2023Copper ContributorThanks, was wondering the same thing.