Answered

Error The provided machine group identifier is invalid

(0) Share

Report

Posted on by JonathanGibbs

313

I have a PowerApps Canvas App which
- calls a Power Automate Cloud flow, which
- calls a Power Automate Desktop Flow, which runs on an unattended VM in Azure, under a local account on the machine.

This all works fine when I run it all myself.

The Power Apps app is shared with a colleague, who has the same licences as me. When attempting to open the Power Apps app she gets this dialog:

Screenshot 2022-10-10 160725.png

I've entered the unattended VM machine name in Machine or machine group, and then tried various versions for Domain and username / Password, but only get the error 'We weren't able to add this connection'. Under More.. I get 'The provided machine group identifier '[VM-name]' is invalid'.
The Domain/username attempts have been
\[LocalAccountName under which PAD runs]
\\[LocalAccountName..]
AzureAD\[MyName]
AzureAD\[MyColleague'sName]
but all fail.

I'm thinking this must mean my colleague cannot 'see' the VM in some way? She has Contributor access in Azure IAM for the machine, and I have Owner.

This permissions stuff is so baffling!!

Categories:

Power Automate Desktop

I have the same question (0)

All responses (5)

Answers (1)

Sort by

VJR 7,635 on at

Like
a
(0)

Report
Copy link

Link copied!

Could you also see via the Machine runtime app to verify if you find anything fishy there.

https://powerautomate.microsoft.com/en-us/blog/introducing-power-automate-machine-runtime/

https://learn.microsoft.com/en-us/power-automate/desktop-flows/manage-machines

Also compare your settings with your colleague's.

Was this reply helpful? Yes No
VJR 7,635 on at

Like
a
(0)

Report
Copy link

Link copied!

Also the Machine and Machine Group section on the Cloud Flows

Was this reply helpful? Yes No
JonathanGibbs 313 on at

Like
a
(0)

Report
Copy link

Link copied!

Well, I've found a few possible anomalies: the machine was not shared with my colleague, but now is; I've tried making her co-owner of the Cloud flow; I've made her role in the VM the same as mine; I've RDP'd into the machine as her and made sure it opens for her; while there I checked the Machine Runtime App while logged in as her and it said she did not have permission to change the workspace, though that would be expected. But none of these changes have helped.
The Cloud Flow is definitely shared
The Desktop Flow(s) are definitely shared
The machine is shared
She has the same access rights to the machine
What else might be in the sequence?

Was this reply helpful? Yes No
Verified answer

JonathanGibbs 313 on at

Like
a
(1)

Report
Copy link

Link copied!
This is now resolved (for anyone facing the same issue):
I did a 'save as' copy of the cloud flow under a different name, and shared this with my colleague as a co-owner;
I ran the cloud flow directly, as her, and resolved the connection requests, before attempting to run it from the PowerApps application.
Previously I had tried resolving the connection requests on the first run of the PowerApps App which calls the cloud flow, rather than run the cloud flow directly. It may be that attempting to resolve these while the flow was 'wrapped' by PowerApps was the problem.
Don't know which of these two changes made it work, but glad it does!

Was this reply helpful? Yes No
wigglwrrm on at

Like
a
(0)

Report
Copy link

Link copied!

This helped a BUNCH - we were stuck with the same situation. Thank you so much!! 🙂

Was this reply helpful? Yes No