Merge pull request #12013 from MicrosoftDocs/main

Publishing main to live, Friday 10:30AM PDT, 07/19

Author: Stacyrch140

exchange/exchange-ps/exchange/New-AuthenticationPolicy.md

@@ -34,7 +34,6 @@ New-AuthenticationPolicy [[-Name] <String>]
  [-AllowBasicAuthRpc]
  [-AllowBasicAuthSmtp]
  [-AllowBasicAuthWebServices]
- [-AllowLegacyExchangeTokens]
  [-BlockLegacyAuthActiveSync]
  [-BlockLegacyAuthAutodiscover]
  [-BlockLegacyAuthImap]
@@ -333,33 +332,6 @@ Accept pipeline input: False
 Accept wildcard characters: False
 ```
 
-### -AllowLegacyExchangeTokens
-This parameter is available only in the cloud-based service.
-
-The AllowLegacyExchangeTokens switch specifies whether to allow legacy Exchange tokens. You don't need to specify a value with this switch.
-
-Legacy Exchange tokens (for example, Exchange user identity and callback tokens) are used by Outlook add-ins.
-
-**Important**:
-
-- The Microsoft Report Message and Report Phishing add-ins require legacy Exchange tokens to work.
-- Legacy Exchange tokens will eventually be blocked by default in all cloud-based organizations.
-
-For more information about the Report Message and Report Phishing add-ins, see [Enable the Microsoft Report Message or the Report Phishing add-ins](https://learn.microsoft.com/microsoft-365/security/office-365-security/submissions-users-report-message-add-in-configure).
-
-```yaml
-Type: SwitchParameter
-Parameter Sets: (All)
-Aliases:
-Applicable: Exchange Online, Exchange Online Protection
-
-Required: False
-Position: Named
-Default value: True
-Accept pipeline input: False
-Accept wildcard characters: False
-```
-
 ### -BlockLegacyAuthActiveSync
 This parameter is available only in on-premises Exchange.
 

exchange/exchange-ps/exchange/Remove-AuthenticationPolicy.md

@@ -66,7 +66,16 @@ Accept wildcard characters: False
 ### -AllowLegacyExchangeTokens
 This parameter is available only in the cloud-based service.
 
-This parameter is reserved for internal Microsoft use.
+The AllowLegacyExchangeTokens switch specifies whether to allow legacy Exchange tokens. You don't need to specify a value with this switch.
+
+Legacy Exchange tokens (for example, Exchange user identity and callback tokens) are used by Outlook add-ins.
+
+**Important**:
+
+- The Microsoft Report Message and Report Phishing add-ins require legacy Exchange tokens to work.
+- Legacy Exchange tokens will eventually be blocked by default in all cloud-based organizations.
+
+For more information on the Report Message and Report Phishing add-ins, see [Enable the Microsoft Report Message or the Report Phishing add-ins](https://learn.microsoft.com/microsoft-365/security/office-365-security/submissions-users-report-message-add-in-configure).
 
 ```yaml
 Type: SwitchParameter

exchange/exchange-ps/exchange/Set-Place.md

@@ -32,7 +32,6 @@ Set-Place [-Identity] <RecipientIdParameter>
  [-City <String>]
  [-Confirm]
  [-CountryOrRegion <CountryInfo>]
- [-Desks <RecipientIdParameter[]>]
  [-DisplayDeviceName <String>]
  [-Floor <System.Int32>]
  [-FloorLabel <String>]
@@ -198,22 +197,6 @@ Accept pipeline input: False
 Accept wildcard characters: False
 ```
 
-### -Desks
-{{ Fill Desks Description }}
-
-```yaml
-Type: RecipientIdParameter[]
-Parameter Sets: (All)
-Aliases:
-Applicable: Exchange Online
-
-Required: False
-Position: Named
-Default value: None
-Accept pipeline input: False
-Accept wildcard characters: False
-```
-
 ### -DisplayDeviceName
 The DisplayDeviceName parameter specifies the name of the display device in the room. If the value contains spaces, enclose the value in quotation marks (").