deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-05-12 21:37:22 +00:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity

Merge pull request #10794 from tiaraquan/ap-updates-042125

Browse Source 
Added Feature Update option question and answer
This commit is contained in:
Tiara Quan 2025-04-21 12:18:44 -07:00 committed by GitHub
commit 79a5206671
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 13 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
windows/deployment/windows-autopatch/overview/windows-autopatch-faq.yml
View File

@ -4,7 +4,7 @@ metadata:
description: Answers to frequently asked questions about Windows Autopatch. description: Answers to frequently asked questions about Windows Autopatch.
ms.service: windows-client ms.service: windows-client
ms.topic: faq ms.topic: faq
ms.date: 04/11/2025 ms.date: 04/21/2025
audience: itpro audience: itpro
ms.localizationpriority: medium ms.localizationpriority: medium
manager: aaroncz manager: aaroncz
@ -97,6 +97,18 @@ sections:
- question: Can I configure when to move to the next ring or is it controlled by Windows Autopatch? - question: Can I configure when to move to the next ring or is it controlled by Windows Autopatch?
answer: | answer: |
You're in full control over when updates are deployed to their devices. Autopatch groups will recommend a set of intelligent defaults but those are fully customizable so that you can achieve your desired rollout. You're in full control over when updates are deployed to their devices. Autopatch groups will recommend a set of intelligent defaults but those are fully customizable so that you can achieve your desired rollout.
- question: What is the expected behavior for turning on the Feature Update option for Autopatch groups?
answer: |
Starting in April 2025, default policies aren't created for new Autopatch customers. Existing customers will continue to receive support until Windows 10 reaches its End-of-Service (EOS). However, these policies won't transition to Windows 11.
If you created an Autopatch group before April 2025:
- The Feature Update option is unselected by default.
- Selecting the Feature Update option creates a feature update policy for the newly created Autopatch group. This doesn't affect the Global DSS policy.
- The Feature Update option doesn't affect existing releases created before April 2025; these releases remain unchanged
If you created an Autopatch group after April 2025:
- Selecting the Feature Update option creates a feature update policy and assigns it to all its deployment rings.
- Global DSS policy isn't affected.
- name: Hotpatch updates - name: Hotpatch updates
questions: questions:
- question: What are the licensing requirements for hotpatch updates? - question: What are the licensing requirements for hotpatch updates?