Merge branch 'main' into missingdocumentation

Author: michbrown-png

exchange/docs-conceptual/exchange-online-powershell-v2.md

@@ -3,7 +3,7 @@ title: About the Exchange Online PowerShell V3 module
 ms.author: chrisda
 author: chrisda
 manager: deniseb
-ms.date: 07/16/2024
+ms.date: 09/25/2024
 ms.audience: Admin
 audience: Admin
 ms.topic: article
@@ -47,7 +47,7 @@ REST API connections require the PowerShellGet and PackageManagement modules. Fo
 
 Cmdlets in REST API connections have the following advantages over their historical counterparts:
 
-- **More secure**: Built-in support for modern authentication and don't rely on the remote PowerShell session. PowerShell on your client computer doesn't need [Basic authentication in WinRM](#turn-on-basic-authentication-in-winrm).
+- **More secure**: Built-in support for modern authentication and no dependence on the remote PowerShell session. PowerShell on your client computer doesn't need [Basic authentication in WinRM](#turn-on-basic-authentication-in-winrm).
 - **More reliable**: Transient failures use built-in retries, so failures or delays are minimized. For example:
   - Failures due to network delays.
   - Delays due to large queries that take a long time to complete.
@@ -610,14 +610,20 @@ Unless otherwise noted, the current release of the Exchange Online PowerShell mo
 
 ### Current release
 
+#### Version 3.6.0
+
+- **Get-VivaModuleFeature** now returns information about the kinds of identities that the feature supports creating policies for (for example, users, groups, or the entire tenant).
+- Cmdlets for Viva feature access management now handle continuous access evaluation (CAE) claim challenges.
+- Added fix for compatibility issue with the Microsoft.Graph module.
+
+### Previous releases
+
 #### Version 3.5.1
 
 - Bug fixes in **Get-EXOMailboxPermission** and **Get-EXOMailbox**.
 - The module has been upgraded to run on .NET 8, replacing the previous version based on .NET 6.
 - Enhancements in **Add-VivaModuleFeaturePolicy**.
 
-### Previous releases
-
 #### Version 3.5.0
 
 - New **Get-VivaFeatureCategory** cmdlet.

exchange/docs-conceptual/whats-new-in-the-exo-module.md

@@ -3,7 +3,7 @@ title: What's new in the Exchange Online PowerShell module
 ms.author: chrisda
 author: chrisda
 manager: deniseb
-ms.date: 07/16/2024
+ms.date: 09/25/2024
 ms.audience: Admin
 audience: Admin
 ms.topic: article
@@ -22,17 +22,23 @@ description: "Learn about the new features and functionality available in the la
 
 This article lists new features in the Exchange Online PowerShell module that's used for connecting to Exchange Online PowerShell, Security & Compliance PowerShell, and standalone Exchange Online Protection (EOP) PowerShell. Features that are currently in preview are denoted with **(preview)**.
 
+## September 2024
+
+- [Version 3.6.0](https://www.powershellgallery.com/packages/ExchangeOnlineManagement/3.6.0)
+
+  For information about what's in this release, see [Version 3.6.0](exchange-online-powershell-v2.md#version-360).
+
 ## July 2024
 
 - [Version 3.5.1](https://www.powershellgallery.com/packages/ExchangeOnlineManagement/3.5.1) has been released.
 
-  For information about what's in this release, see [Version 3.5.1](exchange-online-powershell-v2.md#version-351)
+  For information about what's in this release, see [Version 3.5.1](exchange-online-powershell-v2.md#version-351).
 
 ## May 2024
 
 - [Version 3.5.0](https://www.powershellgallery.com/packages/ExchangeOnlineManagement/3.5.0) has been released.
 
-  For information about what's in this release, see [Version 3.5.0](exchange-online-powershell-v2.md#version-350)
+  For information about what's in this release, see [Version 3.5.0](exchange-online-powershell-v2.md#version-350).
 
 ## October 2023
 

exchange/exchange-ps/exchange/Add-VivaModuleFeaturePolicy.md

@@ -23,6 +23,7 @@ Use the Add-VivaModuleFeaturePolicy cmdlet to add a new access policy for a spec
 - Policies assigned to a specific user or group take priority over the policy assigned to the entire tenant when determining whether a feature/category is enabled. If a user has multiple policies assigned for a feature/category (directly as a user or member of a group), the most restrictive policy applies.
 - If a category is disabled by category policies, all features under the category are disabled regardless of the policies set at the feature level.
 - You can only update user controls at the feature policy level, not the category policy level.
+- Some features only support policies that apply to the entire tenant, not specific users or groups. You can refer to supported policy scopes for a feature using the [Get-VivaModuleFeature](https://learn.microsoft.com/powershell/module/exchange/get-vivamodulefeature) cmdlet.
 
 Some features include the option for user controls (user opt out). Refer to the feature documentation to see if user controls are available for the feature that you intend to set a policy for.
 

exchange/exchange-ps/exchange/Update-VivaModuleFeaturePolicy.md

@@ -22,6 +22,7 @@ Use the Update-VivaModuleFeaturePolicy cmdlet to update an access policy for a f
 - You can't update a policy for a particular user or group to include the entire tenant if a policy for the entire tenant already exists for the feature. Only one tenant-wide policy is supported.
 - Policies assigned to a specific user or group take priority over the policy assigned to the entire tenant when determining whether a feature/category is enabled. If a user has multiple policies assigned for a feature/category (directly as a user or member of a group), the most restrictive policy applies.
 - You can only update user controls at the feature policy level, not the category policy level.
+- Some features only support policies that apply to the entire tenant, not specific users or groups. You can refer to supported policy scopes for a feature using the [Get-VivaModuleFeature](https://learn.microsoft.com/powershell/module/exchange/get-vivamodulefeature) cmdlet.
 
 Some features include the option for user controls (user opt out). Refer to the feature documentation to see if user controls are available for the feature that you intend to set a policy for.
 

teams/teams-ps/teams/Set-CsTeamsMessagingPolicy.md

@@ -4,10 +4,6 @@ online version: https://learn.microsoft.com/powershell/module/teams/set-csteamsm
 applicable: Microsoft Teams
 title: Set-CsTeamsMessagingPolicy
 schema: 2.0.0
-manager: bulenteg
-author: tomkau
-ms.author: tomkau
-ms.reviewer: williamlooney
 ---
 
 # Set-CsTeamsMessagingPolicy
@@ -21,12 +17,21 @@ The CsTeamsMessagingPolicy cmdlets enable administrators to control if a user is
 ```
 Set-CsTeamsMessagingPolicy [[-Identity] <XdsIdentity>]
  [-Allow [-ReadReceiptsEnabledType <String>]
+ [-AllowChatWithGroup <Boolean>]
+ [-AllowCommunicationComplianceEndUserReporting <Boolean>]
+ [-AllowCustomGroupChatAvatars <Boolean>]
+ [-AllowFluidCollaborate <Boolean>]
+ [-AllowFullChatPermissionUserToDeleteAnyMessage <Boolean>]
  [-AllowGiphy <Boolean>]
+ [-AllowGiphyDisplay <Boolean>]
+ [-AllowGroupChatJoinLinks <Boolean>]
  [-AllowImmersiveReader <Boolean>]
  [-AllowMemes <Boolean>]
  [-AllowOwnerDeleteMessage <Boolean>]
+ [-AllowPasteInternetImage <Boolean>] 
  [-AllowPriorityMessages <Boolean>]
  [-AllowRemoveUser <Boolean>]
+ [-AllowSecurityEndUserReporting <Boolean>]
  [-AllowSmartCompose] <Boolean>]
  [-AllowSmartReply <Boolean>]
  [-AllowStickers <Boolean>]
@@ -36,6 +41,7 @@ Set-CsTeamsMessagingPolicy [[-Identity] <XdsIdentity>]
  [-AllowUserDeleteMessage <Boolean>]
  [-AllowUserEditMessage <Boolean>]
  [-AllowUserTranslation <Boolean>]
+ [-AllowVideoMessages <Boolean>]
  [-AudioMessageEnabledType <AudioMessageEnabledTypeEnum>]
  [-ChannelsInChatListEnabledType <ChannelsInChatListEnabledTypeEnum>]
  [-ChatPermissionRole <String>]
@@ -46,6 +52,7 @@ Set-CsTeamsMessagingPolicy [[-Identity] <XdsIdentity>]
  [-DesignerForBackgroundsAndImages <DesignerForBackgroundsAndImagesTypeEnum>]
  [-Force]
  [-GiphyRatingType <String>]
+ [-InOrganizationChatControl <String>]
  [-Tenant <Guid>]
  [-WhatIf]
  [<CommonParameters>]
@@ -54,12 +61,21 @@ Set-CsTeamsMessagingPolicy [[-Identity] <XdsIdentity>]
 ### Instance
 ```
 Set-CsTeamsMessagingPolicy [-Instance <PSObject>]
+ [-AllowChatWithGroup <Boolean>]
+ [-AllowCommunicationComplianceEndUserReporting <Boolean>]
+ [-AllowCustomGroupChatAvatars <Boolean>]
+ [-AllowFluidCollaborate <Boolean>]
+ [-AllowFullChatPermissionUserToDeleteAnyMessage <Boolean>]
  [-AllowGiphy <Boolean>]
+ [-AllowGiphyDisplay <Boolean>]
+ [-AllowGroupChatJoinLinks <Boolean>]
  [-AllowImmersiveReader <Boolean>]
  [-AllowMemes <Boolean>]
  [-AllowOwnerDeleteMessage <Boolean>]
  [-AllowPriorityMessages <Boolean>]
+ [-AllowPasteInternetImage <Boolean>] 
  [-AllowRemoveUser <Boolean>]
+ [-AllowSecurityEndUserReporting <Boolean>]
  [-AllowSmartCompose] <Boolean>]
  [-AllowSmartReply <Boolean>]
  [-AllowStickers <Boolean>]
@@ -69,6 +85,7 @@ Set-CsTeamsMessagingPolicy [-Instance <PSObject>]
  [-AllowUserDeleteMessage <Boolean>]
  [-AllowUserEditMessage <Boolean>]
  [-AllowUserTranslation <Boolean>]
+ [-AllowVideoMessages <Boolean>]
  [-AudioMessageEnabledType <AudioMessageEnabledTypeEnum>]
  [-ChannelsInChatListEnabledType <ChannelsInChatListEnabledTypeEnum>]
  [-Confirm]
@@ -78,6 +95,7 @@ Set-CsTeamsMessagingPolicy [-Instance <PSObject>]
  [-DesignerForBackgroundsAndImages <DesignerForBackgroundsAndImagesTypeEnum>]
  [-Force]
  [-GiphyRatingType <String>]
+ [-InOrganizationChatControl <String>]
  [-ReadReceiptsEnabledType <String>]
  [-Tenant <Guid>]
  [-WhatIf]
@@ -126,6 +144,88 @@ Accept pipeline input: False
 Accept wildcard characters: False
 ```
 
+### -AllowChatWithGroup
+
+This setting determines if users can chat with groups (Distribution, M365 and Security groups).
+Possible values: True, False
+
+```yaml
+Type: Boolean
+Parameter Sets: (All)
+Aliases:
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -AllowCommunicationComplianceEndUserReporting
+
+This setting determines if users can report offensive messages to their admin for Communication Compliance.
+Possible Values: True, False
+
+```yaml
+Type: Boolean
+Parameter Sets: (All)
+Aliases:
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -AllowCustomGroupChatAvatars
+These settings enables, disables updating or fetching custom group chat avatars for the users included in the messaging policy.
+Possible values: True, False
+
+```yaml
+Type: Boolean
+Parameter Sets: (All)
+Aliases:
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -AllowFluidCollaborate
+This field enables or disables Fluid Collaborate feature for users.
+Possible values: True, False
+
+```yaml
+Type: Boolean
+Parameter Sets: (All)
+Aliases:
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -AllowFullChatPermissionUserToDeleteAnyMessage
+This setting determines if users with the 'Full permissions' role can delete any group or meeting chat message within their tenant.
+Possible values: True, False
+
+```yaml
+Type: Boolean
+Parameter Sets: (All)
+Aliases:
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
 ### -AllowGiphy
 Determines whether a user is allowed to access and post Giphys. Set this to TRUE to allow. Set this FALSE to prohibit.
 
@@ -143,6 +243,38 @@ Accept pipeline input: False
 Accept wildcard characters: False
 ```
 
+### -AllowGiphyDisplay
+Determines if Giphy images should be displayed that had been already sent or received in chat. 
+Possible values: True, False
+
+```yaml
+Type: Boolean
+Parameter Sets: (All)
+Aliases:
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -AllowGroupChatJoinLinks
+This setting determines if users in a group chat can create and share join links for other users within the organization to join that chat.
+Possible values: True, False
+
+```yaml
+Type: Boolean
+Parameter Sets: (All)
+Aliases:
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
 ### -AllowImmersiveReader
 Determines whether a user is allowed to use Immersive Reader for reading conversation messages. Set this to TRUE to allow. Set this FALSE to prohibit.
 
@@ -188,8 +320,40 @@ Accept pipeline input: False
 Accept wildcard characters: False
 ```
 
+### -AllowPasteInternetImage
+Determines if a user is allowed to paste internet-based images in compose. 
+Possible values: True, False
+
+```yaml
+Type: Boolean
+Parameter Sets: (All)
+Aliases:
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
 ### -AllowPriorityMessages
-Determines whether a user is allowed to send priorities messages. Set this to TRUE to allow. Set this FALSE to prohibit.
+Determines whether a user is allowed to send priority messages. Set this to TRUE to allow. Set this FALSE to prohibit.
+
+```yaml
+Type: Boolean
+Parameter Sets: (All)
+Aliases:
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -AllowSecurityEndUserReporting
+This setting determines if users can report any security concern posted in message to their admin.
+Possible values: True, False
 
 ```yaml
 Type: Boolean
@@ -355,6 +519,22 @@ Accept pipeline input: False
 Accept wildcard characters: False
 ```
 
+### -AllowVideoMessages
+This setting determines if users can create and send video messages.
+Possible values: True, False
+
+```yaml
+Type: Boolean
+Parameter Sets: (All)
+Aliases:
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
 ### -AudioMessageEnabledType
 Determines whether a user is allowed to send audio messages. Possible values are: ChatsAndChannels, ChatsOnly, Disabled.
 
@@ -520,6 +700,21 @@ Accept pipeline input: False
 Accept wildcard characters: False
 ```
 
+### -InOrganizationChatControl
+This setting determines if chat regulation for internal communication in the tenant is allowed.
+
+```yaml
+Type: String
+Parameter Sets: (All)
+Aliases:
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
 ### -ReadReceiptsEnabledType
 Use this setting to specify whether read receipts are user controlled, enabled for everyone, or disabled. Set this to UserPreference, Everyone or None.