[Automation Kit - QUESTION] Automation Project app issue when user is only assigned Automation Project Admin or Automation Project Contributor role.

[bilodeauju]

What is your question?

I am a Power Platform tenant administrator, I have setup the kit for testing in our organization as per the manual instructions here Set up the automation kit main components - Power Automate | Microsoft Learn.

I shared the Automation Project App with a few test users and assigned them the following roles in the main solution environment as per the documentation :

• Automation Project Admin: Maintains the configuration data in the automation kit and maps automation projects to environments.
• Automation Project Contributor: Generates or requests new automation projects.

From our intial testing, when a user has either the Automation Project Admin or Automation Project Contributor role only and they launch the Automation Project App, they see a banner at the top "Error when trying to retrieve data from the network". Also, the option "Add Project" is missing and they are unable to use the app.

Then I tested granting them the "Basic user" role together with the Automation Project Admin or Automation Project Contributor role and this resolved the error and the missing "Add project" button.

QUESTION: Is this the expected behavior by design or a bug? If this is by design, the documentation should include a note that the Automation project app also requires having at least the basic user role assigned to the Automation Project users.

What component is the question related to?

Automation Project

What solution version are you using?

June 2023

What app or flow are you having the issue with?

Automation Project

[G1982C]

I had exactly the same issue and applied the same fix. Additionally, I did wonder what happens when we update the solution each month, would we be required to re-share the apps after each update.

I assumed that if someone was given the Automation Project Admin role that the apps would automatically be available to them without manually sharing.

[G1982C]

Actually I retract my previous statement. The person I shared the app with can now open the Automation Project App, but the 'add project' button is still missing. I have even provided the security role 'system administrator' and still they are unable to see the 'add project' button.

[KoteshMCGit]

As per design, the use who launches the power automate project app needs a security role 'Automation Project Admin' or 'Automation Project Contributor' and also user primary email addresses should match with the user principal name (UPN).

I suggest please do verify once with above 2 items and let me know if you need additional details

[G1982C]

I can confirm that the person launching the app has both the Automatoin Project Admin and Automation Project Contributor role. As this person will be playing both roles.

Where are you referring too when you mention the user primary email address should match the UPN? As in AD they match. Also under the Automation roles the UPN matches the email address. Is there a particular place I should be checking for this match? Thanks

[bilodeauju]

As per design, the use who launches the power automate project app needs a security role 'Automation Project Admin' or 'Automation Project Contributor' and also user primary email addresses should match with the user principal name (UPN).

I suggest please do verify once with above 2 items and let me know if you need additional details

For context, we are a very large multinational organization and all employees are setup to have a different primary email address than their UPN. The requirement by design for user primary email addresses to match with the user principal name (UPN) is very problematic for us.

[Grant-Archibald-MS]

@KoteshMCGit to review this use case and look at impacts across the following with UPN does not match email address for approvals.

Key elements to verify:

1. Operation of Automation Project with UPN mismatch
2. Operation of Automation Solution Manager to meter a deployed solution

Once verified provide update on if changes are needed in the application and possible resolutions using unmanaged solution fixes or an update in an upcoming milestone release