Merge pull request #13192 from MicrosoftDocs/main

[AutoPublish] main to live - 10/23 10:31 PDT | 10/23 23:01 IST

Author: m365-skilling-repo-management[bot]

exchange/exchange-ps/ExchangePowerShell/New-DlpComplianceRule.md

@@ -3471,9 +3471,9 @@ Accept wildcard characters: False
 
 The SenderAddressLocation parameter specifies where to look for sender addresses in conditions and exceptions that examine sender email addresses. Valid values are:
 
-- Header: Only examine senders in the message headers (for example, the From, Sender, or Reply-To fields). This value is the default.
-- Envelope: Only examine senders from the message envelope (the MAIL FROM value that was used in the SMTP transmission, which is typically stored in the Return-Path field).
-- HeaderOrEnvelope: Examine senders in the message header and the message envelope.
+- Header: Only examine senders in the message headers (the From field). This value is the default.
+- Envelope: Only examine senders from the message envelope (the MAIL FROM value used in SMTP message transmission, which is typically stored in the Return-Path field).
+- HeaderOrEnvelope: Examine senders in the message header (the From field) and the message envelope (the Return-Path field).
 
 Message envelope searching is available only for the following conditions and exceptions:
 

exchange/exchange-ps/ExchangePowerShell/New-TransportRule.md

@@ -4799,9 +4799,9 @@ Accept wildcard characters: False
 
 The SenderAddressLocation parameter specifies where to look for sender addresses in conditions and exceptions that examine sender email addresses. Valid values are:
 
-- Header: Only examine senders in the message headers. For example, in on-premises Exchange the From, Sender, or Reply-To fields. In Exchange Online, the From field only. This value is the default, and is the way rules worked before Exchange 2013 Cumulative Update 1 (CU1).
-- Envelope: Only examine senders from the message envelope (the MAIL FROM value that was used in the SMTP transmission, which is typically stored in the Return-Path field).
-- HeaderOrEnvelope: Examine senders in the message header and the message envelope.
+- Header: Only examine senders in the message headers (the From field). This value is the default, how rules worked before Exchange 2013 Cumulative Update 1 (CU1).
+- Envelope: Only examine senders from the message envelope (the MAIL FROM value used in SMTP message transmission, which is typically stored in the Return-Path field).
+- HeaderOrEnvelope: Examine senders in the message header (the From field) and the message envelope (the Return-Path field).
 
 Message envelope searching is available only for the following conditions and exceptions:
 

exchange/exchange-ps/ExchangePowerShell/Set-DlpComplianceRule.md

@@ -3340,9 +3340,9 @@ Accept wildcard characters: False
 
 The SenderAddressLocation parameter specifies where to look for sender addresses in conditions and exceptions that examine sender email addresses. Valid values are:
 
-- Header: Only examine senders in the message headers (for example, the From, Sender, or Reply-To fields). This value is the default.
-- Envelope: Only examine senders from the message envelope (the MAIL FROM value that was used in the SMTP transmission, which is typically stored in the Return-Path field).
-- HeaderOrEnvelope: Examine senders in the message header and the message envelope.
+- Header: Only examine senders in the message headers (the From field). This value is the default.
+- Envelope: Only examine senders from the message envelope (the MAIL FROM value used in SMTP message transmission, which is typically stored in the Return-Path field).
+- HeaderOrEnvelope: Examine senders in the message header (the From field) and the message envelope (the Return-Path field).
 
 Message envelope searching is available only for the following conditions and exceptions:
 

exchange/exchange-ps/ExchangePowerShell/Set-PolicyConfig.md

@@ -686,9 +686,9 @@ Accept wildcard characters: False
 
 The SenderAddressLocation parameter specifies where to look for sender addresses in conditions and exceptions that examine sender email addresses. Valid values are:
 
-- Header: Only examine senders in the message headers (for example, the From, Sender, or Reply-To fields). This value is the default.
-- Envelope: Only examine senders from the message envelope (the MAIL FROM value that was used in the SMTP transmission, which is typically stored in the Return-Path field).
-- HeaderOrEnvelope: Examine senders in the message header and the message envelope.
+- Header: Only examine senders in the message headers (the From field). This value is the default.
+- Envelope: Only examine senders from the message envelope (the MAIL FROM value used in SMTP message transmission, which is typically stored in the Return-Path field).
+- HeaderOrEnvelope: Examine senders in the message header (the From field) and the message envelope (the Return-Path field).
 
 ```yaml
 Type: PolicySenderAddressLocation

exchange/exchange-ps/ExchangePowerShell/Set-TransportRule.md

@@ -4792,9 +4792,9 @@ Accept wildcard characters: False
 
 The SenderAddressLocation parameter specifies where to look for sender addresses in conditions and exceptions that examine sender email addresses. Valid values are:
 
-- Header: Only examine senders in the message headers. For example, in on-premises Exchange the the From, Sender, or Reply-To fields. In Exchange Online, the From field only. This value is the default, and is the way rules worked before Exchange 2013 Cumulative Update 1 (CU1).
-- Envelope: Only examine senders from the message envelope (the MAIL FROM value that was used in the SMTP transmission, which is typically stored in the Return-Path field).
-- HeaderOrEnvelope: Examine senders in the message header and the message envelope.
+- Header: Only examine senders in the message headers (the From field). This value is the default, and how rules worked before Exchange 2013 Cumulative Update 1 (CU1).
+- Envelope: Only examine senders from the message envelope (the MAIL FROM value used in SMTP message transmission, which is typically stored in the Return-Path field).
+- HeaderOrEnvelope: Examine senders in the message header (the From field) and the message envelope (the Return-Path field).
 
 Message envelope searching is available only for the following conditions and exceptions:
 

teams/teams-ps/MicrosoftTeams/New-CsAutoAttendantCallFlow.md

@@ -20,7 +20,7 @@ Use the New-CsAutoAttendantCallFlow cmdlet to create a new call flow.
 ## SYNTAX
 
 ```powershell
-New-CsAutoAttendantCallFlow -Name <String> -Menu <Object> [-Greetings <List>] [-Tenant <Guid>] [-ForceListenMenuEnabled] [<CommonParameters>]
+New-CsAutoAttendantCallFlow -Name <String> -Menu <Object> [-Greetings <List>] [-ForceListenMenuEnabled] [-RingResourceAccountDelegates <Boolean>] [-Tenant <Guid>] [<CommonParameters>]
 ```
 
 ## DESCRIPTION

teams/teams-ps/MicrosoftTeams/New-CsAutoAttendantMenuOption.md

@@ -20,7 +20,7 @@ Use the New-CsAutoAttendantMenuOption cmdlet to create a new menu option.
 ## SYNTAX
 
 ```
-New-CsAutoAttendantMenuOption -Action <AgentAndQueues | Announcement | DisconnectCall | MainlineAttendantFlow | TransferCallToOperator | TransferCallToTarget>] [-DtmfResponse <Tone0 | Tone1 | Tone2 | Tone3 | Tone4 | Tone5 | Tone6 | Tone7 | Tone8 | Tone9 | Automatic>] [-VoiceResponses <List>] [-CallTarget <Object>] [-Prompt <Object>] [-MainlineAttendantTarget <String>] [-Description <String>] [-AgentTargetType <Copilot | IVR>] [-AgentTarget <String>] [-AgentTargetTagTemplateId <String>] [-Tenant <Guid>] [<CommonParameters>]
+New-CsAutoAttendantMenuOption -Action <List> [-DtmfResponse <List>] [-VoiceResponses <List>] [-CallTarget <Object>] [-Prompt <Object>] [-MainlineAttendantTarget <String>] [-Description <String>] [-AgentTargetType <List>] [-AgentTarget <String>] [-AgentTargetTagTemplateId <String>] [-Tenant <Guid>] [<CommonParameters>]
 ```
 
 ## DESCRIPTION
@@ -33,6 +33,9 @@ The New-CsAutoAttendantMenuOption cmdlet creates a new menu option for the Auto
 > - -Action AgentAndQueues
 > - -Action MainLineAttendantFlow
 > - -MainlineAttendantTarget
+> - -AgentTargetType
+> - -AgentTarget
+> - -AgentTargetTagTemplateId
 
 ## EXAMPLES