Skip to content

Commit 2b8aaf4

Browse files
committed
Status of condition features table update
1 parent 081224c commit 2b8aaf4

File tree

1 file changed

+1
-2
lines changed

1 file changed

+1
-2
lines changed

articles/role-based-access-control/conditions-overview.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ ms.service: role-based-access-control
88
ms.subservice: conditions
99
ms.topic: overview
1010
ms.workload: identity
11-
ms.date: 10/24/2022
11+
ms.date: 01/19/2023
1212
ms.author: rolyon
1313

1414
#Customer intent: As a dev, devops, or it admin, I want to learn how to constrain access within a role assignment by using conditions.
@@ -107,7 +107,6 @@ Some features of conditions are still in preview. The following table lists the
107107
| Add conditions using [Azure PowerShell](conditions-role-assignments-powershell.md), [Azure CLI](conditions-role-assignments-cli.md), or [REST API](conditions-role-assignments-rest.md) | GA | October 2022 |
108108
| Use [resource and request attributes](conditions-format.md#attributes) for specific combinations of Azure storage resources, access attribute types, and storage account performance tiers. For more information, see [Status of condition features in Azure Storage](../storage/common/authorize-data-access.md#status-of-condition-features-in-azure-storage). | GA | October 2022 |
109109
| Use [custom security attributes on a principal in a condition](conditions-format.md#principal-attributes) | Preview | November 2021 |
110-
| Use resource and request attributes in a condition | Preview | May 2021 |
111110

112111
## Conditions and Azure AD PIM
113112

0 commit comments

Comments
 (0)