Merge branch 'main' into TABL-chrisda

Author: chrisda

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/Get-ConnectionInformation.md

@@ -46,7 +46,7 @@ The output of the cmdlet contains the following properties:
 - Id: An integer that identifies the session in the PowerShell window. The first connection is 1, the second is 2, etc.
 - Name: A unique name that's based on the PowerShell environment and Id value. For example, ExchangeOnline_1 for Exchange Online PowerShell or ExchangeOnlineProtection_1 for Security & Compliance PowerShell.
 - UserPrincipalName: The account that was used to connect. For example, `laura@contoso.onmicrosoft.com`.
-- ConnectionUri: The connection endpoint that was used. For example, <https://outlook.office365.com> for Exchange Online PowerShell or <https://nam12b.ps.compliance.protection.outlook.com> for Security & Compliance PowerShell.
+- ConnectionUri: The connection endpoint that was used. For example, `https://outlook.office365.com` for Exchange Online PowerShell or `https://nam12b.ps.compliance.protection.outlook.com` for Security & Compliance PowerShell.
 - AzureAdAuthorizationEndpointUri : The Microsoft Entra authorization endpoint for the connection. For example, `https://login.microsoftonline.com/organizations` for Exchange Online PowerShell or `https://login.microsoftonline.com/organizations` for Security & Compliance PowerShell.
 - TokenExpiryTimeUTC: When the connection token expires. For example, 9/30/2023 6:42:24 PM +00:00.
 - CertificateAuthentication: Whether certificate based authentication (also known as CBA or app-only authentication) was used to connect. Values are True or False.

exchange/exchange-ps/exchange/Get-MessageTrackingLog.md

@@ -59,10 +59,17 @@ You need to be assigned permissions before you can run this cmdlet. Although thi
 
 ### Example 1
 ```powershell
-Get-MessageTrackingLog -Server Mailbox01 -Start "03/13/2018 09:00:00" -End "03/15/2018 17:00:00" -Sender "john@contoso.com"
+Get-MessageTrackingLog -Server Mailbox01 -Start "03/13/2024 09:00:00" -End "03/15/2024 17:00:00" -Sender "john@contoso.com"
 ```
 
-This example searches the message tracking logs on the Mailbox server named Mailbox01 for information about all messages sent from March 13, 2018, 09:00 to March 15, 2018, 17:00 by the sender john@contoso.com.
+This example searches the message tracking logs on the Mailbox server named Mailbox01 for information about all messages sent from March 13, 2024, 09:00 to March 15, 2024, 17:00 by the sender john@contoso.com.
+
+### Example 2
+```powershell
+Get-MessageTrackingLog -Server Mailbox01 -Start "03/13/2024 09:00:00" -Recipients @("john@contoso.com","alice@contoso.com")
+```
+
+This example searches the message tracking logs on the Mailbox server named Mailbox01 for information about all messages sent from March 13, 2024, 09:00 to today for the recipients john@contoso.com and/or alice@contoso.com.
 
 ## PARAMETERS
 
@@ -169,7 +176,7 @@ Accept wildcard characters: False
 ```
 
 ### -Recipients
-The Recipients parameter filters the message tracking log entries by the SMTP email address of the message recipients. Multiple recipients in a single message are logged in a single message tracking log entry. Unexpanded distribution group recipients are logged by using the group's SMTP email address. You can specify multiple recipient email addresses separated by commas.
+The Recipients parameter filters the message tracking log entries by the SMTP email address of the message recipients. Multiple recipients in a single message are logged in a single message tracking log entry. Unexpanded distribution group recipients are logged by using the group's SMTP email address. You can specify multiple recipients using an array of email addresses.
 
 ```yaml
 Type: String[]

exchange/exchange-ps/exchange/Set-DistributionGroup.md

@@ -1447,10 +1447,10 @@ Accept wildcard characters: False
 ```
 
 ### -ReportToManagerEnabled
-The ReportToManagerEnabled parameter specifies whether delivery status notifications (also known as DSNs, non-delivery reports, NDRs, or bounce messages) are sent to the owners of the group (defined by the ManagedBy property). Valid values are:
+The ReportToManagerEnabled parameter specifies whether delivery status notifications (also known as DSNs, non-delivery reports, NDRs, or bounce messages) are sent to the owner (first one listed if more than one) of the group (defined by the ManagedBy property). Valid values are:
 
-- $true: Delivery status notifications are sent to the owners of the group.
-- $false: Delivery status notifications aren't sent to the owners of the group. This is the default value.
+- $true: Delivery status notifications are sent to the owner (first one listed if more than one) of the group.
+- $false: Delivery status notifications aren't sent to the owner (first one listed if more than one) of the group. This is the default value.
 
 The ReportToManagerEnabled and ReportToOriginatorEnabled parameters affect the return path for messages sent to the group. Some email servers reject messages that don't have a return path. Therefore, you should set one parameter to $false and one to $true, but not both to $false or both to $true.
 

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/New-CsTeamsCallingPolicy.md

@@ -26,7 +26,7 @@ New-CsTeamsCallingPolicy [-Identity] <string> [-Description <string>] [-AllowPri
  [-BusyOnBusyEnabledType <string>] [-MusicOnHoldEnabledType <string>] [-AllowCloudRecordingForCalls <boolean>]
  [-AllowTranscriptionForCalling <boolean>] [-PopoutForIncomingPstnCalls <string>] [-PopoutAppPathForIncomingPstnCalls <string>]
  [-LiveCaptionsEnabledTypeForCalling <string>] [-AutoAnswerEnabledType <string>] [-SpamFilteringEnabledType <string>]
- [-CallRecordingExpirationDays <long>] [-AllowCallRedirect <string>]
+ [-CallRecordingExpirationDays <long>] [-AllowCallRedirect <string>] [-EnableWebPstnMediaBypass <Boolean>]
  [-InboundPstnCallRoutingTreatment <string>] [-InboundFederatedCallRoutingTreatment <string>] [-Force] [-WhatIf] [-Confirm] [<CommonParameters>]
 ```
 
@@ -308,6 +308,21 @@ Accept pipeline input: False
 Accept wildcard characters: False
 ```
 
+### -EnableWebPstnMediaBypass
+ Determines if MediaBypass is enabled for PSTN calls on specified Web platforms.
+
+```yaml
+Type: Boolean
+Parameter Sets: (All)
+Aliases:
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
 ### -Identity
 Name of the policy instance being created.
 

teams/teams-ps/teams/New-CsTeamsEmergencyCallRoutingPolicy.md

@@ -34,7 +34,15 @@ New-CsTeamsEmergencyCallRoutingPolicy -Identity "Test" -EmergencyNumbers @{add=$
 ```
 
 This example first creates a new Teams emergency number object and then creates a Teams Emergency Call Routing policy with this emergency number object.
-Note that the OnlinePSTNUsage specified in the first command must previously exist. Note that the resulting object from the New-CsTeamsEmergencyNumber only exists in memory, so you must apply it to a policy to be used.
+Note that the OnlinePSTNUsage specified in the first command must previously exist. Note that the resulting object from the New-CsTeamsEmergencyNumber only exists in memory, so you must apply it to a policy to be used. 
+Note that {@add=....} will try to append a new emergency number to the values taken from the global instance.
+
+### Example 2
+```powershell
+$en1 =  New-CsTeamsEmergencyNumber -EmergencyDialString "911" -EmergencyDialMask "933" -OnlinePSTNUsage "USE911"
+New-CsTeamsEmergencyCallRoutingPolicy -Identity "testecrp" -EmergencyNumbers $en1 -AllowEnhancedEmergencyServices:$true -Description "test"
+```
+This example overrides the global emergency numbers from the global instance.
 
 ## PARAMETERS
 

teams/teams-ps/teams/Set-CsExternalAccessPolicy.md

@@ -4,8 +4,6 @@ online version: https://learn.microsoft.com/powershell/module/teams/set-csextern
 applicable: Microsoft Teams
 title: Set-CsExternalAccessPolicy
 schema: 2.0.0
-author: tomkau
-ms.author: tomkau
 ms.reviewer: rogupta
 ---
 
@@ -24,13 +22,15 @@ This cmdlet was introduced in Lync Server 2010.
 Set-CsExternalAccessPolicy [-Tenant <Guid>] [-Description <String>] [-EnableFederationAccess <Boolean>] [-EnableAcsFederationAccess <Boolean>]
  [-EnableXmppAccess <Boolean>] [-EnablePublicCloudAccess <Boolean>]
  [-EnablePublicCloudAudioVideoAccess <Boolean>] [-EnableTeamsConsumerAccess <Boolean>] [-EnableTeamsConsumerInbound <Boolean>] [-EnableOutsideAccess <Boolean>] [[-Identity] <XdsIdentity>]
+ [-RestrictTeamsConsumerAccessToExternalUserProfiles <Boolean>] [-EnableTeamsSmsAccess <Boolean>]
  [-Force] [-WhatIf] [-Confirm] [<CommonParameters>]
 ```
 
 ### Instance
 ```
 Set-CsExternalAccessPolicy [-Tenant <Guid>] [-Description <String>] [-EnableFederationAccess <Boolean>] [-EnableAcsFederationAccess <Boolean>]
  [-EnableXmppAccess <Boolean>] [-EnablePublicCloudAccess <Boolean>]
+ [-RestrictTeamsConsumerAccessToExternalUserProfiles <Boolean>] [-EnableTeamsSmsAccess <Boolean>]
  [-EnablePublicCloudAudioVideoAccess <Boolean>] [-EnableTeamsConsumerAccess <Boolean>] [-EnableTeamsConsumerInbound <Boolean>] [-EnableOutsideAccess <Boolean>] [-Instance <PSObject>]
  [-Force] [-WhatIf] [-Confirm] [<CommonParameters>]
 ```
@@ -397,6 +397,38 @@ Accept pipeline input: False
 Accept wildcard characters: False
 ```
 
+### -EnableTeamsSmsAccess
+Allows you to control whether users can have SMS text messaging capabilities within Teams.
+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
+```
+
+### -RestrictTeamsConsumerAccessToExternalUserProfiles
+Defines if a user is restriced to collaboration with Teams Consumer (TFL) user only in Extended Directory
+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
+```
+
 ### CommonParameters
 This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction, and -WarningVariable. For more information, see about_CommonParameters (https://go.microsoft.com/fwlink/?LinkID=113216).
 

teams/teams-ps/teams/Set-CsTeamsAIPolicy.md

@@ -18,23 +18,40 @@ This cmdlet Set Teams AI policy value for current tenant.
 ## SYNTAX
 
 ```
-Set-CsTeamsAIPolicy -Identity <string> -EnrollVoice <Enabled/Disabled>
+Set-CsTeamsAIPolicy 
+    [[-Identity] <string>] 
+    [-EnrollFace <Enabled/Disabled>]
+    [-EnrollVoice <Enabled/Disabled>]
 ```
 
 ## DESCRIPTION
 
-This cmdlet sets the Teams AI policy EnrollFace and EnrollVoice value for the tenant. The values of EnrollFace and EnrollVoice can be set to "Enabled" or "Disabled"
+This cmdlet sets the Teams AI policy EnrollFace and EnrollVoice value for the tenant. The values of EnrollFace and EnrollVoice can be set to "Enabled" or "Disabled".
 
 ## EXAMPLES
 
 ### Example 1
 ```powershell
+PS C:\> Set-CsTeamsAIPolicy -Identity Test -EnrollFace Enabled
+```
+
+Set Teams AI policy "EnrollFace" value to "Enabled" for identity "Test".
+
+### Example 2
+```powershell
+PS C:\> Set-CsTeamsAIPolicy -Identity Test -EnrollVoice Enabled
+```
+
+Set Teams AI policy "EnrollVoice" value to "Enabled" for identity "Test".
+
+### Example 3
+```powershell
 PS C:\> Set-CsTeamsAIPolicy -Identity Test -EnrollFace Disabled
 ```
 
 Set Teams AI policy "EnrollFace" value to "Disabled" for identity "Test".
 
-### Example 2
+### Example 4
 ```powershell
 PS C:\> Set-CsTeamsAIPolicy -Identity Test -EnrollVoice Disabled
 ```
@@ -57,7 +74,7 @@ Accept pipeline input: False
 Accept wildcard characters: False
 ```
 ### -EnrollFace
-Policy value of the Teams AI EnrollFace policy.
+Policy value of the Teams AI EnrollFace policy. EnrollFace controls user access to user face enrollment in the Teams app settings.
 
 ```yaml
 Type: Boolean
@@ -72,7 +89,7 @@ Accept wildcard characters: False
 ```
 
 ### -EnrollVoice
-Policy value of the Teams AI EnrollVoice policy.
+Policy value of the Teams AI EnrollVoice policy. EnrollVoice controls user access to user voice enrollment in the Teams app settings.
 
 ```yaml
 Type: Boolean

teams/teams-ps/teams/Set-CsTeamsFeedbackPolicy.md

@@ -4,10 +4,6 @@ online version: https://learn.microsoft.com/powershell/module/teams/set-csteamsf
 applicable: Microsoft Teams
 title: Set-CsTeamsFeedbackPolicy
 schema: 2.0.0
-manager: bulenteg
-ms.author: tomkau
-ms.author: tomkau
-ms.reviewer:
 ---
 
 # Set-CsTeamsFeedbackPolicy
@@ -21,7 +17,7 @@ Use this cmdlet to modify a Teams feedback policy (the ability to send feedback
 ```
 Set-CsTeamsFeedbackPolicy [-WhatIf] [-Confirm] [[-Identity] <Object>] [-Tenant <Object>]
  [-ReceiveSurveysMode <String>] [-UserInitiatedMode <String>] [-AllowEmailCollection <Boolean>]
- [-AllowLogCollection <Boolean>] [-AllowScreenshotCollection <Boolean>]
+ [-AllowLogCollection <Boolean>] [-AllowScreenshotCollection <Boolean>] [-EnableFeatureSuggestions <Boolean>] 
  [-Force] [-Instance <Object>]
 ```
 
@@ -200,6 +196,22 @@ Accept pipeline input: False
 Accept wildcard characters: False
 ```
 
+### -EnableFeatureSuggestions
+This setting will enable Tenant Admins to hide or show the Teams menu item "Help | Suggest a Feature".
+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
+```
+
 ### -WhatIf
 Shows what would happen if the cmdlet runs.
 The cmdlet is not run.