IntuneAppConfigurationDevicePolicy cannot handle 'for Intune' applications

[dannyKBjj]

Description of the issue

Works well for most application types, but it cannot handle the 'for Intune' apps (e.g. Appian For Intune, Zoom for Intune etc.). However, if you create a configuration with a 'for Intune' application, then trigger Set-Targetresource by deleting the policy, the recreated policy will show a message about the application nolonger being available

I explored the issue a bit and seems be that when recreating the policy, it pick up both the Android and iOS app.

If I create a new policy:

The TargetedMobileApps guid in the policy matches the existing GUID for that.

I then export the policy and delete it. Run start-dscConfiguration to recreate the policy.

If I pull the TargetedMobileApps, it is now targetted at both the iOS and Android apps

With the end result that the policy in my tenant is broken:

Microsoft 365 DSC Version

1.24.1211.1

Which workloads are affected

Intune

The DSC configuration

IntuneAppConfigurationDevicePolicy "IntuneAppConfigurationDevicePolicy-Man-Dev-App-ZoomForIntune v2"
        {
            ApplicationId         = $ConfigurationData.NonNodeData.ApplicationId;
            Assignments           = @();
            CertificateThumbprint = $ConfigurationData.NonNodeData.CertificateThumbprint;
            Description           = "";
            DisplayName           = "Man-Dev-App-ZoomForIntune v2";
            Ensure                = "Present";
            Id                    = "50baf12c-db85-4ec5-ae51-385380207c63";
            PayloadJson           = "";
            RoleScopeTagIds       = @("0");
            Settings              = @(
                MSFT_MicrosoftGraphappConfigurationSettingItem{
                    AppConfigKey = 'test'
                    AppConfigKeyType = 'stringType'
                    AppConfigKeyValue = 'test'
                }
            );
            TargetedMobileApps    = @("us.zoom.videomeetings4intune");
            TenantId              = $OrganizationName;
        }

Verbose logs showing the problem

NA

Environment Information + PowerShell Version

[dannyKBjj]

Actually, I just realised that I mistakenly submitted modules to replace this thinking they weren't covered by DSC

#5444

#5401

These were merged and then pulled in favour of the existing DSC resource. My initial testing with my old modules suggests that they resolve this bug...

[dannyKBjj]

created pull request to fix this:

#5588