Fix: Replace en dash with hyphen in Group functions #1450
Conversation
Enhance: Additional automatic formatting and style updates based on standard conventions. - Updated parameter help messages to use single quotes for consistency. - Changed parameter set names to use single quotes for consistency. - Improved formatting and alignment of parameter blocks in New-EntraGroup, Set-EntraGroup, New-EntraBetaGroup, and Set-EntraBetaGroup scripts. - Enhanced readability by standardizing the use of brackets and spacing in conditional statements.
|
Learn Build status updates of commit b0a3415: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
|
I know it's late on the beginning of Easter weekend, but is anyone still available to review, merge, and publish this fix in a 1.6.1 release? Users on Windows PowerShell 5.1 currently cannot import Microsoft.Entra.Groups. 🙏 @DButoyez, @emmanuel-karanja, @KenitoInc, @SteveMutungi254, @v-akarke |
|
Hi @SamErde , is this bug fixed for PowerShell 5.x?. Customer: |
The fix has been merged into the project, but a new build has not been released yet. Your options for now are to either downgrade to v1.0.5 or to follow this repository's instructions to build a local copy of the module. (Not recommended unless you are familiar and comfortable with that process.) |
|
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: @KenitoInc |
|
@AngeloAgb, @SamErde, the plan is to release a new version with the fixes by end of the week of 28th April to May 4th. cc: @DButoyez, @KenitoInc. |
|
Hi @SamErde, @SteveMutungi254, @thomasvochten, the customer downgraded per your recommendation and still gets the error. |
|
@AngeloAgb, can you please run |
|
I suspect that you successfully downgraded the Microsoft.Entra module to 1.0.5, but v1.0.6 of the Entra sub-modules is probably also installed still. Running If so, there are two ways you can cleanly work around it: Completely uninstall the base module and all sub-modules, and then re-install v1.0.5: Get-InstalledModule Microsoft.Entra* | % { Uninstall-Module -Name $_.Name -AllVersions -Force }
# You MAY need to run the above command twice to make sure it's removed.
Install-Module -Name Microsoft.Entra -RequiredVersion 1.0.5
Import-Module -Name Microsoft.EntraOR, import the older version explicitly and make sure Group 1.0.6 is not imported: Import-Module Microsoft.Entra.Groups -RequiredVersion 1.0.5 -Force
Import-Module Microsoft.Entra
Get-Module | Where-Object {$_.Name -eq 'Microsoft.Entra.Groups' -and $_.Version -eq '1.0.6'} | Remove-Module -ForceIt's not convenient, but it should work until the fix is released. |
|
Hi @SamErde , here is an update from the customer. That’s not the case here. I already removed all the modules before downgrading the Entra Module to 1.0.5. 
After installing the module, the dependent modules which are installed automatically are always the latest one. If you try the steps on your end you will get what I am trying to explain. |
|
OK, I updated my workaround example with more coverage. The following lines will ensure that both 1.0.5 and 1.0.6 are installed. It will successfully import the 1.0.5 Groups module and 1.0.6 of all other Microsoft.Entra modules. They will see the error still but the final output should show what they need: # Run the following commands in a new PowerShell session before importing any modules:
# Install both versions of the module:
Install-Module -Name 'Microsoft.Entra' -RequiredVersion 1.0.5 -Force
Install-Module -Name 'Microsoft.Entra' -RequiredVersion 1.0.6 -Force
# Import the working version of the Groups sub-module:
Import-Module -Name 'Microsoft.Entra.Groups' -RequiredVersion 1.0.5 -Force
# Import the base module and then remove the auto-imported version of the Groups sub-module that doesn't work:
Import-Module -Name 'Microsoft.Entra'
Get-Module | Where-Object { $_.Name -eq 'Microsoft.Entra.Groups' -and $_.Version -eq '1.0.6' } | Remove-Module -ForceHere is what I get: |
|
Hello @SamErde @SteveMutungi254, thomasvochten, Just following up on this if the fix was successfully deployed on PS 5.x so I can ask the customer to test again. You mentioned " there was a plan to deploy fixes by end of the week of 28th April to May 4th". |
|
@AngeloAgb - Yes, version 1.0.7 was successfully deployed on May 5th. |
3 participants
Fixed
This PR replaces the en dashes with a regular hyphen. Successfully tested with a local build in Windows PowerShell 5.1 and PowerShell 7.5.
Changed
Additional automatic formatting and style updates based on standard conventions. Copilot summary: