set-defender deployment fails with loganalytics autoprovision enabled - its been deprecated in commercial

[brsteel]

Description

log analytics auto provisioning with defender has been deprecated in commercial

Steps to Reproduce

run the deployment
Steps to reproduce the behavior:
1.
2.

Expected behavior

Actual behavior

Screenshots

Additional context

We need to figure out what this did and can we just remove the autoprovisioning option from our code, or do we have to do something else.
defendder-for-cloud.bicep contains the setting

@description('Turn automatic deployment by Defender of the MMA (OMS VM extension) on or off')
param enableAutoProvisioning bool = true
var autoProvisioning = enableAutoProvisioning ? 'On' : 'Off'

Operating System:
Cloud (public, Azure Government, etc.):

[ruandersMSFT]

Deprecation of MMA auto-provisioning capability
September 18, 2024 As part of the MMA agent retirement, the auto provisioning capability that provides the installation and configuration of the agent for MDC customers, will be deprecated as well in two stages:

By the end of September 2024- auto provisioning of MMA will be disabled for customers that are no longer using the capability, as well as for newly created subscriptions. After end of September, the capability will no longer be able to be re-enabled on those subscriptions.

End of November 2024- auto provisioning of MMA will be disabled on subscriptions that haven't yet switched it off. From that point forward, it can no longer be possible to enable the capability on existing subscriptions.