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

'add-powerAppsAccount' command was found in the module 'Microsoft.Powerapps.Administration.Powershell' but could not the module could not be loaded. #523

Open
Keatnuxsuo opened this issue Jan 17, 2024 · 7 comments
Assignees
Labels
PowerShell question Further information is requested

Comments

@Keatnuxsuo
Copy link

Followed all the steps up until Connect enterprise policy to Dataverse environment. I have this error while trying to execute ./NewIdentity.ps1. I put in the right environmentid for dataverse at the armpolicyid that was generated in the previous step.

I use cloud shell for this. Powershell version is 7. I read this blog that this module won't work cross-platform (6+) because it relies on .Net Framework.

My question is "Is there another way to associate Dataverse to Azure Enterprise Policy"?

Thank you
image

@phecke phecke added the waiting on input from dev team Waiting on dev team authors of sample to review label Feb 23, 2024
@phecke
Copy link
Member

phecke commented Feb 23, 2024

@Keatnuxsuo I sent your question to the team that maintains the code.

@phecke phecke removed the waiting on input from dev team Waiting on dev team authors of sample to review label Mar 16, 2024
@GBDCHA1
Copy link

GBDCHA1 commented Oct 1, 2024

I am getting similar error while connecting VNet with PowerApps but PowerShell command is giving the similar error appreciate some help.

@phecke
Copy link
Member

phecke commented Oct 1, 2024

@JasonHQX @Mattp123 Any suggestions for @Keatnuxsuo?

@phecke phecke added the question Further information is requested label Oct 1, 2024
@tkawas
Copy link

tkawas commented Oct 2, 2024

has there been any updates on this??

@ValerasNarbutas
Copy link

ValerasNarbutas commented Oct 2, 2024

did anyone try to use before importing? @Keatnuxsuo @phecke @JasonHQX @Mattp123
Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Force
dir . | Unblock-File

@Michal-Ziemba
Copy link

Michal-Ziemba commented Oct 2, 2024

did anyone try to use before importing? @Keatnuxsuo @phecke @JasonHQX @Mattp123 Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Force
dir . | Unblock-File

Just tried and it didn't help. The same error.

@ValerasNarbutas
Copy link

yeah, we had same issue, colleagues specifically targeted 2.0.194 (previous working one) version instead of 2.0.197

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
PowerShell question Further information is requested
Projects
None yet
Development

No branches or pull requests

7 participants