You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If policy doesn't exist yet on tenant then when trying to create it an error message appears but policy is created without issues, any subsequent changes to the policy also work without issues.
Issue is caused by trying to retrieve the policy by name before existing and the cmdlet Get-MessageClassification spits that error message, I'll raise a PR to fix this.
Microsoft 365 DSC Version
1.24.710.3
Which workloads are affected
Exchange Online
The DSC configuration
EXOMessageClassification "EXOMessageClassification-EXOMessageClassification_1"
{
Credential =$CredsCredential;
DisplayName ="EXOMessageClassification_1";
DisplayPrecedence ="Highest";
Ensure ="Present";
Identity ="EXOMessageClassification_1";
Name ="EXOMessageClassification_1";
PermissionMenuVisible =$True;
RecipientDescription ="Shown to recipients";
RetainClassificationEnabled =$True;
SenderDescription ="Shown to senders";
}
Verbose logs showing the problem
Setting configuration of Message Classification for EXOMessageClassification_1 Ex6F930
4|Microsoft.Exchange.Configuration.Tasks.ManagementObjectNotFoundException|The operation couldn't be performed because object 'EXOMessageClassification_1' couldn't be found on 'PR3P195A06DC006.EURP195A006.PROD.OUTLOOK.COM'.
+ CategoryInfo : NotSpecified: (:) [], CimException
+ FullyQualifiedErrorId : [Server=DU2P195MB2466,RequestId=51e7e140-0733-181e-1630-1d324bfe6955,TimeStamp=Mon,15Jul202412:09:30GMT],Write-ErrorMessage+ PSComputerName : localhost
Environment Information + PowerShell Version
Win11 / PS5.1
The text was updated successfully, but these errors were encountered:
Description of the issue
If policy doesn't exist yet on tenant then when trying to create it an error message appears but policy is created without issues, any subsequent changes to the policy also work without issues.
Issue is caused by trying to retrieve the policy by name before existing and the cmdlet
Get-MessageClassification
spits that error message, I'll raise a PR to fix this.Microsoft 365 DSC Version
1.24.710.3
Which workloads are affected
Exchange Online
The DSC configuration
Verbose logs showing the problem
Environment Information + PowerShell Version
The text was updated successfully, but these errors were encountered: