Skip to content

Update New-CsExternalAccessPolicy.md #12780

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Jun 5, 2025
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 12 additions & 1 deletion teams/teams-ps/teams/New-CsExternalAccessPolicy.md
Original file line number Diff line number Diff line change
Expand Up @@ -394,16 +394,27 @@ Accept wildcard characters: False
```

### -FederatedBilateralChats
> [!NOTE]
> Please note that this parameter is in Private Preview.

This setting enables bi-lateral chats for the users included in the messaging policy.

Some organizations may want to restrict who users are able to message in Teams. While organizations have always been able to limit users' chats to only other internal users, organizations can now limit users' chat ability to only chat with other internal users and users in one other organization via the bilateral chat policy.

Once external access and bilateral policy is set up, users with the policy can be in external group chats only with a maximum of two organizations. When they try to create a new external chat with users from more than two tenants or add a user from a third tenant to an existing external chat, a system message will be shown preventing this action.

Users with bilateral policy applied are also removed from existing external group chats with more than two organizations.

This policy doesn't apply to meetings, meeting chats, or channels.

```yaml
Type: Boolean
Parameter Sets: (All)
Aliases:

Required: False
Position: Named
Default value: True
Default value: False
Accept pipeline input: False
Accept wildcard characters: False
```
Expand Down