🪲 Microsoft.Entra.Groups.psm1 has a bug in version 1.0.6 preventing module load

[jasonfritts]

Thanks for reporting the bug. Please ensure you've gone through the following checklist before opening an issue:

• Make sure you can reproduce this issue using the latest released version of Microsoft.Entra or Microsoft.Entra.Beta.
• Please search the existing issues to see if there has been a similar issue filed.

Describe the bug

To Reproduce

Steps to reproduce the behavior:

1. Execute Import-Module Microsoft.Entra
2. See error at ...

Import-Module Microsoft.Entra
Import-Module : At C:\Program Files\WindowsPowerShell\Modules\Microsoft.Entra.Groups\1.0.6\Microsoft.Entra.Groups.psm1:1302 char:191
+ ... group (max 64 characters). It must use ASCII characters (0–127).")]
+                                                                  ~
Missing closing ')' in expression.
At C:\Program Files\WindowsPowerShell\Modules\Microsoft.Entra.Groups\1.0.6\Microsoft.Entra.Groups.psm1:1302 char:191
+ ... group (max 64 characters). It must use ASCII characters (0–127).")]
+                                                                  ~
Parameter declarations are a comma-separated list of variable names with optional initializer expressions.
At C:\Program Files\WindowsPowerShell\Modules\Microsoft.Entra.Groups\1.0.6\Microsoft.Entra.Groups.psm1:1302 char:191
+ ... group (max 64 characters). It must use ASCII characters (0–127).")]
+                                                                  ~
Missing ')' in function parameter list.
At line:1 char:1
+ Import-Module Microsoft.Entra
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : ParserError: (:) [Import-Module], ParentContainsErrorRecordException
    + FullyQualifiedErrorId : MissingEndParenthesisInExpression,Microsoft.PowerShell.Commands.ImportModuleCommand

Module Version

    Directory: C:\Program Files\WindowsPowerShell\Modules


ModuleType Version    Name                                ExportedCommands
---------- -------    ----                                ----------------
Script     1.0.6      Microsoft.Entra                     Enable-EntraAzureADAlias
Script     1.0.6      Microsoft.Entra.Applications        {Add-EntraApplicationOwner, Add-EntraServicePrincipalDelegatedPermissionClassification, Add-EntraServicePrincipalOwner, Get-EntraApplication...}
Script     1.0.6      Microsoft.Entra.Authentication      {Add-EntraEnvironment, Connect-Entra, Disconnect-Entra, Find-EntraPermission...}
Script     1.0.6      Microsoft.Entra.CertificateBased... {Get-EntraUserCBAAuthorizationInfo, Get-EntraUserCertificateUserIdsFromCertificate, Set-EntraUserCBACertificateUserId, Enable-EntraAzureADAlias...}
Script     1.0.6      Microsoft.Entra.DirectoryManagement {Add-EntraAdministrativeUnitMember, Add-EntraCustomSecurityAttributeDefinitionAllowedValue, Add-EntraDeviceRegisteredOwner, Add-EntraDeviceRegisteredUser...}
Script     1.0.6      Microsoft.Entra.Governance          {Get-EntraDirectoryRoleAssignment, Get-EntraDirectoryRoleDefinition, Get-EntraUnsupportedCommand, New-EntraCustomHeaders...}
Script     1.0.6      Microsoft.Entra.Groups              {Add-EntraGroupMember, Add-EntraGroupOwner, Add-EntraLifecyclePolicyGroup, Get-EntraDeletedGroup...}
Script     1.0.6      Microsoft.Entra.Reports             {Get-EntraAuditDirectoryLog, Get-EntraAuditSignInLog, Get-EntraAuthenticationMethodUserRegistrationDetailReport, Get-EntraUnsupportedCommand...}
Script     1.0.6      Microsoft.Entra.SignIns             {Get-EntraAuthorizationPolicy, Get-EntraConditionalAccessPolicy, Get-EntraFeatureRolloutPolicy, Get-EntraIdentityProvider...}
Script     1.0.6      Microsoft.Entra.Users               {Get-EntraDeletedUser, Get-EntraUnsupportedCommand, Get-EntraUser, Get-EntraUserAdministrativeUnit...}

Environment Data

$PSVersionTable

Name                           Value
----                           -----
PSVersion                      5.1.20348.2849
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.20348.2849
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1

Screenshots

Additional context

• Can fix the issue by editing C:\Program Files\WindowsPowerShell\Modules\Microsoft.Entra.Groups\1.0.6\Microsoft.Entra.Groups.psm1:2428 char:167 and removing all non-ASCII characters
• Unable to reproduce using PowerShell 7.5.0 only 5.1

[SamErde]

Can reproduce in Windows PowerShell 5.1 and confirmed that it does not occur in PowerShell 7.5. Setting output encoding to utf-8 does not seem to help in WPS 5.1.

#1450 fixes this bug.

[SamErde]

@jasonfritts, it may be too late for the team to merge and publish changes this week, but I'm happy to help provide local build instructions in the meantime for anyone who is in a bind with this bug.

[SteveMutungi254]

Thanks, @jasonfritts, for flagging this — and a big thank you to @SamErde for the quick fix. We’ll move fast to apply it. cc: @emmanuel-karanja , @KenitoInc, @DButoyez

[SteveMutungi254]

Update: We’ve added PowerShell 5.1 validation "follow-up or repair item" to our build pipeline to catch these issues early and ensure they won’t happen again. Target ETA is by end of May. cc: @jasonfritts, @SamErde. @KenitoInc