Skip to content

Commit 3a17cb9

Browse files
committed
issue #11878
1 parent 226e2eb commit 3a17cb9

File tree

1 file changed

+3
-0
lines changed

1 file changed

+3
-0
lines changed

articles/azure-netapp-files/nfs-access-control-lists.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -188,6 +188,9 @@ This Audit ACL is an example of that, where `user1` is audited for failed access
188188
189189
Azure NetApp Files only supports setting administrative flags for Audit ACEs. File access logging isn't currently supported. Alarm ACEs aren't supported in Azure NetApp Files.
190190
191+
>[!IMPORTANT]
192+
>Azure NetApp Files supports setting administrative flags for Audit ACEs, however the ACEs do _not_ function. In addition, Alarm ACEs aren't supported in Azure NetApp Files.
193+
191194
## NFSv4.x user and group principals
192195
193196
With NFSv4.x ACLs, user and group principals define the specific objects that an ACE should apply to. Principals generally follow a format of [email protected]. The “name” portion of a principal can be a user or group, but that user or group must be resolvable in Azure NetApp Files via the LDAP server connection when specifying the NFSv4.x ID domain. If the name@domain isn't resolvable by Azure NetApp Files, then the ACL operation fails with an “invalid argument” error.

0 commit comments

Comments
 (0)