[BUG] Remove-PnPTeamsChannelUser - weird error return

[toucan2297]

Notice

Reporting an Issue or Missing Feature

When using the command, i've notices a weird error return :

$team.DisplayName = 'RBPO Coordination protection de l'enfance / pédopsychiatrie'
$userEmail = 'c.vincent@h***********m'
$privateTeamChannel.DisplayName = 'Recherche documentaire - analyse de la littérature'

COMMAND ISSUED :
Remove-PnPTeamsChannelUser -Identity $userEmail -Channel $privateTeamChannel.DisplayName -Team $team.DisplayName -Force

Expected behavior

I expect removing the user from the TEAMS private channel

Actual behavior

Bad request (400): Invalid filter clause: ')' or operator expected at position 103 in '(resourceProvisioningOptions/Any(x:x eq 'Team') and mailNickname eq 'RBPO Coordination protection de l'enfance / pédopsychiatrie')'.

the caracter chain looks like a graph request
i've iterated on 1082 TEAMS to process a user supprssion and it works pretty OK, but i've found 2 use cases where terminal retruned that error; i really don't think it comes from my script, pretty sure there's something wrong in the command and it reaches a block where it goes wrong (maybe special chars)

Steps to reproduce behavior

Remove-PnPTeamsChannelUser -Identity $userEmail -Channel $privateTeamChannel.DisplayName -Team $team.DisplayName -Force

What is the version of the Cmdlet module you are running?

2.12.0

Which operating system/environment are you running PnP PowerShell on?

• Windows

[jackpoz]

This seems to be caused by the ' character in $team.DisplayName

[toucan2297]

This seems to be caused by the ' character in $team.DisplayName

I understand the issue comes from a bad char in the team name, which is badly escaped when passed to graph API request, then i think the issue is not on the PnP user side (me), because at this point we would need to avoid using bad chars when naming teams or m365 groups or sharepoint sites, this bug report is not intended to be a criticism, PnP is great and help me so much, i sent this report to improve the command and put the finger on a use case that is not actually handled by the function code

[jackpoz]

Oh my comment was to help you workaround the issue until it gets properly fixed, bug reports are always welcome 😃