Skip to content

Commit ddd1350

Browse files
authored
Merge pull request MicrosoftDocs#180 from Microsoft/FromPrivateRepo
From private repo
2 parents e4f5e8c + 565e054 commit ddd1350

File tree

156 files changed

+1181
-394
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

156 files changed

+1181
-394
lines changed

articles/active-directory/active-directory-privileged-identity-management-configure.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -105,7 +105,7 @@ There are two ways to track how your employees and admins are using privileged r
105105
The second option is to set up regular [access reviews](active-directory-privileged-identity-management-how-to-start-security-review.md). These access reviews can be performed by and assigned reviewer (like a team manager) or the employees can review themselves. This is the best way to monitor who still requires access, and who no longer does.
106106

107107
## Azure AD PIM at subscription expiration
108-
Prior to reaching general availability Azure AD PIM was in preview and there were no license checks for a tenant to preview Azure AD PIM.  Now that Azure AD PIM has reached general availability, a trial or paid subscription must be present in the tenant to continue using PIM after December 2016.  If your organization does not purchase Azure AD Premium P2 or your subscription expires, then Azure AD PIM will no longer be available in your tenant.  You can read more in the [Azure AD PIM subscription requirements](/privileged-identity-management/subscription-requirements.md)
108+
Prior to reaching general availability Azure AD PIM was in preview and there were no license checks for a tenant to preview Azure AD PIM.  Now that Azure AD PIM has reached general availability, a trial or paid subscription must be present in the tenant to continue using PIM after December 2016.  If your organization does not purchase Azure AD Premium P2 or your subscription expires, then Azure AD PIM will no longer be available in your tenant.  You can read more in the [Azure AD PIM subscription requirements](./privileged-identity-management/subscription-requirements.md)
109109

110110
## Next steps
111111
[!INCLUDE [active-directory-privileged-identity-management-toc](../../includes/active-directory-privileged-identity-management-toc.md)]

articles/active-directory/active-directory-reporting-retention.md

+26-28
Original file line numberDiff line numberDiff line change
@@ -13,38 +13,36 @@ ms.devlang: na
1313
ms.topic: article
1414
ms.tgt_pltfrm: na
1515
ms.workload: identity
16-
ms.date: 03/07/2016
16+
ms.date: 11/30/2016
1717
ms.author: dhanyahk
1818

1919
---
2020
# Azure Active Directory report retention policies
2121
*This documentation is part of the [Azure Active Directory Reporting Guide](active-directory-reporting-guide.md).*
2222

23-
Azure Active Directory (Azure AD) reports retain data for a certain number of days, indicated here.
24-
25-
| Report | Description |
26-
| --- | --- |
27-
| Sign-ins from unknown sources |30 days |
28-
| Sign-ins after multiple failures |30 days |
29-
| Sign-ins from multiple geographies |30 days |
30-
| Sign-ins from IP addresses with suspicious activity |30 days |
31-
| Sign-ins from possibly infected devices |30 days |
32-
| Irregular sign-in activity |30 days |
33-
| Users with anomalous sign-in activity |30 days |
34-
| Users with leaked credentials |30 days |
35-
| Audit report |180 days |
36-
| Password reset activity (Azure AD) |30 days |
37-
| Password reset activity (Identity Manager) |30 days |
38-
| Password reset registration activity (Azure AD) |30 days |
39-
| Password reset registration activity (Identity Manager) |30 days |
40-
| Self service groups activity (Azure AD) |30 days |
41-
| Self service groups activity (Identity Manager) |30 days |
42-
| Application usage |30 days |
43-
| Account provisioning activity |30 days |
44-
| Password rollover status |30 days |
45-
| Account provisioning errors |30 days |
46-
| RMS usage |30 days |
47-
| Most active RMS users |30 days |
48-
| RMS device usage |30 days |
49-
| RMS enabled application usage |30 days |
23+
24+
25+
This article provides an overview of data retention for the different Activity reports present in Azure Active Directory.
26+
27+
For Activity reports, for Premium and Premium 2 customers, we start collecting your activity data as soon as you sign-up for a Premium license. For free customers, we start collecting activity data as soon as you login into the portal or use our reporting APIs for the first time.
28+
29+
If you had already seeing reports in the Azure Classic portal, you will see your data immediately in the Azure Portal (new). If you haven’t turned on reporting through the old portal and logging into Azure Active Directory in Azure Portal and want to see these activity reports, it may take up 2 hours for you to see the data. We start collecting the data as soon as you log into the Azure Active Directory blade.
30+
31+
For Security signals, we start collecting data as soon as you opt-in to use Identity Protection Center.
32+
33+
34+
35+
**Activity reports**
36+
37+
| Report | Azure AD Free | Azure AD Premium 1 | Azure AD Premium 2 |
38+
| :-- | :-- | :-- | :-- |
39+
| Directory Audit | 7 days | 30 days | 30 days |
40+
| Sign-in Activity | 7 days | 30 days | 30 days |
41+
42+
**Security Signals**
43+
44+
| Report | Azure AD Free | Azure AD Premium 1 | Azure AD Premium 2 |
45+
| :-- | :-- | :-- | :-- |
46+
| Risky sign-ins | 7 days | 30 days | 90 days |
47+
5048

0 commit comments

Comments
 (0)