[EXOPerimeterConfiguration/EXOResourceConfiguration] Switch to IsSingleInstance

[ykuijs]

Details of the scenario you tried and the problem that is occurring

Both the EXOPerimeterConfiguration and EXOResourceConfiguration resources have an Identity property, but in both resources this property isn't used. It looks like these resources should only be used once in a configuration and therefore should be using the IsSingleInstance parameter instead of the Identity parameter.

Verbose logs showing the problem

Suggested solution to the issue

Change the Identity parameter to the IsSingleInstance parameter.

The DSC configuration that is used to reproduce the issue (as detailed as possible)

        EXOIRMConfiguration 'ConfigureIRMConfiguration'
        {
            Identity                                   = "Global"
            AutomaticServiceUpdateEnabled              = $True
            AzureRMSLicensingEnabled                   = $True
            DecryptAttachmentForEncryptOnly            = $True
            EDiscoverySuperUserEnabled                 = $True
            EnablePdfEncryption                        = $True
            InternalLicensingEnabled                   = $True
            JournalReportDecryptionEnabled             = $True
            RejectIfRecipientHasNoRights               = $True
            SearchEnabled                              = $True
            SimplifiedClientAccessDoNotForwardDisabled = $True
            SimplifiedClientAccessEnabled              = $True
            SimplifiedClientAccessEncryptOnlyDisabled  = $True
            TransportDecryptionSetting                 = "Mandatory"
            Ensure                                     = "Present"
            Credential                                 = $credsGlobalAdmin
        }

The operating system the target node is running

Version of the DSC module that was used ('dev' if using current dev branch)

Dev