Skip to content

Update Set-CsExternalAccessPolicy.md #12720

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 9 commits into from
May 15, 2025

Conversation

krammerliu
Copy link
Contributor

No description provided.

Copy link

Learn Build status updates of commit 2dfc1bc:

✅ Validation status: passed

File Status Preview URL Details
teams/teams-ps/teams/Set-CsExternalAccessPolicy.md ✅Succeeded View (teams-ps)

For more details, please refer to the build report.

For any questions, please:

Copy link

Learn Build status updates of commit d717c46:

✅ Validation status: passed

File Status Preview URL Details
teams/teams-ps/teams/Set-CsExternalAccessPolicy.md ✅Succeeded View (teams-ps)

For more details, please refer to the build report.

For any questions, please:

Copy link

Learn Build status updates of commit 6ff6201:

✅ Validation status: passed

File Status Preview URL Details
teams/teams-ps/teams/Set-CsExternalAccessPolicy.md ✅Succeeded View (teams-ps)

For more details, please refer to the build report.

For any questions, please:

Copy link

Learn Build status updates of commit 91d96c4:

✅ Validation status: passed

File Status Preview URL Details
teams/teams-ps/teams/New-CsExternalAccessPolicy.md ✅Succeeded View (teams-ps)
teams/teams-ps/teams/Set-CsExternalAccessPolicy.md ✅Succeeded View (teams-ps)

For more details, please refer to the build report.

For any questions, please:

@michbrown-png michbrown-png added Sign off The pull request is ready to be reviewed and merged by PubOps and removed Sign off The pull request is ready to be reviewed and merged by PubOps labels May 12, 2025
> [!NOTE]
> Please note that this parameter is in Private Preview.

Indicates the domains that are allowed to communicate with the users of this policy. This is referenced only when `CommunicationWithExternalOrgs` is set to be `AllowSpecificExternalDomains`. Only custom policies can change this setting. In Global (default) policy this setting should be default value always and is not allowed to be changed.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@krammerliu I may not be aware of the most recent changes to GFC plan, therefore, asking. Are we saying that global org wide external access policy will not allow specifying Specific domains? This would only be available in org settings page?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@MJMicrosoft yes and no. Are we saying that global org wide external access policy will not allow specifying Specific domains? <- yes, but for "This would only be available in org settings page?" <- this would only be available in external access policy page, which is not enabled yet in our preview

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@krammerliu shouldn't we update the Tenant Federation config doc as well in this case ?

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@krammerliu just to make sure that I understand this correctly:
external access org wide policy - will only have 2 options:

  1. Off
  2. follow org settings
    Correct?

External access custom policies will have 5 options:

  1. Follow org settings
  2. Allow specific
  3. Allow all
  4. Block specific
  5. Block all
    Correct?

I am probably not getting that information reading the document.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@MJMicrosoft for custom polies, yes. for org wide policy, based on "In Global (default) policy this setting should be default value always and is not allowed to be changed", it will be "Follow org settings" by default and customers can't change this value

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

Indicates the domains that are blocked from communicating with the users of this policy. This is referenced only when `CommunicationWithExternalOrgs` is set to be `BlockSpecificExternalDomains`. Only custom policies can change this setting. In Global (default) policy this setting should be default value always and is not allowed to be changed.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@krammerliu same question as above.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

replied above


The setting only applies if `EnableFederationAccess` is true. Simiar to `AllowedExternalDomains` and `BlockedExternalDomains`, only custom policies can change this setting. In Global (default) policy this setting should be default value always and is not allowed to be changed.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@krammerliu should we add clarity about what is the default value?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@MJMicrosoft yes, the default value is listed below (line #214 before the change. line #224 in the new change)

Copy link

@akhilsoman akhilsoman May 13, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

But that is not clear enough I feel . OrganizationDefault , is what it says right ? What I am missing is the default behavior

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

hi @akhilsoman what's missing in your opinion based on "the users of this policy will follow the federation settings defined in TenantFederationConfiguration"? feel free to suggest. thanks!

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

Indicates the domains that are allowed to communicate with the users of this policy. This is referenced only when `CommunicationWithExternalOrgs` is set to be `AllowSpecificExternalDomains`. Only custom policies can change this setting. In Global (default) policy this setting should be default value always and is not allowed to be changed.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@krammerliu should we add clarity about what is the default value?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

default value is listed below, which is an empty list

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Specifies the external domains allowed to communicate with users assigned to this policy. This setting is applicable only when CommunicationWithExternalOrgs is configured to AllowSpecificExternalDomains. This setting can be modified only in custom policy. In Global (default) policy CommunicationWithExternalOrgs can only be set to OrganizationDefault and cannot be changed.

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

Indicates the domains that are allowed to communicate with the users of this policy. This is referenced only when `CommunicationWithExternalOrgs` is set to be `AllowSpecificExternalDomains`. Only custom policies can change this setting. In Global (default) policy this setting should be default value always and is not allowed to be changed.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Specifies the external domains allowed to communicate with users assigned to this policy. This setting is applicable only when CommunicationWithExternalOrgs is configured to AllowSpecificExternalDomains. This setting can be modified only in custom policy. In Global (default) policy CommunicationWithExternalOrgs can only be set to OrganizationDefault and cannot be changed.

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

Indicates the domains that are blocked from communicating with the users of this policy. This is referenced only when `CommunicationWithExternalOrgs` is set to be `BlockSpecificExternalDomains`. Only custom policies can change this setting. In Global (default) policy this setting should be default value always and is not allowed to be changed.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Specifies the external domains blocked from communicating with users assigned to this policy. This setting is applicable only when CommunicationWithExternalOrgs is configured to BlockSpecificExternalDomains. This setting can be modified only in custom policy. In Global (default) policy CommunicationWithExternalOrgs can only be set to OrganizationDefault and cannot be changed.

@@ -196,14 +202,18 @@ Accept wildcard characters: False
```

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

Indicates how the users get assigned by this policy can communicate with the external orgs. There are 5 options:

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Indicates how users assigned to the policy can communicate with external organizations (domains). This setting has 5 possible values:

- AllowSpecificExternalDomains: the users can only communicate with the users of the domains defined in `AllowedExternalDomains`
- BlockSpecificExternalDomains: only users from the domains defined in `BlockedExternalDomains` are blocked from communicating with the users of this policy
- BlockAllExternalDomains: the users are not able to communicate with any external domains
- OrganizationDefault: the users of this policy will follow the federation settings defined in TenantFederationConfiguration.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  • OrganizationDefault: users follow the federation settings specified in TenantFederationConfiguration. This is the default value.

- BlockSpecificExternalDomains: only users from the domains defined in `BlockedExternalDomains` are blocked from communicating with the users of this policy
- BlockAllExternalDomains: the users are not able to communicate with any external domains
- OrganizationDefault: the users of this policy will follow the federation settings defined in TenantFederationConfiguration.
- AllowAllExternalDomains: the users are open to communicate with all domains.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  • AllowAllExternalDomains: the users are allowed to communicate with all domains.

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

Indicates the domains that are blocked from communicating with the users of this policy. This is referenced only when `CommunicationWithExternalOrgs` is set to be `BlockSpecificExternalDomains`. Only custom policies can change this setting. In Global (default) policy this setting should be default value always and is not allowed to be changed.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Specifies the external domains blocked from communicating with users assigned to this policy. This setting is applicable only when CommunicationWithExternalOrgs is configured to BlockSpecificExternalDomains. This setting can be modified only in custom policy. In Global (default) policy CommunicationWithExternalOrgs can only be set to OrganizationDefault and cannot be changed.

@@ -230,6 +235,9 @@ Accept wildcard characters: False
```

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

Indicates how the users get assigned by this policy can communicate with the external orgs. There are 5 options:

- OrganizationDefault: the users of this policy will follow the federation settings defined in TenantFederationConfiguration.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

-OrganizationDefault: users follow the federation settings specified in TenantFederationConfiguration. This is the default value.

@@ -238,6 +246,7 @@ Indicates how the users get assigned by this policy can communicate with the ext
- BlockSpecificExternalDomains: only users from the domains defined in `BlockedExternalDomains` are blocked from communicating with the users of this policy.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

-BlockSpecificExternalDomains: users are blocked from communicating with domains listed in BlockedExternalDomains

@@ -238,6 +246,7 @@ Indicates how the users get assigned by this policy can communicate with the ext
- BlockSpecificExternalDomains: only users from the domains defined in `BlockedExternalDomains` are blocked from communicating with the users of this policy.
- BlockAllExternalDomains: the users are not able to communicate with any external domains.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

-BlockAllExternalDomains: users cannot communicate with any external domains.

@@ -238,6 +246,7 @@ Indicates how the users get assigned by this policy can communicate with the ext
- BlockSpecificExternalDomains: only users from the domains defined in `BlockedExternalDomains` are blocked from communicating with the users of this policy.
- BlockAllExternalDomains: the users are not able to communicate with any external domains.

The setting only applies if `EnableFederationAccess` is true. Simiar to `AllowedExternalDomains` and `BlockedExternalDomains`, only custom policies can change this setting. In Global (default) policy this setting should be default value always and is not allowed to be changed.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The setting is only applicable when EnableFederationAccess is set to true. This setting can only be modified in custom policies. In the Global (default) policy, it is fixed to OrganizationDefault and cannot be changed.

Copy link

Learn Build status updates of commit 6c01f10:

✅ Validation status: passed

File Status Preview URL Details
teams/teams-ps/teams/New-CsExternalAccessPolicy.md ✅Succeeded View (teams-ps)
teams/teams-ps/teams/Set-CsExternalAccessPolicy.md ✅Succeeded View (teams-ps)

For more details, please refer to the build report.

For any questions, please:

Copy link

Learn Build status updates of commit 46edee9:

✅ Validation status: passed

File Status Preview URL Details
teams/teams-ps/teams/New-CsExternalAccessPolicy.md ✅Succeeded View (teams-ps)
teams/teams-ps/teams/Set-CsExternalAccessPolicy.md ✅Succeeded View (teams-ps)

For more details, please refer to the build report.

For any questions, please:

- BlockAllExternalDomains: the users are not able to communicate with any external domains
- OrganizationDefault: users follow the federation settings specified in `TenantFederationConfiguration`. This is the default value.
- AllowAllExternalDomains: users are allowed to communicate with all domains.
- AllowSpecificExternalDomains: users the users can communicate with external domains listed in `AllowedExternalDomains`.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Remove the "users the"

- BlockAllExternalDomains: the users are not able to communicate with any external domains.
- OrganizationDefault: users follow the federation settings specified in `TenantFederationConfiguration`. This is the default value.
- AllowAllExternalDomains: users are allowed to communicate with all domains.
- AllowSpecificExternalDomains: users the users can communicate with external domains listed in `AllowedExternalDomains`.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Remove "users the"

Copy link

Learn Build status updates of commit cc68787:

✅ Validation status: passed

File Status Preview URL Details
teams/teams-ps/teams/New-CsExternalAccessPolicy.md ✅Succeeded View (teams-ps)
teams/teams-ps/teams/Set-CsExternalAccessPolicy.md ✅Succeeded View (teams-ps)

For more details, please refer to the build report.

For any questions, please:

Copy link

Learn Build status updates of commit bf8c657:

✅ Validation status: passed

File Status Preview URL Details
teams/teams-ps/teams/New-CsExternalAccessPolicy.md ✅Succeeded View (teams-ps)
teams/teams-ps/teams/Set-CsExternalAccessPolicy.md ✅Succeeded View (teams-ps)

For more details, please refer to the build report.

For any questions, please:

@michbrown-png michbrown-png self-assigned this May 15, 2025
@michbrown-png michbrown-png added the Sign off The pull request is ready to be reviewed and merged by PubOps label May 15, 2025
@Ruchika-mittal01 Ruchika-mittal01 self-assigned this May 15, 2025
@Ruchika-mittal01 Ruchika-mittal01 added the In review PubOps is reviewing the pull request label May 15, 2025
Copy link

Learn Build status updates of commit a088edb:

✅ Validation status: passed

File Status Preview URL Details
teams/teams-ps/teams/New-CsExternalAccessPolicy.md ✅Succeeded View (teams-ps)
teams/teams-ps/teams/Set-CsExternalAccessPolicy.md ✅Succeeded View (teams-ps)

For more details, please refer to the build report.

For any questions, please:

@Ruchika-mittal01 Ruchika-mittal01 merged commit 1935dac into MicrosoftDocs:main May 15, 2025
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
In review PubOps is reviewing the pull request Microsoft submitter Sign off The pull request is ready to be reviewed and merged by PubOps
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants