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

Merge pull request #10733 from MicrosoftDocs/main
Some checks failed
(Scheduled) Stale branch removal / stale-branch (push) Has been cancelled
Details

Browse Source 
Publish main to live, 03/31/25, 3:30 PM PDT
This commit is contained in:
Ruchika Mittal 2025-04-01 04:26:14 +05:30 committed by GitHub
commit 176e331436
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
3 changed files with 7 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
.github/workflows/StaleBranch.yml vendored
View File

@ -5,9 +5,9 @@ permissions:
on: on:
schedule: schedule:
- cron: "0 */12 * * *" - cron: "0 9 1 * *"
workflow_dispatch: # workflow_dispatch:
jobs: jobs:
@ -21,6 +21,6 @@ jobs:
"ExampleBranch1", "ExampleBranch1",
"ExampleBranch2" "ExampleBranch2"
]' ]'
ReportOnly: true ReportOnly: false
secrets: secrets:
AccessToken: ${{ secrets.GITHUB_TOKEN }} AccessToken: ${{ secrets.GITHUB_TOKEN }}

2
windows/deployment/windows-autopatch/manage/windows-autopatch-windows-feature-update-overview.md
View File

@ -133,7 +133,7 @@ The following table is an example of the Windows feature update policies that we
## Pause and resume a release ## Pause and resume a release
> [!IMPORTANT] > [!IMPORTANT]
> **Pausing or resuming an update can take up to eight hours to be applied to devices**. Windows Autopatch uses Microsoft Intune as its device management solution and that's the average frequency Windows devices take to communicate back to Microsoft Intune with new instructions to pause, resume, or rollback updates. For more information, see [how long does it take for devices to get a policy, profile, or app after they're assigned from Microsoft Intune](/mem/intune/configuration/device-profile-troubleshoot#how-long-does-it-take-for-devices-to-get-a-policy-profile-or-app-after-they-are-assigned). > **Pausing or resuming an update can take up to eight hours to be applied to devices**. Windows Autopatch uses Microsoft Intune as its device management solution and that's the average frequency Windows devices take to communicate back to Microsoft Intune with new instructions to pause, resume, or rollback updates. For more information, see [how long does it take for devices to get a policy, profile, or app after they're assigned from Microsoft Intune](/intune/intune-service/configuration/device-profile-troubleshoot#how-long-does-it-take-for-devices-to-get-a-policy-profile-or-app-after-they-are-assigned).
**To pause and resume a release:** **To pause and resume a release:**

4
windows/deployment/windows-autopatch/monitor/windows-autopatch-windows-quality-and-feature-update-reports-overview.md
View File

@ -70,7 +70,9 @@ Users with the following permissions can access the reports:
## About data latency ## About data latency
The data source for these reports is Windows [diagnostic data](../overview/windows-autopatch-privacy.md#microsoft-windows-1011-diagnostic-data). The data typically uploads from enrolled devices once per day. Then, the data is processed in batches before being made available in Windows Autopatch. The maximum end-to-end latency is approximately four hours. The data source for these reports is Windows [diagnostic data](../overview/windows-autopatch-privacy.md#microsoft-windows-1011-diagnostic-data) and Microsoft Intune.The data typically uploads from enrolled devices every hour. Then, the data is processed in batches before being made available in Windows Autopatch. The maximum end-to-end latency is approximately four hours.
## Windows quality and feature update statuses ## Windows quality and feature update statuses