You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: microsoft-365/compliance/retention-policies-teams.md
+3-1Lines changed: 3 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -60,7 +60,9 @@ Other mailbox types, such as RoomMailbox that is used for Teams conference rooms
60
60
61
61
Teams uses an Azure-powered chat service as its primary storage for all messages (chats and channel messages). If you need to delete Teams messages for compliance reasons, retention policies for Teams can delete messages after a specified period, based on when they were created. Messages are then permanently deleted from both the Exchange mailboxes where they stored for compliance operations, and from the primary storage used by the underlying Azure-powered chat service. For more information about the underlying architecture, see [Security and compliance in Microsoft Teams](/MicrosoftTeams/security-compliance-overview) and specifically, the [Information Protection Architecture](/MicrosoftTeams/security-compliance-overview#information-protection-architecture) section.
62
62
63
-
Although this data from Teams chats and channel messages are stored in mailboxes, you must configure a retention policy for the **Teams channel messages** and **Teams chats** locations. Teams chats and channel messages are not included in retention policies that are configured for Exchange user or group mailboxes. If a user is added to a chat, a copy of all messages shared with them are ingested into their mailbox. The created date of those messages does not change for the new user and remains the same for all users.
63
+
Although this data from Teams chats and channel messages are stored in mailboxes, you must configure a retention policy for the **Teams channel messages** and **Teams chats** locations. Teams chats and channel messages are not included in retention policies that are configured for Exchange user or group mailboxes. Similarly, retention policies for Teams don't affect other email items stored mailboxes.
64
+
65
+
If a user is added to a chat, a copy of all messages shared with them are ingested into their mailbox. The created date of those messages does not change for the new user and remains the same for all users.
64
66
65
67
> [!NOTE]
66
68
> If a user is included in an active retention policy that retains Teams messages and you delete a mailbox of a user who is included in this policy, the mailbox is converted into an [inactive mailbox](inactive-mailboxes-in-office-365.md) to retain the Teams data. If you don't need to retain this Teams data for the user, exclude the user account from the retention policy and [wait for this change to take effect](create-retention-policies.md#how-long-it-takes-for-retention-policies-to-take-effect) before you delete their mailbox.
Copy file name to clipboardExpand all lines: microsoft-365/lighthouse/m365-lighthouse-compare-compliance-policies.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -24,24 +24,24 @@ description: "For Managed Service Providers (MSPs) using Microsoft 365 Lighthous
24
24
> [!NOTE]
25
25
> The features described in this article are in Preview, are subject to change, and are only available to partners who meet the [requirements](m365-lighthouse-requirements.md). If your organization does not have Microsoft 365 Lighthouse, see [Sign up for Microsoft 365 Lighthouse](m365-lighthouse-sign-up.md).
26
26
27
-
Microsoft 365 Lighthouse lets you view compliance policies across your tenants in a single view. You can drive security and standardization across your tenants by comparing policies. You can filter views to see settings that have been configured (versus settings that were left not configured), settings that differ in their configurations, or just the settings that match. You can also search for specific settings you’re interested in and see how that compares among the policies.
27
+
Microsoft 365 Lighthouse lets you view compliance policies across your tenants in a single view. You can drive security and standardization across your tenants by comparing policies. You can filter views to see settings that have been configured (versus settings that were left not configured), settings that differ in their configurations, or settings that match. You can also search for specific settings to see how they compare across policies.
28
28
29
29
## Before you begin
30
30
31
-
- Devices must have an Intune license and be enrolled in Microsoft Endpoint Manager (MEM).
31
+
Make sure devices have a Microsoft Intune license and are enrolled in Microsoft Endpoint Manager (MEM).
32
32
33
33
## Compare policy settings
34
34
35
35
1. In the left navigation pane in Lighthouse, select **Devices**.
36
36
37
37
2. Select the **Policies** tab.
38
38
39
-
3. From the **Filters** drop-down list, select an operating system/platform.
39
+
3. From the **Filters** drop-down list, select an operating system or platform.
40
40
41
41
> [!NOTE]
42
-
> You can only compare policies with the same operating system/platform.
42
+
> You can only compare policies with the same operating system or platform.
43
43
44
-
4. From the filtered list, select up to three policies you want to compare.
44
+
4. From the filtered list, select up to three policies that you want to compare.
Copy file name to clipboardExpand all lines: microsoft-365/lighthouse/m365-lighthouse-reset-user-password.md
+9-9Lines changed: 9 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -23,29 +23,29 @@ description: "For Managed Service Providers (MSPs) using Microsoft 365 Lighthous
23
23
> [!NOTE]
24
24
> The features described in this article are in Preview, are subject to change, and are only available to partners who meet the [requirements](m365-lighthouse-requirements.md). If your organization does not have Microsoft 365 Lighthouse, see [Sign up for Microsoft 365 Lighthouse](m365-lighthouse-sign-up.md).
25
25
26
-
Microsoft 365 Lighthouse lets you change or reset user passwords. You can reset a single user or multiple risky users across different tenants.
26
+
Microsoft 365 Lighthouse lets you change or reset user passwords. You can reset the password for a single user or for multiple risky users across different tenants.
27
27
28
28
## Reset a password for a user
29
29
30
30
1. In the left navigation pane in Lighthouse, select **Users**.
31
31
32
32
2. Select the **Search users** tab.
33
33
34
-
3. In the search box, enter a user’s name.
34
+
3. In the search box, enter a user's name.
35
35
36
36
4. From the search results list, select the user.
37
37
38
38
5. In the user details pane, select **Reset password**.
39
39
40
40
6. In the Reset password pane, select **Autogenerate a password** or **Let me create a password**.
41
41
42
-
a. If you choose to create a password, enter a password.
42
+
- If you choose to create a password, enter a password.
43
43
44
-
b. If you want the user to change their password after first signin, select the checkbox.
44
+
- If you want the user to change their password after first sign-in, select the checkbox.
45
45
46
46
7. Select **Reset password**.
47
47
48
-
## Reset password for risky users
48
+
## Reset a password for a risky user
49
49
50
50
1. In the left navigation pane in Lighthouse, select **Users**.
51
51
@@ -57,13 +57,13 @@ Microsoft 365 Lighthouse lets you change or reset user passwords. You can reset
57
57
58
58
5. In the Reset password pane, select **Autogenerate a password** or **Let me create a password**.
59
59
60
-
1. If you choose to create a password, enter a password.
60
+
- If you choose to create a password, enter a password.
61
61
62
-
1. If you want the user to change their password after first signin, select the checkbox.
62
+
- If you want the user to change their password after first sign-in, select the checkbox.
63
63
64
64
6. Select **Reset password**.
65
65
66
66
## Related content
67
67
68
-
[Manage Microsoft 365 user accounts](../enterprise/manage-microsoft-365-accounts.md)\
69
-
[Block user sign-in](m365-lighthouse-block-user-signin.md)
68
+
[Manage Microsoft 365 user accounts](../enterprise/manage-microsoft-365-accounts.md) (article)\
69
+
[Block user sign-in](m365-lighthouse-block-user-signin.md) (article)
Copy file name to clipboardExpand all lines: microsoft-365/lighthouse/m365-lighthouse-review-audit-logs.md
+36-36Lines changed: 36 additions & 36 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -29,58 +29,58 @@ Microsoft 365 Lighthouse audit logs record actions that generate a change in Lig
29
29
30
30
To view audit logs, you must have one of the following permissions:
31
31
32
-
- Azure AD role - Global Administrator of partner tenant
32
+
- Azure Active Directory (Azure AD) role - Global Administrator of partner tenant
33
33
34
-
- Partner Center role - Admin Agent
34
+
-Microsoft Partner Center role - Admin agent
35
35
36
-
## Review logs
36
+
## Review audit logs
37
37
38
38
1. In the left navigation pane in Lighthouse, select **Audit logs**.
39
39
40
40
> [!NOTE]
41
41
> It might take up to 1 hour to see new logs. Go to the respective service to see the most recent changes.
42
42
43
-
2.To filter the logs, refine the list using the following options:
43
+
2.Filter the logs, as needed, by using the following options:
44
44
45
45
-**Date range** - Previous month, week, or day.
46
46
-**Tenants** - Tenant tags or customer tenant names.
47
-
-**Activity** - Microsoft 365 activity type that corresponds to the action taken. For more information, see Activity Types table.
47
+
-**Activity** - Microsoft 365 activity type that corresponds to the action taken. For more information, see the [Activities](#activities) table.
48
48
-**Initiated by** - Who initiated the action.
49
49
50
-
3. Select a log from the list to see full details including the **Request** body.
51
-
52
-
Select **Export**, to export log data to a comma-separated values (.csv) file.
53
-
54
-
## Activity Types
55
-
56
-
The following table is a list of activity types captured within Lighthouse audit logs. The list is subject to change as new actions are created. You can use the activity value from the audit log to see what action was initiated.
57
-
58
-
| Activity name | Area in Microsoft 365 Lighthouse | Action initiated | Service impacted|
|**restartDevice**| Devices | Restart | Microsoft Endpoint Manager|
74
-
|**syncDevice**| Devices | Sync | Microsoft Endpoint Manager|
75
-
|**rebootNow**| Threat management | Reboot | Microsoft Endpoint Manager|
76
-
|**reprovision**| Windows 365 | Retry Provisioning | Windows 365|
77
-
|**windowsDefenderScanFull**| Threat management | Full scan | Microsoft Endpoint Manager|
78
-
|**windowsDefenderScan**| Threat management | Quick scan | Microsoft Endpoint Manager|
79
-
|**windowsDefenderUpdateSignatures**| Threat management | Update antivirus | Microsoft Endpoint Manager|
50
+
3. Select a log from the list to see full details, including the **Request** body.
51
+
52
+
To export log data to a comma-separated values (.csv) file, select **Export**.
53
+
54
+
## Activities
55
+
56
+
The following table lists activities captured within Lighthouse audit logs. The list is subject to change as new actions are created. You can use the activity listed in the audit log to see which action was initiated.<br><br>
57
+
58
+
| Activity name | Area in Lighthouse | Action initiated | Service impacted |
59
+
|--|--|--|--|
60
+
|**apply**| Tenants | Apply deployment plan | Azure AD, Microsoft Endpoint Manager (MEM)|
61
+
|**assignTag**| Tenants | Apply a tag from a customer |Lighthouse |
62
+
|**changeDeploymentStatus**| Tenants | Action plan status for deployment plan |Lighthouse |
63
+
|**offboardTenant**| Tenants | Inactivate a customer |Lighthouse |
64
+
|**resetTenantOnboardingStatus**| Tenants | Reactive a customer |Lighthouse |
65
+
|**tenantTags**| Tenants | Create or delete a tag |Lighthouse |
66
+
|**tenantCustomizedInformation**| Tenants | Create, update, or delete a customer website or contact information | Lighthouse |
67
+
|**unassignTag**| Tenants | Remove a tag from a customer |Lighthouse |
68
+
|**blockUserSignin**| Users | Block sign-in | Azure AD |
69
+
|**confirmUsersCompromised**| Users | Confirm a user is compromised | Azure AD |
70
+
|**dismissUsersRisk**| Users | Dismiss user risk | Azure AD |
71
+
|**resetUserPassword**| Users | Reset password | Azure AD |
72
+
|**setCustomerSecurityDefaultsEnabledStatus**| Users | Enable multifactor authentication (MFA) with security defaults | Azure AD |
73
+
|**restartDevice**| Devices | Restart | MEM|
74
+
|**syncDevice**| Devices | Sync | MEM|
75
+
|**rebootNow**| Threat management | Reboot | MEM|
76
+
|**reprovision**| Windows 365 | Retry provisioning | Windows 365 |
77
+
|**windowsDefenderScanFull**| Threat management | Full scan | MEM|
If you need more information, you can use Microsoft Graph API to access more audit events. For more information, see [Overview for multi-tenant management using the Microsoft 365 Lighthouse API](/graph/managedtenants-concept-overview).
83
+
If you need more information, use Microsoft Graph API to access more audit events. For more information, see [Overview for multi-tenant management using the Microsoft 365 Lighthouse API](/graph/managedtenants-concept-overview).
Copy file name to clipboardExpand all lines: microsoft-365/security/defender-endpoint/run-analyzer-macos-linux.md
+2-1Lines changed: 2 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -22,6 +22,7 @@ ms.technology: m365d
22
22
23
23
# Run the client analyzer on macOS and Linux
24
24
25
+
25
26
**Applies to:**
26
27
-[Microsoft Defender for Endpoint Plan 2](https://go.microsoft.com/fwlink/p/?linkid=2154037)
27
28
@@ -30,7 +31,7 @@ ms.technology: m365d
30
31
1. Download the [XMDE Client Analyzer](https://aka.ms/XMDEClientAnalyzer) tool to the macOS or Linux machine you need to investigate.
31
32
32
33
> [!NOTE]
33
-
> The current SHA256 hash of 'XMDEClientAnalyzer.zip' that is downloaded from the above link is: '34C0DA20A6B38A16951394958991CD74EF7E07EB1DE06923547B351665A32DF6'.
34
+
> The current SHA256 hash of 'XMDEClientAnalyzer.zip' that is downloaded from the above link is: 'AA6E73A5F451C3B78B066C9D55EE6499CE3C2F1A6E05CCE691A6055F36F93A3B'.
34
35
35
36
2. Extract the contents of XMDEClientAnalyzer.zip on the machine.
0 commit comments