Skip to content

Commit 9acb958

Browse files
authored
Merge pull request MicrosoftDocs#6117 from MicrosoftDocs/chrisda
Update Get-MailboxAuditBypassAssociation.md
2 parents edff942 + 92aa735 commit 9acb958

File tree

1 file changed

+27
-19
lines changed

1 file changed

+27
-19
lines changed

exchange/exchange-ps/exchange/Get-MailboxAuditBypassAssociation.md

Lines changed: 27 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 ||
1515
## SYNOPSIS
1616
This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
1717

18-
Use the Get-MailboxAuditBypassAssociation cmdlet to retrieve user or computer accounts configured to bypass mailbox audit logging.
18+
Use the Get-MailboxAuditBypassAssociation cmdlet to retrieve information about the AuditBypassEnabled property value for user accounts (on-premises Exchange and the cloud) and computer accounts (on-premises Exchange only). You use the [Set-MailboxAuditBypassAssociation](https://docs.microsoft.com/powershell/module/exchange/set-mailboxauditbypassassociation) cmdlet to enable this property to bypass mailbox audit logging.
1919

2020
For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-cmdlet-syntax).
2121

@@ -27,59 +27,67 @@ Get-MailboxAuditBypassAssociation [[-Identity] <MailboxAuditBypassAssociationIdP
2727
```
2828

2929
## DESCRIPTION
30-
When you configure a user or computer account to bypass mailbox audit logging, access or actions taken by the user or computer account to any mailbox isn't logged. By bypassing trusted user or computer accounts that need to access mailboxes frequently, you can reduce the noise in mailbox audit logs.
30+
When you configure a user or computer account to bypass mailbox audit logging, access or actions taken by the user account or computer account to any mailbox isn't logged. By bypassing trusted user accounts or computer accounts that need to access mailboxes frequently, you can reduce the noise in mailbox audit logs.
3131

3232
You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
3333

3434
## EXAMPLES
3535

3636
### Example 1
3737
```powershell
38-
Get-MailboxAuditBypassAssociation -ResultSize unlimited
38+
Get-MailboxAuditBypassAssociation -ResultSize unlimited | Format-Table Name,AuditBypassEnabled
3939
```
4040

41-
This example retrieves all user or computer accounts configured for mailbox audit logging bypass.
41+
This example returns all accounts and whether they are configured or not configured for mailbox audit logging bypass.
4242

4343
### Example 2
4444
```powershell
4545
Get-MailboxAuditBypassAssociation -Identity "Svc-MyApplication"
4646
```
4747

48-
This example retrieves the mailbox audit bypass association for the Svc-MyApplication account.
48+
This example returns the status of the AuditBypassEnabled property for the Svc-MyApplication account.
4949

50-
## PARAMETERS
50+
### Example 3
51+
```powershell
52+
$MBX = Get-MailboxAuditBypassAssociation -ResultSize unlimited
53+
$MBX | where {$_.AuditBypassEnabled -eq $true} | Format-Table Name,AuditBypassEnabled
54+
```
5155

52-
### -DomainController
53-
This parameter is available only in on-premises Exchange.
56+
This example returns all accounts that are configured for mailbox audit logging bypass.
5457

55-
The DomainController parameter specifies the ___domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the ___domain controller by its fully qualified ___domain name (FQDN). For example, dc01.contoso.com.
58+
## PARAMETERS
59+
60+
### -Identity
61+
The Identity parameter specifies the user account or computer account where you want to view the value of the AuditBypassEnabled property.
5662

5763
```yaml
58-
Type: Fqdn
64+
Type: MailboxAuditBypassAssociationIdParameter
5965
Parameter Sets: (All)
6066
Aliases:
61-
Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
67+
Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
6268

6369
Required: False
64-
Position: Named
70+
Position: 1
6571
Default value: None
66-
Accept pipeline input: False
72+
Accept pipeline input: True
6773
Accept wildcard characters: False
6874
```
6975
70-
### -Identity
71-
The Identity parameter specifies a user or computer account to retrieve audit logging bypass association for.
76+
### -DomainController
77+
This parameter is available only in on-premises Exchange.
78+
79+
The DomainController parameter specifies the ___domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the ___domain controller by its fully qualified ___domain name (FQDN). For example, dc01.contoso.com.
7280
7381
```yaml
74-
Type: MailboxAuditBypassAssociationIdParameter
82+
Type: Fqdn
7583
Parameter Sets: (All)
7684
Aliases:
77-
Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
85+
Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
7886

7987
Required: False
80-
Position: 1
88+
Position: Named
8189
Default value: None
82-
Accept pipeline input: True
90+
Accept pipeline input: False
8391
Accept wildcard characters: False
8492
```
8593

0 commit comments

Comments
 (0)