Skip to content

Commit 6865bd9

Browse files
Merge pull request #13351 from williamlooney/master
Pre-release version of RequireMutualFederationForChatMembership and ApplyExternalAccessRestrictionsToChatMembership docs
2 parents b743e36 + e2e43f5 commit 6865bd9

1 file changed

Lines changed: 65 additions & 3 deletions

File tree

teams/teams-ps/MicrosoftTeams/Set-CsTenantFederationConfiguration.md

Lines changed: 65 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -30,6 +30,8 @@ Set-CsTenantFederationConfiguration [-Tenant <Guid>]
3030
[-AllowedDomainsAsAList <List>] [-ExternalAccessWithTrialTenants <ExternalAccessWithTrialTenantsType>]
3131
[-SecurityTeamAllowBlockListDelegation <SecurityTeamAllowBlockListDelegationType>]
3232
[-AllowedTrialTenantDomains <List>]
33+
[-ApplyExternalAccessRestrictionsToChatMembership <Boolean>]
34+
[-ExtendMutualFederationForChatMembership <Boolean>]
3335
[[-Identity] <XdsIdentity>] [-Force] [-WhatIf] [-Confirm] [<CommonParameters>]
3436
```
3537

@@ -38,7 +40,10 @@ Set-CsTenantFederationConfiguration [-Tenant <Guid>]
3840
Set-CsTenantFederationConfiguration [-Tenant <Guid>] [-AllowedDomains <IAllowedDomainsChoice>]
3941
[-BlockedDomains <List>] [-BlockAllSubdomains <Boolean>] [-AllowFederatedUsers <Boolean>]
4042
[-TreatDiscoveredPartnersAsUnverified <Boolean>] [-SharedSipAddressSpace <Boolean>] [-RestrictTeamsConsumerToExternalUserProfiles <Boolean>]
41-
[-AllowedDomainsAsAList <List>] [-Instance <PSObject>] [-Force] [-WhatIf] [-Confirm] [<CommonParameters>]
43+
[-AllowedDomainsAsAList <List>]
44+
[-ApplyExternalAccessRestrictionsToChatMembership <Boolean>]
45+
[-ExtendMutualFederationForChatMembership <Boolean>]
46+
[-Instance <PSObject>] [-Force] [-WhatIf] [-Confirm] [<CommonParameters>]
4247
```
4348

4449
## DESCRIPTION
@@ -309,7 +314,7 @@ Accept wildcard characters: False
309314
> Applicable: Microsoft Teams
310315

311316
When set to True (the default value) users will be potentially allowed to communicate with users from other domains.
312-
If this property is set to False then users cannot communicate with users from other domains, regardless of the values assigned to the `AllowedDomains` and `BlockedDomains` properties or any `ExternalAccessPolicy` instances. In effect, the `AllowFederatedUsers` property serves as a master switch that globally enables or disables federation across the Tenant, overridding all other policy settings.
317+
If this property is set to False then users cannot communicate with users from other domains, regardless of the values assigned to the `AllowedDomains` and `BlockedDomains` properties or any `ExternalAccessPolicy` instances. In effect, the `AllowFederatedUsers` property serves as a master switch that globally enables or disables federation across the Tenant, overriding all other policy settings.
313318

314319
To block all domains while selectively allowing specific users to communicate externally via explicit `ExternalAccessPolicy` instances, set `AllowFederatedUsers` to `True` and leave the `AllowedDomains` property empty.
315320

@@ -459,6 +464,63 @@ Default value: None
459464
Accept pipeline input: False
460465
Accept wildcard characters: False
461466
```
467+
### -ApplyExternalAccessRestrictionsToChatMembership
468+
469+
> Applicable: Microsoft Teams
470+
471+
> This parameter is reserved for future use and has no effect at this time.
472+
473+
When set to False (the default value), users in the tenant who have `EnableFederationAccess` set to False in their assigned `ExternalAccessPolicy` can be added to group chats that include external users only when the chat is initiated by a user in the same tenant who has `EnableFederationAccess` set to True.
474+
475+
When set to True, users in the tenant who have `EnableFederationAccess` set to False are blocked from being added to any group chat that includes external users and are removed from existing active group chats that include external users.
476+
477+
The `ApplyExternalAccessRestrictionsToChatMembership` parameter does not affect the behavior set by `CommunicationWithExternalOrgs` parameter of the `ExternalAccessPolicy`.
478+
> [!NOTE]
479+
> This setting only applies to group chats and does not affect a user's ability to join meetings with external users or participate in meeting chats with external users. Refer to [Set-CsExternalAccessPolicy](/powershell/module/microsoftteams/set-csexternalaccesspolicy) for information about `EnableFederationAccess` parameter.
480+
>
481+
> Removal of users only applies to active group chats. An active group chat is defined as a chat in which a message has been sent within the past two hours. Users are removed from inactive group chats only when a new message is sent and the chat becomes active
482+
483+
```yaml
484+
Type: ApplyExternalAccessRestrictionsToChatMembership
485+
Parameter Sets: (All)
486+
Aliases:
487+
488+
Required: False
489+
Position: Named
490+
Default value: False
491+
Accept pipeline input: False
492+
Accept wildcard characters: False
493+
```
494+
### -ExtendMutualFederationForChatMembership
495+
496+
> Applicable: Microsoft Teams
497+
498+
> This parameter is reserved for future use and has no effect at this time.
499+
500+
This parameter specifies whether additional mutual federation requirements are extended across all participants in a group chat. Mutual federation relationships are determined by each user’s effective external access configuration (`AllowedDomains`, `BlockedDomains`, and `ExternalAccessPolicy`). When enabled, this parameter adds participant‑level mutual federation enforcement to group chat.
501+
502+
When set to False (the default value), **only the initiator of the group chat and the user joining or being added are required to have a mutual federation relationship**. Users in the tenant can join or be added to group chats that may include other external participants who are not permitted by the user’s own external access configuration, based on the initiating user’s settings. This behavior applies to group chats initiated by users within the tenant or by external users.
503+
504+
When set to True, **all participants in the group chat must have mutual federation relationships with every other participant in the chat**. Users are blocked from joining or being added to group chats if they do not have mutual federation relationships with all existing participants. These relationships are evaluated continuously for all active chats and participants are automatically removed from existing active group chats when required relationships are no longer valid.
505+
506+
> [!NOTE]
507+
> This setting only applies to group chats and does not affect a user's ability to join meetings with external users or participate in meeting chats with external users. Refer to [Set-CsExternalAccessPolicy](/powershell/module/microsoftteams/set-csexternalaccesspolicy) for information about `EnableFederationAccess` parameter.
508+
>
509+
> Removal of users only applies to active group chats. An active group chat is defined as a chat in which a message has been sent within the past two hours. Users are removed from inactive group chats only when a new message is sent and the chat becomes active.
510+
>
511+
> The user who initiated the chat is never removed from the group chat as a result of this setting.
512+
513+
```yaml
514+
Type: ExtendMutualFederationForChatMembership
515+
Parameter Sets: (All)
516+
Aliases:
517+
518+
Required: False
519+
Position: Named
520+
Default value: False
521+
Accept pipeline input: False
522+
Accept wildcard characters: False
523+
```
462524

463525
### -Force
464526

@@ -483,7 +545,7 @@ Accept wildcard characters: False
483545
> Applicable: Microsoft Teams
484546

485547
Specifies the collection of tenant federation configuration settings to be modified.
486-
Because each tenant is limited to a single, global collection of federation settings there is no need include this parameter when calling the `Set-CsTenantFederationConfiguration` cmdlet.
548+
Because each tenant is limited to a single, global collection of federation settings there is no need to include this parameter when calling the `Set-CsTenantFederationConfiguration` cmdlet.
487549
If you do choose to use the Identity parameter you must also include the Tenant parameter.
488550
For example:
489551

0 commit comments

Comments
 (0)