Windows 10: How to configure RBAC for Windows Autopatch

WinClub · Jun 20, 2025 at 4:52 PM

If you are an IT admin and want to create a setup to manage access permissions to Windows Autopatch resources effectively, try using RBAC or Role-Based Access Control. You can give permission to users, allowing them to control devices to manage Windows Updates. In this post, we will see how you can configure RBAC for Windows Autopath and talk about […]

This article How to configure RBAC for Windows Autopatch first appeared on TheWindowsClub.com.

read more...

Brink · Jun 20, 2025 at 4:55 PM

Windows Autopatch now available for public preview

Windows Autopatch is now available for public preview! This post will take you through the steps to join the public preview and offer a quick primer to familiarize you with the service. What Is Windows Autopatch? Windows Autopatch is a new service that automates the process of managing and rolling out updates for Windows and Microsoft 365 apps. If you missed the announcement, beginning in early July 2022, this service will be generally available if you have a Windows Enterprise E3 license or greater. The takeaway if you're an IT admin? You can continue using the tools and processes you're accustomed to for managing and deploying updates—or you can take a hands-off approach and let Windows Autopatch do it for you. For more information, see Get current and stay current with Windows Autopatch and the Windows Autopatch FAQ. Why join the public preview? Changing the way things get done, even when that change makes things easier, gives pause to most people who run large IT organizations. By joining the public preview, you'll be able to get comfortable with Windows Autopatch and ready your organization to take advantage of the service at scale. Are you Windows Autopatch-ready? Prerequisites

Licensing: Windows Autopatch is available at no extra cost to Windows Enterprise E3 and above license holders.

Specifications: Windows Autopatch works with Windows 10 and 11 Enterprise versions and, when we reach general availability, on virtual machines including Windows 365 Cloud PCs.

Hardware requirements: If your corporate-owned devices are running a current. supported version of Windows 10 or Windows 11, they can be enrolled in Windows Autopatch. Bring-your-own-device (BYOD) scenarios are not currently supported.

Management requirements: Your devices must be managed with either Microsoft Intune or via Configuration Manager co-management.

Identity requirements: User accounts must be managed by Azure Active Directory or Hybrid Azure Active Directory Join.

For granular details and prerequisites for licensing and connectivity, see Windows Autopatch prerequisites. What is Windows Autopatch patching? Windows Autopatch applies updates to your Windows operating system and configures automatic updates for Office applications. Windows updates The General Availability Channel is the source for Windows updates through Windows Autopatch. Polices for quality and feature updates can be set independently to meet your needs. Admins will be able to see what updates have been applied through the Windows Autopatch message center in Endpoint Manager and will learn about what updates to expect. The familiar cadence of monthly Windows security and quality updates, also referred to as "B" releases, will continue and out-of-band updates will be applied as needed. Office updates Windows Autopatch uses the Monthly Enterprise Channel to balance stability and feature availability. These updates are also released on the second Tuesday of the month. Office rollouts follow a unique, fixed schedule-they do not make use of ring-based progressive deployment and are not controlled by Autopatch. Microsoft Teams and Microsoft Edge updates The Microsoft Teams client application is synchronized with changes to the Teams online service. As a result, updates to this client occur on a different cadence than general Windows or Office updates. Microsoft Edge also has its own update channel to facilitate frequent revisions to the browser. Windows Autopatch progressive deployment is not used for either Teams or Edge updates, nor do the pause or rollback actions apply to either application. However, support issues for these app can be raised via the Windows Autopatch support request portal. For more details on Teams updates, see our documentation on the Teams update process. See more details about Windows Autopatch and Edge, including configuring IE mode for Edge, see Plan your deployment of Microsoft Edge. Windows Autopatch activation This video walks you through the steps to enroll your tenant in the Windows Autopatch public preview and add your devices. Briefly the steps are:

Log in to Endpoint Manager as a Global Administrator and find the Windows Autopatch blade under the Tenant Administration menu. If you don't see 'Windows Autopatch' you don't have the right licenses. See Windows Autopatch prerequisites for more information on prerequisites, including licensing.

Use an InPrivate or Incognito browser window to redeem your public preview code.

Run the readiness assessment, add your admin contact, and add devices.

To guide you through common enrollment tasks, we have created three additional video tutorials:

How to add devices to your test ring

How to resolve a status of "tenant not ready"

How to resolve a status of "device not ready" or "device not registered"

Want even more details? Read a thorough how-to that explains the 'what' and 'why' as well as the 'how' for Windows Autopatch, see Enroll your tenant. Have questions about Windows Autopatch? Join our Windows Autopatch Ask Microsoft Anything (AMA) event on June 15th at 8:00 a.m. Pacific Time with members of the Windows Autopatch engineering team. Save the date and start posting your questions at https://aka.ms/AMA/WindowsAutopatch. You can also join the conversation, ask questions, or share insights anytime on the new Windows Autopatch Community: https://aka.ms/Community/WindowsAutopatch. What happens when Windows Autopatch reaches general availability? Once the service reaches general availability, you will be able to keep using the service as you have been. There may be some cosmetic changes to the interface, but your enrolled devices will stay enrolled, and you'll be able to expand your enrollment when you're ready. To stay on top of the latest be sure to follow the Windows IT Pro Blog.
Click to expand...

Source: https://techcommunity.microsoft.com/...w/ba-p/3439912

Brink · Jun 20, 2025 at 4:55 PM

What is new in Windows Autopatch: February 2024

The start of the new year brings a great opportunity for positive change, including the release of new features in Windows Autopatch. We heard your feedback! Here are some improvements made in response to your enterprise needs. Import Update rings for Windows 10 and later in preview Update rings allow you to specify how and when Windows as a service updates your Windows 10 or Windows 11 device with feature and quality updates. Update rings are available for Windows 10 and later. And if you’re a Windows Autopatch customer, you can now bring existing Update rings for Windows 10 and later policies into Windows Autopatch Management. For additional information, see Configure Update rings for Windows 10 and later policy in Intune. Importing existing rings allows you to take advantage of the many capabilities of Windows Autopatch without impacting your existing Windows update schedules. Imported rings will automatically register all targeted devices into Windows Autopatch without the need to redeploy or change your existing update rings. Additionally, important rings will be reflected in the reporting and release experience. Learn how to import update rings for Windows 10 and later. If needed, brush up on Windows client updates, channels, and tools. Customer defined service outcomes in preview Have you used Windows Autopatch reports to monitor the health and activity of your deployments? The insights from the reports can help you understand if your devices are maintaining update compliance targets. Previously, deployment success measures were based on a static schedule of 21 days. This means that Windows Autopatch aims to keep at least 95% of eligible devices on the latest Windows quality update 21 days after release. With this enhancement, the success of Windows Autopatch deployments will be based on your defined rings. We’ll also be introducing new columns in our release blade, as well as Windows quality and feature update reporting, to show the percentage complete for quality and feature updates. Devices that are up to date will remain in the “In Progress” status in reporting until you either get the current monthly cumulative update or an alert. If an alert is received, the status will change to “Not up to date.” To learn more, read Service level objectives. Improved data refresh speed and reporting accuracy Windows Autopatch reporting provides rich insights into your patch compliance status, so you can make informed choices about protecting against defects and vulnerabilities. This release is changing the refresh cycle for Windows Autopatch reporting. The refresh cycle refers to the amount of time from when a change is made to when it’s reflected in reporting and other UX components. This time will be reduced from every 24 hours to every 30 minutes. This improvement supports the many data streams that Windows Autopatch uses to provide current update status for all devices enrolled into Windows Autopatch. To learn more, see Windows quality update reporting. Take your next step with Windows Autopatch We hope these enhancements will help you keep your devices secure and up to date with less hassle and more control. Get current and stay current with automation that leads to higher security and lower costs. The ideas behind these releases originated from conversations, input, and requests from you, our customers. We'd love to hear your feedback and suggestions on how we can continue to make Windows Autopatch even better for you. You can share your thoughts and ideas with us on our feedback hub or by joining our community forum. If you want to learn more about Windows Autopatch:

Visit our website.

Read our documentation.

Watch our guided demos.

If you want to try Windows Autopatch for yourself, sign up for a free trial or contact us for a demo. Thank you for choosing Windows Autopatch and stay tuned for more updates and announcements.
Click to expand...

Source: https://techcommunity.microsoft.com/...4/ba-p/4056151

Solaris17 · Jun 20, 2025 at 4:55 PM

is there any demand for a system configurator?

http://www.techpowerup.com/configurator/

suggestions how to make cpu selection easy?
Click to expand...

Processor(V) <--drop down arrow
-AMD(V)
--Socket(V)
---AM2(V)
----List of cpu's
---939(V)
----List of CPU's
-Intel(V)
--Socket(V)
---775(V)
----List of cpu's
---771(V)
----List of CPU's

etc etc.

Windows 10: How to configure RBAC for Windows Autopatch

How to configure RBAC for Windows Autopatch

How to configure RBAC for Windows Autopatch

How to configure RBAC for Windows Autopatch

How to configure RBAC for Windows Autopatch - Similar Threads - configure RBAC Autopatch

KB5043145 - Autopatch

KB5043145 - Autopatch

Does windows autopatch support in business premium.

Does windows autopatch support in business premium.

Does windows autopatch support in business premium.

Windows Autopatch Overview

RBAC or limited access for Hyper-V on Windows 10 in Domain

how to configure Bluetooth?

how to configure windows updates