Skip to content

Commit 4bc8b18

Browse files
Merge pull request #236002 from besiler/patch-6
Clean up signinactivity docs
2 parents c2b5a47 + 0581c71 commit 4bc8b18

File tree

1 file changed

+7
-7
lines changed

1 file changed

+7
-7
lines changed

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

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -22,16 +22,16 @@ This article explains a method to handle obsolete user accounts in Azure Active
2222

2323
## What are inactive user accounts?
2424

25-
Inactive accounts are user accounts that aren't required anymore by members of your organization to gain access to your resources. One key identifier for inactive accounts is that they haven't been used *for a while* to sign in to your environment. Because inactive accounts are tied to the sign-in activity, you can use the timestamp of the last sign-in that was successful to detect them.
25+
Inactive accounts are user accounts that aren't required anymore by members of your organization to gain access to your resources. One key identifier for inactive accounts is that they haven't been used *for a while* to sign in to your environment. Because inactive accounts are tied to the sign-in activity, you can use the timestamp of the last time an account attempted to sign in to detect inactive accounts.
2626

2727
The challenge of this method is to define what *for a while* means for your environment. For example, users might not sign in to an environment *for a while*, because they are on vacation. When defining what your delta for inactive user accounts is, you need to factor in all legitimate reasons for not signing in to your environment. In many organizations, the delta for inactive user accounts is between 90 and 180 days.
2828

29-
The last successful sign-in provides potential insights into a user's continued need for access to resources. It can help with determining if group membership or app access is still needed or could be removed. For external user management, you can understand if an external user is still active within the tenant or should be cleaned up.
29+
The last sign-in provides potential insights into a user's continued need for access to resources. It can help with determining if group membership or app access is still needed or could be removed. For external user management, you can understand if an external user is still active within the tenant or should be cleaned up.
3030

3131
## Detect inactive user accounts with Microsoft Graph
3232
<a name="how-to-detect-inactive-user-accounts"></a>
3333

34-
You can detect inactive accounts by evaluating the `lastSignInDateTime` property exposed by the `signInActivity` resource type of the **Microsoft Graph API**. The `lastSignInDateTime` property shows the last time a user made a successful interactive sign-in to Azure AD. Using this property, you can implement a solution for the following scenarios:
34+
You can detect inactive accounts by evaluating the `lastSignInDateTime` property exposed by the `signInActivity` resource type of the **Microsoft Graph API**. The `lastSignInDateTime` property shows the last time a user attempted to make an interactive sign-in attempt in Azure AD. Using this property, you can implement a solution for the following scenarios:
3535

3636
- **Last sign-in date and time for all users**: In this scenario, you need to generate a report of the last sign-in date of all users. You request a list of all users, and the last `lastSignInDateTime` for each respective user:
3737
- `https://graph.microsoft.com/v1.0/users?$select=displayName,signInActivity`
@@ -59,11 +59,11 @@ The following details relate to the `lastSignInDateTime` property.
5959
- AuditLog.Read.All
6060
- User.Read.All
6161

62-
- Each interactive sign-in that was successful results in an update of the underlying data store. Typically, successful sign-ins show up in the related sign-in report within 10 minutes.
62+
- Each interactive sign-in attempt results in an update of the underlying data store. Typically, sign-ins show up in the related sign-in report within 6 hours.
6363

64-
- To generate a `lastSignInDateTime` timestamp, you need a successful sign-in. The value of the `lastSignInDateTime` property may be blank if:
65-
- The last successful sign-in of a user took place before April 2020.
66-
- The affected user account was never used for a successful sign-in.
64+
- To generate a `lastSignInDateTime` timestamp, you an attempted sign-in. The value of the `lastSignInDateTime` property may be blank if:
65+
- The last attempted sign-in of a user took place before April 2020.
66+
- The affected user account was never used for a sign-in attempt.
6767

6868
- The last sign-in date is associated with the user object. The value is retained until the next sign-in of the user.
6969

0 commit comments

Comments
 (0)