7.9 KiB
title, description, ms.date, ms.service, ms.subservice, ms.topic, ms.localizationpriority, author, ms.author, manager, ms.reviewer, ms.collection
| title | description | ms.date | ms.service | ms.subservice | ms.topic | ms.localizationpriority | author | ms.author | manager | ms.reviewer | ms.collection | ||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Maintain the Windows Autopatch environment | This article details how to maintain the Windows Autopatch environment | 09/15/2023 | windows-client | itpro-autopatch | how-to | medium | tiaraquan | tiaraquan | aaroncz | smithcharles |
|
Maintain the Windows Autopatch environment
After you've completed enrollment in Windows Autopatch, some management settings might need to be adjusted. Use the following steps:
- Review the Microsoft Intune settings described in the following section.
- If any of the items apply to your environment, make the adjustments as described.
Note
As your operations continue in the following months, if you make changes after enrollment to policies in Microsoft Intune, Microsoft Entra ID, or Microsoft 365 that affect Windows Autopatch, it's possible that Windows Autopatch could stop operating properly. To avoid problems with the service, check the specific settings described in Fix issues found by the readiness assessment tool before you change the policies listed there.
Microsoft Intune settings
| Setting | Description |
|---|---|
| Deployment rings for Windows 10 or later | For any deployment rings for Windows 10 or later policies you've created, exclude the Modern Workplace Devices - All Microsoft Entra group from each policy. For more information, see Create and assign deployment rings. Windows Autopatch creates some update ring policies. These policies have "Modern Workplace" in the name. For example:
When you update your own policies, ensure that you don't exclude the Modern Workplace Devices - All Microsoft Entra group from the policies that Windows Autopatch created. To resolve the Not ready result: After enrolling into Autopatch, make sure that any update ring policies you have exclude the Modern Workplace Devices - All Microsoft Entra group. For more information, see Manage Windows 10 software updates in Intune. To resolve the Advisory result:
For more information, see Manage Windows 10 software updates in Intune. |
Windows Autopatch configurations
Windows Autopatch deploys, manages and maintains all configurations related to the operation of the service, as described in Changes made at tenant enrollment. Don't make any changes to any of the Windows Autopatch configurations.
Windows Autopatch tenant management
Windows Autopatch tenant actions
The Tenant management blade presents IT admins with any actions that are required to maintain Windows Autopatch service health. The Tenant management blade can be found by navigating to Tenant administration > Windows Autopatch > Tenant management.
Important
If you have any critical actions in your tenant, you must take action as soon as possible as the Windows Autopatch service might not be able to manage your tenant. When a critical action is active on your tenant, Windows Autopatch will consider your tenant as inactive.
The type of banner that appears depends on the severity of the action. Currently, only critical actions are listed.
Tenant action severity types
| Severity | Description |
|---|---|
| Critical | You must take action as soon as possible to avoid disruption to the Windows Autopatch service. If no action is taken, Windows Autopatch might not be able to manage devices in your tenant, and the Windows Autopatch service may be marked as inactive. To restore service health and return to an active status, all critical pending actions must be resolved. |
Critical actions
| Action type | Severity | Description |
|---|---|---|
| Maintain tenant access | Critical | Required licenses have expired. The licenses include:
To take action on missing licenses, you can visit the Microsoft 365 admin center or contact your Microsoft account manager. Until you have renewed the required licenses to run the service, Windows Autopatch marks your tenant as inactive. For more information, see Microsoft 365 - What happens after my subscription expires? |
| Maintain tenant access | Critical | Address tenant access issues. Windows Autopatch currently can't manage your tenant. Until you take action, your tenant is marked as inactive, and you have only limited access to the Windows Autopatch portal. Reasons for tenant access issues:
Take action by consenting to allow Windows Autopatch to make the appropriate changes on your behalf. You must be a Global Administrator to consent to this action. Once you provide consent, Windows Autopatch remediates this critical action for you. For more information, see Windows Autopatch enterprise applications. |
Inactive status
Note
Only the Windows Autopatch sections of your tenant will be marked as inactive.
When Windows Autopatch is inactive, you're alerted with banners on all Windows Autopatch blades. You only have access to the Tenant management and Support requests blades. All other blades return an error message and redirect you to Tenant management blade.
To be taken out of the inactive status, you must resolve any critical actions shown in the Tenant management blade.
Note
Once critical actions are resolved, it can take up to two hours for Windows Autopatch to return to an active state.
Impact to your tenant
| Impact area | Description |
|---|---|
| Management | Windows Autopatch isn't able to manage your tenant and perform non-interactive actions we use to run the service. Non-interactive actions include:
For more information, see Windows Autopatch enterprise applications. |
| Device updates | Changes to Windows Autopatch policies aren't pushed to your devices. The existing configurations on these devices remain unchanged, and they continue receiving updates. |