TeamsOrgWideAppSettings attrib ManagedIdentity

[PavolVonSekule]

Description of the issue

Hi,

we updated M365DSC to the latest version, but we are having issues running the Start/Test-DSCConfiguration.
Res TeamsOrgWideAppSettings requires attribute ManagedIdentity, even if added to the MOF file, error is the same, please advise, thanks.

Microsoft 365 DSC Version

1.24.1002.1

Which workloads are affected

Teams

The DSC configuration

instance of MSFT_Credential as $MSFT_Credential1ref
{
Password = "-----BEGIN CMS-----#####\n-----END CMS-----";
UserName = "###.onmicrosoft.com";

};

instance of MSFT_TeamsOrgWideAppSettings as $MSFT_TeamsOrgWideAppSettings1ref
{
ResourceID = "[TeamsOrgWideAppSettings]Container-208-4f85d2dd-3f11-4e0b-a68d-62b4ef5c84c0";
Credential = $MSFT_Credential1ref;
IsSideloadedAppsInteractionEnabled = False;
#ManagedIdentity = False;
SourceInfo = "::10::3::TeamsOrgWideAppSettings";
IsSingleInstance = "Yes";
ModuleName = "Microsoft365DSC";
ModuleVersion = "1.24.1002.1";

ConfigurationName = "MainConfig";

};
instance of OMI_ConfigurationDocument

                {

Version="2.0.0";

                    MinimumCompatibleVersion = "1.0.0";


                    CompatibleVersionAdditionalProperties= {"Omi_BaseResource:ConfigurationName"};


                    Author="xeb4010";


                    GenerationDate="10/15/2024 14:48:08";


                    GenerationHost="ABC01";


                    ContentType="PasswordEncrypted";


                    Name="MainConfig";


                };

Verbose logs showing the problem

PS C:\Users\me\source\m365automation\src>Start-DscConfiguration -Wait -Verbose -UseExisting | fl
VERBOSE: Perform operation 'Invoke CimMethod' with following parameters, ''methodName' = ApplyConfiguration,'className' = MSFT_DSCLocalConfigurationManager,'namespaceName' = root/Microsoft/Windows/DesiredStateConfiguration'.
VERBOSE: An LCM method call arrived from computer ABC01 with user sid S-1-5-21-1413711509-3798752799-1858511927-68712.
VERBOSE: [ABC01]: [] Starting consistency engine.
WARNING: [ABC01]: [] The partial configuration file C:\Windows\system32\configuration\PartialConfigurations\PartialConfiguration_MainConfig.mof will be skipped. Reason: The command Test-TargetResource of the PS module
MSFT_TeamsOrgWideAppSettings does not implement the write property ManagedIdentity mentioned in the corresponding MOF schema file C:\Program
Files\WindowsPowerShell\Modules\Microsoft365DSC\1.24.1002.1\DscResources\MSFT_TeamsOrgWideAppSettings\MSFT_TeamsOrgWideAppSettings.schema.mof. All write paramenters mentioned in the schema file must be implemented by the command Test-TargetResource.
One or more partial configurations failed to apply. No configuration could be created. LCM failed to start desired state configuration manually.
+ CategoryInfo : ObjectNotFound: (root/Microsoft/...gurationManager:String) [], CimException
+ FullyQualifiedErrorId : MI RESULT 6
+ PSComputerName : localhost

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

Environment Information + PowerShell Version

OsName : Microsoft Windows Server 2019 Standard
OsOperatingSystemSKU : StandardServerEdition
OsArchitecture : 64-bit
WindowsVersion : 1809
WindowsBuildLabEx : 17763.1.amd64fre.rs5_release.180914-1434
OsLanguage : en-US
OsMuiLanguages : {en-US, de-DE}

Key : PSVersion
Value : 5.1.17763.6414
Name : PSVersion

Key : PSEdition
Value : Desktop
Name : PSEdition

Key : PSCompatibleVersions
Value : {1.0, 2.0, 3.0, 4.0...}
Name : PSCompatibleVersions

Key : BuildVersion
Value : 10.0.17763.6414
Name : BuildVersion

Key : CLRVersion
Value : 4.0.30319.42000
Name : CLRVersion

Key : WSManStackVersion
Value : 3.0
Name : WSManStackVersion

Key : PSRemotingProtocolVersion
Value : 2.3
Name : PSRemotingProtocolVersion

Key : SerializationVersion
Value : 1.1.0.1
Name : SerializationVersion