TeamsUpdateManagementPolicy: Verbose parameter causes problems during deployments

[ricmestre]

Description of the issue

Even though I have tests for this resource that are not failing, even for deployments, now I tested a customer's blueprint where the deployment to another tenant reliably failed, after some troubleshooting I found out this was due to having the Verbose parameter included, after removing it everything worked.

I'll create a PR to fix this.

Microsoft 365 DSC Version

1.24.424.1

Which workloads are affected

Teams

The DSC configuration

TeamsUpdateManagementPolicy "TeamsUpdateManagementPolicy-Global"
        {
            AllowManagedUpdates  = $False;
            AllowPreview         = $False;
            AllowPublicPreview   = "FollowOfficePreview";
            Credential           = $Credscredential;
            Ensure               = "Present";
            Identity             = "Global";
            UpdateDayOfWeek      = 1;
            UpdateTime           = "18:00";
            UpdateTimeOfDay      = "6:00 PM";
            UseNewTeamsClient    = "MicrosoftChoice";
        }

Verbose logs showing the problem

VERBOSE: [REDACTED]: [[TeamsUpdateManagementPolicy]TeamsUpdateManagementPolicy-Tag:Default] Updating existing Teams Update Management Policy {Tag:Default}
{"code":"ClientError","message":"Invalid input parameters Tenant Admin can't modify first party documents","action":"Please check your request parameters. CorrelationId: b55fd536-347c-41ac-9db2-3d5f509ae706","errorCode":40006}
+ CategoryInfo          : NotSpecified: (:) [], CimException
+ FullyQualifiedErrorId : ClientError,Microsoft.Teams.Policy.Administration.Cmdlets.Core.SetTeamsUpdateManagementPolicyCmdlet
+ PSComputerName        : localhost

Environment Information + PowerShell Version

N/A