Closed Atreidae closed 1 year ago
Seems to actually be an issue with the backend Teams Cmdlets
The New-CsAutoAttendant cmdlet in the Ps Module appears to correctly strip off the parsed attributes however, when it attempts to call "$internalOutput = Microsoft.Teams.ConfigAPI.Cmdlets.internal\New-CsAutoAttendant @PSBoundParameters" the "CallHandlingAssociations" parameter is invalid.
New-CsAutoAttendant : A parameter cannot be found that matches parameter name 'CallHandlingAssociations'.
This happens in both versions 4.3.3 and 5.0 of the PS Module.
I need to test on a clean box to ensure it's not something in my PowerShell folders on OneDrive.
Spun up a Windows Sandbox and replicated by installing the MSTeams and MSOL module.
Connected to MSTeams and MSOL and ran
new-UcmCsFixedNumberDiversion -OriginalNumber +************ -TargetNumber +************* -Domain **************.onmicrosoft.com -Country AU -LicenceType MCOPSTNEAU2
Looks like something has changed just recently. I've been having the above error for 2 weeks. but now I seem to be getting errors relating to sharing the afterhours schedule. which indicates that perhaps the new afterhours handling (tenant wide) is now the default. which is okay. I just need to update the schedule creation bit to make a unique schedule and look for it.
Issues with New-UcmCsFixedNumberDiversion since the migration to UCM prefix, the cmdlet needs some love.