Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The term 'Join-String' is not recognized as the name of a cmdlet, function, script file, or operable program. #511

Closed
chuckstones opened this issue Dec 11, 2023 · 3 comments
Assignees

Comments

@chuckstones
Copy link

Following error message is received when attempting to add permission scopes to Microsoft Graph through the ManagePermissionsGrant.ps1 script:

ApplicationName AppId


Microsoft Graph 00000003-0000-0000-c000-000000000000

Join-String : The term 'Join-String' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify
that the path is correct and try again.
At C:\Users________\Downloads\ManagePermissionGrant.ps1:227 char:35

  • $joinedScopes = $selectedScopes | Join-String -Property {$_.Value} -S ...
  •                               ~~~~~~~~~~~
    
    • CategoryInfo : ObjectNotFound: (Join-String:String) [], ParentContainsErrorRecordException
    • FullyQualifiedErrorId : CommandNotFoundException

The same error is received if attempting to add one permission scope or multiple.

I am attempting to install the Microsoft Power Platform COE "CenterofExcellenceCoreComponents_4.17_managed.zip" and am unable to due to not being able to create a connection for the HTTP with Azure AD (HTTP with MS Entra) connection reference.

Reference link: https://learn.microsoft.com/en-gb/connectors/webcontentsv2/#authorize-the-connector-to-act-on-behalf-of-a-signed-in-user

Entra connection error

@martincyr
Copy link
Contributor

Join-String was introduced with PowerShell 6.2, so my guess is that the script was run with a PowerShell older than 6.2.
#514 should fix that.

@bhaarathms
Copy link
Contributor

PowerShell version 7 or later needs to be installed to run this script.

@chuckstones
Copy link
Author

Urgh, I'm so sorry guys. You're a absolutely correct, I had v7 installed but it's running side by side with the previous installation, so my shortcut was loading v5.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants