Skip to content

Commit e94cc1d

Browse files
author
Jiachen Jiang
authored
Update aspire-dashboard.md
1 parent 7e19d76 commit e94cc1d

File tree

1 file changed

+20
-2
lines changed

1 file changed

+20
-2
lines changed

articles/container-apps/aspire-dashboard.md

Lines changed: 20 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -36,7 +36,8 @@ The dashboard is secured against unauthorized access and modification. To use th
3636
::: zone pivot="portal"
3737

3838
> [!TIP]
39-
> While you have the portal as an option, the recommended approach to enabling your dashboard is with [azd](aspire-dashboard.md?pivots=azd). If you run into an problems using the portal, [create an issue in the Container Apps GitHub repo](https://github.com/microsoft/azure-container-apps/issues).
39+
> While you have the portal as an option, the recommended approach to enabling your dashboard is with [azd
40+
](aspire-dashboard.md?pivots=azd). If you run into an problems using the portal, [create an issue in the Container Apps GitHub repo](https://github.com/microsoft/azure-container-apps/issues).
4041

4142
You can enable the .NET Aspire Dashboard on any existing container app using the following steps.
4243

@@ -96,7 +97,24 @@ Refer to the following items if you have issues enabling your dashboard:
9697

9798
- You might receive an authentication error when accessing the dashboard that reads, "Could not authenticate user with requested resource."
9899

99-
To solve this problem, make sure you grant the *Microsoft.App/managedEnvironments/write*, *Contributor*, or *Owner* roles on your Container Apps environment.
100+
This issue occurs because security group permissions do not propagate to the Container App Environment. To solve this problem, make sure you explicitly give yourself a *Contributor* or *Owner* role on your Container Apps environment. This can be done through the following steps:
101+
102+
- **Navigate to the Resource:**
103+
- Open the Azure Portal and search for your container app environment.
104+
- **Access the Access Control (IAM) Blade:**
105+
- Click on _Access Control (IAM)_ for the container app environment.
106+
- **Verify Existing Role Assignments:**
107+
- Check if you (or your account) are assigned any roles. Note that permissions do not currently propagate through security groups.
108+
- If you are not, follow the remaining steps to assign the role.
109+
- **Explicit Role Assignment:**
110+
- Click _Add > Add role assignment_.
111+
- Choose Role: Either _Contributor_ or _Owner_, as appropriate for your required access level.
112+
- Assign the role explicitly to your user account (e.g., [email protected]).
113+
- **Save and Confirm:**
114+
- Save the changes. Ensure the role is visible under the Role Assignments section.
115+
- **Verify Dashboard Access:**
116+
- Test by attempting to access the Aspire dashboard. If you continue to get the error, please reach out to our team.
117+
100118

101119
## Related content
102120

0 commit comments

Comments
 (0)