New-TenantAllowBlockListSpoofItems
This cmdlet is available only in the cloud-based service.
Use the New-TenantAllowBlockListSpoofItems cmdlet to create spoofed sender entries in the Tenant Allow/Block List.
For information about the parameter sets in the Syntax section below, see Exchange cmdlet syntax.
Syntax
New-TenantAllowBlockListSpoofItems
[-Identity] <HostedConnectionFilterPolicyIdParameter>
-Action <String>
-SendingInfrastructure <String>
-SpoofedUser <String>
-SpoofType <String>
[-Confirm]
[-WhatIf]
[<CommonParameters>] Description
This cmdlet adds a spoof pair (the combination of the spoofed user and the sending infrastructure) to the Tenant Allow/Block List.
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.
Examples
Example 1
New-TenantAllowBlockListSpoofItems -Identity Default -Action Allow -SendingInfrastructure contoso.com -SpoofedUser bob@contoso.com -SpoofType ExternalThis example creates an allow entry for the sender bob@contoso.com from the source contoso.com.
Parameters
-Action
The Action parameter specifies whether is an allowed or blocked spoofed sender entry. Valid values are:
- Allow
- Block
| Type: | String |
| Position: | Named |
| Default value: | None |
| Required: | True |
| Accept pipeline input: | False |
| Accept wildcard characters: | False |
| Applies to: | Exchange Online, Security & Compliance, Exchange Online Protection |
-Confirm
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax:
-Confirm:$false. - Most other cmdlets (for example, New-* and Set-* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding.
| Type: | SwitchParameter |
| Aliases: | cf |
| Position: | Named |
| Default value: | None |
| Required: | False |
| Accept pipeline input: | False |
| Accept wildcard characters: | False |
| Applies to: | Exchange Online, Security & Compliance, Exchange Online Protection |
-Identity
The Identity parameter uses the value Default.
| Type: | HostedConnectionFilterPolicyIdParameter |
| Position: | 0 |
| Default value: | None |
| Required: | True |
| Accept pipeline input: | True |
| Accept wildcard characters: | False |
| Applies to: | Exchange Online, Security & Compliance, Exchange Online Protection |
-SendingInfrastructure
The SendingInfrastructure parameter specifies the source of the messages sent by the spoofed sender that's defined in the SpoofedUser parameter. Valid values are:
- An email domain (for example contoso.com). The domain is found in the reverse DNS lookup (PTR record) of the source email server's IP address.
- An IP address using the syntax: <source IP>/24 (for example, 192.168.100.100/24). Use the IP address if the source IP address has no PTR record. /24 is the only available and maximum subnet depth.
- A verified DKIM domain.
| Type: | String |
| Position: | Named |
| Default value: | None |
| Required: | True |
| Accept pipeline input: | False |
| Accept wildcard characters: | True |
| Applies to: | Exchange Online, Security & Compliance, Exchange Online Protection |
-SpoofedUser
The SpoofedUser parameter specifies the email address or domain for the spoofed sender entry.
- For domains outside your organization (cross-org), use the domain of the email address that appears in the From field of the message.
- For domains inside your organization (intra-org), use the full email address that appears in the From field of the message.
For spoofed senders, the maximum number of entries is 1024.
| Type: | String |
| Position: | Named |
| Default value: | None |
| Required: | True |
| Accept pipeline input: | False |
| Accept wildcard characters: | True |
| Applies to: | Exchange Online, Security & Compliance, Exchange Online Protection |
-SpoofType
The SpoofType parameter specifies whether this is an internal or external spoofed sender entry. Valid values are:
- External
- Internal
| Type: | String |
| Position: | Named |
| Default value: | None |
| Required: | True |
| Accept pipeline input: | False |
| Accept wildcard characters: | False |
| Applies to: | Exchange Online, Security & Compliance, Exchange Online Protection |
-WhatIf
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
| Type: | SwitchParameter |
| Aliases: | wi |
| Position: | Named |
| Default value: | None |
| Required: | False |
| Accept pipeline input: | False |
| Accept wildcard characters: | False |
| Applies to: | Exchange Online, Security & Compliance, Exchange Online Protection |