Skip to content

Clarify RejectDirectSend parameter usage in Set-OrganizationConfig #13210

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Oct 30, 2025
Merged

Clarify RejectDirectSend parameter usage in Set-OrganizationConfig #13210

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
2041d3a
Clarify RejectDirectSend parameter usage in Set-OrganizationConfig
oriolcomasGH Oct 30, 2025
879bd68
Update Set-OrganizationConfig.md
chrisda Oct 30, 2025
3afbffe
Merge branch 'main' into patch-1
chrisda Oct 30, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 8 additions & 1 deletion exchange/exchange-ps/ExchangePowerShell/Set-OrganizationConfig.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4050,7 +4050,14 @@ Accept wildcard characters: False

This parameter is available only in the cloud-based service.

{{ Fill RejectDirectSend Description }}
The RejectDirectSend parameter specifies whether to block Direct Send in your organization. Valid values are:

- $true: Direct Send is blocked. Exchange Online rejects anonymous messages sent from your own domain to your organization's mailboxes when the following conditions are met:

• The anonymous incoming messages don't match any Inbound connector.
• The domain in the MAIL FROM address (also known as the `5321.MailFrom` address, P1 sender, or envelope sender) is an accepted domain in your organization.

- $false: Direct Send isn't blocked.

```yaml
Type: Boolean
Expand Down