Skip to content

Commit e467c7f

Browse files
authored
Merge pull request #101606 from tamram/tamram-0117
clarify portal auth via key or AAD
2 parents 74401ec + e0e99e9 commit e467c7f

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

includes/storage-auth-rbac-roles-include.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ services: storage
55
author: tamram
66
ms.service: storage
77
ms.topic: "include"
8-
ms.date: 07/25/2019
8+
ms.date: 01/17/2020
99
ms.author: tamram
1010
ms.custom: "include file"
1111
---
@@ -24,3 +24,5 @@ Azure provides the following built-in RBAC roles for authorizing access to blob
2424
> RBAC role assignments may take up to five minutes to propagate.
2525
>
2626
> Only roles explicitly defined for data access permit a security principal to access blob or queue data. Roles such as **Owner**, **Contributor**, and **Storage Account Contributor** permit a security principal to manage a storage account, but do not provide access to the blob or queue data within that account.
27+
>
28+
> Access to blob or queue data in the Azure portal can be authorized using either your Azure AD account or the storage account access key. For more information, see [Use the Azure portal to access blob or queue data](../articles/storage/common/storage-access-blobs-queues-portal.md).

0 commit comments

Comments
 (0)