Announcing GA of enhanced patching for SQL Server on Azure VM with Azure Update Manager

TarynPratt I have checked it and there is no good way to exclude SQL updates in a maintenance plan. Except one really checks the pending update list in AUM and exclude SQL CU or GDR Update IDs. 

As I assumed SQL updates will be mostly in security updates or updates category. Unselecting the whole update category doesn't fit the purpose. 

Unfortunately there is a second issue with the new instance based SQL patching. 

Enabling it will alter the the WU policy settings (download and install at the time set in SQL patching) in registry and lead to default reboot behaviour of WU after applying patches. The SQL patching has no logical link to the maintenance plan reboot policy, which would be feasible. 

It will even override a GPO which intend is to ensure that WU settings are compliant with the defaults as AUM docs suggest (download only, include other Microsoft products). 

Disabling the SQL patching feature will entirely delete the registry key in policies Windows Update.

Does anyone experience the same? This is reproducible on Arc Enabled Windows Server 2022 running on-premises.