Skip to content

Commit 23b1ab3

Browse files
authored
Merge pull request #110569 from MarkusVi/dhanyah91
dhanyah91
2 parents 7f23339 + fbe3621 commit 23b1ab3

File tree

1 file changed

+7
-4
lines changed

1 file changed

+7
-4
lines changed

articles/active-directory/reports-monitoring/howto-manage-inactive-user-accounts.md

Lines changed: 7 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ ms.topic: conceptual
1414
ms.tgt_pltfrm: na
1515
ms.workload: identity
1616
ms.subservice: report-monitor
17-
ms.date: 03/11/2020
17+
ms.date: 04/07/2020
1818
ms.author: markvi
1919
ms.reviewer: dhanyahk
2020

@@ -62,11 +62,14 @@ No.
6262

6363
### What edition of Azure AD do I need to access the property?
6464

65-
To access this property using the related API, you need an Azure AD Premium edition.
65+
You can access this property in all editions of Azure AD.
6666

6767
### What permission do I need to read the property?
6868

69-
To read this property, you need to grant the following right: **AuditLogs.Read.All**
69+
To read this property, you need to grant the following rights:
70+
71+
- AuditLogs.Read.All
72+
- Organisation.Read.All
7073

7174

7275
### When does Azure AD update the property?
@@ -78,7 +81,7 @@ Each interactive sign-in that was successful results in an update of the underly
7881

7982
To generate a lastSignInDateTime timestamp, you need a successful sign-in. Because the lastSignInDateTime property is a new feature, the value of the lastSignInDateTime property can be blank if:
8083

81-
- The last successful sign-in of a user took place before this feature was released.
84+
- The last successful sign-in of a user took place before this feature was released (12/01/2019).
8285
- The affected user account was never used for a successful sign-in.
8386

8487
## Next steps

0 commit comments

Comments
 (0)