IntuneSettingCatalogASRRulesPolicyWindows10: Unable to import ASR rules configuration

[aarontguilmette]

Description of the issue

When attempting to deploy a DSC export that contains ASR rules that were configured as a Settings Catalog, the DSC reports there is an error with the Identity Property not being implemented.

Microsoft 365 DSC Version

1.23.1122.1

Which workloads are affected

other

The DSC configuration

New Azure Windows 11 23H2 VM 
Install all DSC modules per documentation

Verbose logs showing the problem

PS C:\dsc\DSCBaseline\M365TenantConfig> Start-DscConfiguration -Wait -Verbose -Force -Path .\
VERBOSE: Perform operation 'Invoke CimMethod' with following parameters, ''methodName' =
SendConfigurationApply,'className' = MSFT_DSCLocalConfigurationManager,'namespaceName' =
root/Microsoft/Windows/DesiredStateConfiguration'.
VERBOSE: An LCM method call arrived from computer Win11DSC with user sid S-1-5-21-3146137402-4174336731-232515920-500.
VERBOSE: [Win11DSC]: LCM:  [ Start  Set      ]
VERBOSE: [Win11DSC]: LCM:  [ End    Set      ]
The command Get-TargetResource of the PS resource MSFT_IntuneSettingCatalogASRRulesPolicyWindows10 does not implement
the key property Identity mentioned in the corresponding MOF schema file C:\Program Files\WindowsPowerShell\Modules\Mic
rosoft365DSC\1.23.1122.1\DscResources\MSFT_IntuneSettingCatalogASRRulesPolicyWindows10\MSFT_IntuneSettingCatalogASRRule
sPolicyWindows10.schema.mof as a mandatory parameter. All key parameters mentioned in the schema file must be
implemented by the command Get-TargetResource as mandatory function parameters.
    + CategoryInfo          : InvalidOperation: (root/Microsoft/...gurationManager:String) [], CimException
    + FullyQualifiedErrorId : KeyParameterNotImplemented
    + PSComputerName        : localhost

VERBOSE: Operation 'Invoke CimMethod' complete.
VERBOSE: Time taken for configuration job to complete is 10.514 seconds

Environment Information + PowerShell Version

OsName               : Microsoft Windows 11 Pro
OsOperatingSystemSKU : 48
OsArchitecture       : 64-bit
WindowsVersion       : 2009
WindowsBuildLabEx    : 22621.1.amd64fre.ni_release.220506-1250
OsLanguage           : en-US
OsMuiLanguages       : {en-US}

Name                           Value
----                           -----
PSVersion                      5.1.22621.2506
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.22621.2506
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1

[ricmestre]

@andikrueger The Identity field in the schema needs to be changed from Key to Write, nevertheless the resource cannot be used after that anyway. See my issue #3961 for more details.

[aarontguilmette]

Ah, that makes sense, then--I didn't dig enough through to see the chicken/egg.