Skip to content

Commit be28313

Browse files
Merge pull request #223921 from JnHs/jh-lh-datarole
add note about data access
2 parents 8d9989f + 035b6f1 commit be28313

File tree

1 file changed

+4
-1
lines changed

1 file changed

+4
-1
lines changed

articles/lighthouse/concepts/tenants-users-roles.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Tenants, users, and roles in Azure Lighthouse scenarios
33
description: Understand how Azure Active Directory tenants, users, and roles can be used in Azure Lighthouse scenarios.
4-
ms.date: 08/02/2022
4+
ms.date: 01/13/2023
55
ms.topic: conceptual
66
---
77

@@ -42,6 +42,9 @@ All [built-in roles](../../role-based-access-control/built-in-roles.md) are curr
4242

4343
In some cases, a role that had previously been supported with Azure Lighthouse may become unavailable. For example, if the [`DataActions`](../../role-based-access-control/role-definitions.md#dataactions) permission is added to a role that previously didn't have that permission, that role can no longer be used when onboarding new delegations. Users who had already been assigned the role will still be able to work on previously delegated resources, but they won't be able to perform tasks that use the [`DataActions`](../../role-based-access-control/role-definitions.md#dataactions) permission.
4444

45+
> [!IMPORTANT]
46+
> When assigning roles, be sure to review the [actions](../../role-based-access-control/role-definitions.md) specified for each role. In some cases, even though roles with [`DataActions`](../../role-based-access-control/role-definitions.md#dataactions) permission are not supported, the actions included in a role may allow access to data, where data is exposed through access keys and not accessed via the user's identity. For example, the [Virtual Machine Contributor](/azure/role-based-access-control/built-in-roles) role includes the `Microsoft.Storage/storageAccounts/listKeys/action` action, which returns storage account access keys that could be used to retrieve certain customer data.
47+
4548
> [!NOTE]
4649
> As soon as a new applicable built-in role is added to Azure, it can be assigned when [onboarding a customer using Azure Resource Manager templates](../how-to/onboard-customer.md). There may be a delay before the newly-added role becomes available in Partner Center when [publishing a managed service offer](../how-to/publish-managed-services-offers.md). Similarly, if a role becomes unavailable, you may still see it in Partner Center for a period of time; however, you won't be able to publish new offers using such roles.
4750

0 commit comments

Comments
 (0)