The issue with "PPTenantIsolationSettings" Component's Rule values while mof file.

[maheshdalavi]

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

ISSUE TITLE:

The issue with "PPTenantIsolationSettings" Component's Rule values while mof file.

ISSUE DESCRIPTION (this template):

• While configuring the localhost.mof got the error for the below value.
• If I remove this key-value pair, things work fine.

       _PPTenantIsolationSettings 342dd968-8fbc-4dfa-9671-9e38695b4c4e
        {
            ApplicationId         = $ConfigurationData.NonNodeData.ApplicationId;
            CertificateThumbprint = $ConfigurationData.NonNodeData.CertificateThumbprint;
            Enabled               = $False;
            IsSingleInstance      = "Yes";
            Rules                 = "@(ule {r
                TenantName          = ''
                Direction           = 'unknown'
            }
            )";
            TenantId              = $ConfigurationData.NonNodeData.TenantId;_

Verbose logs showing the problem

At C:\WINDOWS\system32\WindowsPowerShell\v1.0\Modules\PSDesiredStateConfiguration\PSDesiredStateConfiguration.psm1:2369 
char:21
+ ...             Write-NodeMOFFile $Name $mofNode $Script:NodeInstanceAlia ...
+                 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidOperation: (:) [Write-Error], InvalidOperationException
    + FullyQualifiedErrorId : InvalidMOFDefinition,Write-NodeMOFFile
Write-NodeMOFFile : Invalid MOF definition for node 'localhost': Exception calling "ValidateInstanceText" with "1"
argument(s): "Convert property 'Rules' value from type 'STRING[]' to type 'INSTANCE[]' failed
 At line:304, char:2
 Buffer:
"M365TenantConfig";
};^
insta
"
At
C:\WINDOWS\system32\WindowsPowerShell\v1.0\Modules\PSDesiredStateConfiguration\PSDesiredStateConfiguration.psm1:2369
char:21
+ ...             Write-NodeMOFFile $Name $mofNode $Script:NodeInstanceAlia ...
+                 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidOperation: (:) [Write-Error], InvalidOperationException
    + FullyQualifiedErrorId : InvalidMOFDefinition,Write-NodeMOFFile

Suggested solution to the issue

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

# insert configuration here

The operating system the target node is running

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