Skip to content

Commit b3ea7a8

Browse files
Merge pull request #244510 from JnHs/jh-portal-111804
fixes MicrosoftDocs/azure-docs#111804
2 parents bf90286 + a3083f7 commit b3ea7a8

File tree

1 file changed

+8
-2
lines changed

1 file changed

+8
-2
lines changed

articles/azure-portal/azure-portal-dashboard-share-access.md

Lines changed: 8 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Share Azure portal dashboards by using Azure role-based access control
33
description: This article explains how to share a dashboard in the Azure portal by using Azure role-based access control.
44
ms.topic: how-to
5-
ms.date: 03/16/2023
5+
ms.date: 07/10/2023
66
---
77

88
# Share Azure dashboards by using Azure role-based access control
@@ -22,7 +22,10 @@ For example, any users who have the [Owner](/azure/role-based-access-control/bui
2222

2323
Users with the [Reader](/azure/role-based-access-control/built-in-roles#reader) role for the subscription (or a custom role with `Microsoft.Portal/Dashboards/Read` permission) can list and view dashboards within that subscription, but they can't modify or delete them. These users are able to make private copies of dashboards for themselves. They can also make local edits to a published dashboard for their own use, such as when troubleshooting an issue, but they can't publish those changes back to the server.
2424

25-
To expand access to a dashboard beyond the access granted at the subscription level, assign permissions to an individual dashboard, or to a resource group that contains several dashboards. For example, if a user should have limited permissions across the subscription, but needs to be able to edit one particular dashboard, you can assign a different role with more permissions (such as [Contributor](/azure/role-based-access-control/built-in-roles#contributor)) for that dashboard only.
25+
To expand access to a dashboard beyond the access granted at the subscription level, you can assign permissions to an individual dashboard, or to a resource group that contains several dashboards. For example, if a user should have limited permissions across the subscription, but needs to be able to edit one particular dashboard, you can assign a different role with more permissions (such as [Contributor](/azure/role-based-access-control/built-in-roles#contributor)) for that dashboard only.
26+
27+
> [!IMPORTANT]
28+
> Since individual tiles within a dashboard can enforce their own access control requirements, some users with access to view or edit a dashboard may not be able to see information within specific tiles. To ensure that users can see data within a certain tile, be sure that they have the appropriate permissions for the underlying resources accessed by that tile.
2629
2730
## Publish a dashboard
2831

@@ -62,6 +65,9 @@ For each dashboard that you have published, you can assign Azure RBAC built-in r
6265

6366
1. Select **Review + assign** to complete the assignment.
6467

68+
> [!TIP]
69+
> As noted above, individual tiles within a dashboard can enforce their own access control requirements based on the resources that the tile displays. If users need to see data for a specific tile, be sure that they have the appropriate permissions for the underlying resources accessed by that tile.
70+
6571
## Next steps
6672

6773
* View the list of [Azure built-in roles](../role-based-access-control/built-in-roles.md).

0 commit comments

Comments
 (0)