What's New in Windows Autopatch - New Feature: Tenant Management Blade

[Harman_Thind]

Hi all! We are announcing that the new Windows Autopatch Tenant Management blade is now live in the Windows Autopatch admin center. You can find this blade by navigating to: Tenant administration > Windows Autopatch > Tenant management in the Microsoft Endpoint Manager admin center. Alternatively, if your tenant has been flagged for an action, you will see a banner notifying you of this action in the Windows Autopatch devices blade. See screenshots below for examples.

The purpose of the Tenant Management blade is to highlight all tenant level actions that require an admin action. Currently, the only action that is live is for select customers to take action on their tenant access model, more details below. Once there, Global Admins will need to consent to the action to approve the changes which are as follows:

If you enrolled into Windows Autopatch before July 11, 2022, Windows Autopatch will:

• Create the Modern Workplace Management enterprise application.
  • This is a limited enterprise application with elevated privileges. We use this account to manage the service, publish baseline configuration updates and maintain overall service health. For more information, see Changes made at tenant enrollment.
• Remove the following:
  • Service accounts: MSAdmin, MsAdminInt, MsTest
  • Groups: Workplace Service Accounts, Modern Workplace Service - Intune Reader MMD, Modern Workplace Service - Intune Reader All, Modern Workplace Service - Intune Admin All
  • Conditional Access Policy: Modern Workplace - Secure Workstation

If you enrolled into Windows Autopatch after July 11, 2022, Windows Autopatch will only remove the service accounts, groups and conditional access policy as specified in the previous section as you already have the new first party application on your tenant.

For more information, see the following public documentation: 

• Changes made at tenant enrollment - Windows Deployment | Microsoft Learn
• Maintain the Windows Autopatch environment - Windows Deployment | Microsoft Learn
• Privacy - Windows Deployment | Microsoft Learn

[#2]

Hi @Harman_Thind,

do you know if there is a Roadmap for AutoPatch with features and changes we can expect in the future?

Where can we share Ideas for for features customers are missing?

Best Regards,
Ugur

[#3]

Hi @Ugur_Koc ,

We have plans for a public roadmap that will become available soon. We will keep this tech community discussion board up to date with the latest information!

As for sharing feedback, we have the Windows Autopatch Feedback Portal. Feel free to share feedback directly on that portal. 

Thank you!

Harman

[#4]

What about the "old" configuration profiles using OMA-URI in Intune (Modern Workplace..)? Can we delete them?

[#5]

Hi @MatAitAzzouzene,

If you look for Message Center Post (MC443898): the migration from OMA-URI to Intune Settings Catalog this explains the changes taking place. The previous profiles will be cleaned up once the rollout is complete. The deployment of the change commenced last week and will continue through this month. 

Regards,

Richard

[#6]

(MC443898): the migration from OMA-URI to Intune Settings Catalog is not visible in my message center although we are enrolled in Autopatch. How is this possible ?

[#7]

Hi @Yves te Poel, 

If the messages are not visible in Message center, please also check under Tenant admin-->Windows autopatch-->Messages. If you cannot see the messages here, I would suggest opening a support request so that the Windows Autopatch Service Engineering team can investigate further: Submit a support request - Windows Deployment | Microsoft Learn

I would also suggest you verify that you have your contact details up to date before doing this: Add and verify admin contacts - Windows Deployment | Microsoft Learn

Regards,

Richard