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: Microsoft365/purview/purview/audit-logs/mailbox-audit-logs.md
+6-8Lines changed: 6 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,5 @@
1
1
---
2
-
title: How to use mailbox audit logs in Microsoft 365
2
+
title: Use mailbox audit logs in Microsoft 365
3
3
description: Describes how to use mailbox audit logs to determine when a mailbox was updated unexpectedly or whether items are missing in Microsoft 365 dedicated.
4
4
author: Cloud-Writer
5
5
ms.author: meerak
@@ -18,20 +18,18 @@ search.appverid: MET150
18
18
ms.date: 05/05/2025
19
19
---
20
20
21
-
# How to use mailbox audit logs in Microsoft 365
21
+
# Use mailbox audit logs in Microsoft 365
22
22
23
-
In Microsoft 365, you can run mailbox audit logs to determine when a mailbox was updated unexpectedly or whether items are missing from a mailbox. For example, you may have to do this if items are moved or if they're deleted unexpectedly or incorrectly.
23
+
In Microsoft 365, you can run [mailbox audit logs](/purview/audit-mailboxes) to determine when a mailbox was updated unexpectedly or whether items are missing from a mailbox. For example, you may have to do this if items are moved or if they're deleted unexpectedly or incorrectly.
24
24
25
25
**Note**: For the vNext environment, by default, mailbox audit logs aren't enabled. The feature must be turned on in order for a user to begin a search.
26
26
27
-
## How to run and check mailbox audit logs
27
+
## Run mailbox audit logs
28
28
29
29
Mailbox audit logging lets users obtain information about actions that are performed by non-owners and administrators. Mailbox audit logging is available to members of the Audit Reporting Mailbox self-service group only by using Windows Remote PowerShell.
30
30
31
31
> [!NOTE]
32
-
>
33
-
> - By default, only non-owner mailbox audit logging is enabled, and owner mailbox audit logging is disabled. If you have to perform owner mailbox audit logging to investigate a specific issue, you can temporarily enable the process for two weeks.
34
-
> - Some organizations might not allow you to use mailbox audit logging. In this case, the feature will be turned off for you.
32
+
> Some organizations might not allow you to use mailbox audit logging. In this case, the feature will be turned off for you.
35
33
36
34
To investigate this issue, create and use a Windows PowerShell script by using the sample script that's provided in Step 1 in this section, and then customize a search. By default, you can investigate actions that are performed by non-owners and administrators. This script exports content in a simplified, comma-separated values (.csv) file to help you troubleshoot reports about items that are missing or that were updated unexpectedly.
37
35
@@ -205,7 +203,7 @@ The most useful columns of the .csv file are exported. Some of these columns are
205
203
|OperationResult|Status of the operation</br></br>**Note** Operation results include the following: </br>- Failed </br>- PartiallySucceeded </br>- Succeeded |
206
204
|CrossMailboxOperation|Information about whether the operation that's logged is a cross-mailbox operation (for example, copying or moving messages among mailboxes) |
207
205
208
-
### More information about mailbox audit logging
206
+
### Use Windows Remote PowerShell
209
207
210
208
- The **Search-MailboxAuditLog** cmdlet is used in the sample script in Step 1 to search a single mailbox synchronously. You can do this also by running the cmdlet in Windows Remote PowerShell.
Copy file name to clipboardExpand all lines: Teams/meetings/teams-meeting-with-shared-mailboxes.md
+5-2Lines changed: 5 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,14 +12,17 @@ appliesto:
12
12
- Microsoft Teams
13
13
search.appverid:
14
14
- MET150
15
-
ms.date: 06/23/2025
15
+
ms.date: 10/08/2025
16
16
---
17
17
# Teams meeting features for shared mailboxes
18
18
19
19
For Microsoft Teams meetings that are managed by using a shared mailbox, only a limited number of features are available. The following table lists the details of each feature.
20
20
21
21
> [!NOTE]
22
-
> Shared mailboxes aren't intended for direct login. Keep the shared mailbox account in the **Disabled** state, and avoid resetting its password or signing in by using the shared mailbox user account.
22
+
23
+
> - Keep the shared mailbox account in the **Disabled** state, and avoid resetting its password.
24
+
> - Don't sign in by using the credentials of the shared mailbox user account. Only users that the shared mailbox is shared with can log in with their user credentials.
25
+
> - To create a Teams meeting in a shared mailbox calendar, a valid Teams license must be assigned either to the shared mailbox or to the user who is logged in to the shared mailbox.
Copy file name to clipboardExpand all lines: support/azure/app-service/temporary-storage-for-azure-app-service.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,7 +13,7 @@ If an application is reporting high resource consumption, the source of the prob
13
13
14
14
This video demonstrates how to narrow the scope of your troubleshooting to temporary storage, and the next steps for investigating and troubleshooting performance issues.
Copy file name to clipboardExpand all lines: support/azure/azure-storage/files/file-sync/file-sync-troubleshoot-cloud-tiering.md
+13Lines changed: 13 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -328,6 +328,19 @@ This option doesn't require removing the server endpoint but requires sufficient
328
328
3. Use the *OrphanTieredFiles.txt* output file to identify orphaned tiered files on the server.
329
329
4. Overwrite the orphaned tiered files by copying the full file from the Azure file share to the Windows Server.
330
330
331
+
## How to identify files that are excluded from File Sync
332
+
1. Open a PowerShell window as administrator.
333
+
2. Navigate to the folder. Replace `<volume letter>` and `<syncShare>` with the volume letter and sync share names.
334
+
```powershell
335
+
cd <volume letter>\ <syncShare>\
336
+
```
337
+
3. Run this command:
338
+
```powershell
339
+
dir desktop.ini,thumbs.db,ehthumbs.db,~$*.*,*.laccdb,*.tmp -Recurse -Force -File -ErrorAction Ignore
340
+
```
341
+
342
+
Alternatively, you may use the TreeSize tool. The same list of exclusions can be put into the TreeSize 'filters' configuration to count excluded content. The advantage of this approach is that the content which the administrator does not have access to in case of the former approach will be accessible by TreeSize because it uses the backup/restore permissions when scanning content.
343
+
331
344
## How to troubleshoot files unexpectedly recalled on a server
332
345
333
346
Antivirus, backup, and other applications that read large numbers of files cause unintended recalls unless they respect the skip offline attribute and skip reading the content of those files. Skipping offline files for products that support this option helps avoid unintended recalls during operations like antivirus scans or backup jobs.
Copy file name to clipboardExpand all lines: support/windows-client/windows-tss/collect-data-analyze-troubleshoot-sys-management-components-scenarios.md
0 commit comments