Merge branch 'main' into Export-chrisda

chrisda · chrisda · commit 9b17f87a849b · 2025-05-16T10:35:26.000-07:00
diff --git a/exchange/exchange-ps/exchange/Add-MailboxPermission.md b/exchange/exchange-ps/exchange/Add-MailboxPermission.md
@@ -420,7 +420,7 @@ Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Ex
 
 Required: False
 Position: Named
-Default value: None
+Default value: All
 Accept pipeline input: False
 Accept wildcard characters: False
 ```
diff --git a/skype/skype-ps/skype/New-CsExternalAccessPolicy.md b/skype/skype-ps/skype/New-CsExternalAccessPolicy.md
@@ -12,6 +12,8 @@ ms.reviewer: rogupta
 # New-CsExternalAccessPolicy
 
 ## SYNOPSIS
+> [!NOTE]
+> Starting May 5, 2025, Skype Consumer Interoperability with Teams is no longer supported and the parameter EnablePublicCloudAccess can no longer be used.
 
 Enables you to create a new external access policy.
 
diff --git a/skype/skype-ps/skype/Set-CsExternalAccessPolicy.md b/skype/skype-ps/skype/Set-CsExternalAccessPolicy.md
@@ -12,6 +12,9 @@ ms.reviewer: rogupta
 # Set-CsExternalAccessPolicy
 
 ## SYNOPSIS
+> [!NOTE]
+> Starting May 5, 2025, Skype Consumer Interoperability with Teams is no longer supported and the parameter EnablePublicCloudAccess can no longer be used.
+
 Enables you to modify the properties of an existing external access policy.
 External access policies determine whether or not your users can: 1) communicate with users who have Session Initiation Protocol (SIP) accounts with a federated organization; 2) communicate with users who are using custom applications built with [Azure Communication Services](/azure/communication-services/concepts/teams-interop); 3) access Skype for Business Server over the Internet, without having to log on to your internal network; 4) communicate with users who have SIP accounts with a public instant messaging (IM) provider such as Skype; and, 5) communicate with people who are using Teams with an account that's not managed by an organization.
 
diff --git a/teams/teams-ps/teams/New-CsExternalAccessPolicy.md b/teams/teams-ps/teams/New-CsExternalAccessPolicy.md
@@ -133,7 +133,7 @@ New-CsExternalAccessPolicy -Identity GranularFederationExample -CommunicationWit
 Set-CsTenantFederationConfiguration -CustomizeFederation $true
 ```
 
-In this example, we create an ExternalAccessPolicy named "GranularFederationExample" that allows communication with specific external domains, namely `example1.com` and `example2.com`. The federation policy is set to restrict communication to only these allowed domains. After that, we still have to enable the `CustomizeFederation` setting in the TenantFederationConfiguration to allow the federation settings as defined in the ExternalAccessPolicy to work.
+In this example, we create an ExternalAccessPolicy named "GranularFederationExample" that allows communication with specific external domains, namely `example1.com` and `example2.com`. The federation policy is set to restrict communication to only these allowed domains.
 
 ## PARAMETERS
 
@@ -163,7 +163,10 @@ Accept wildcard characters: False
 ```
 
 ### -AllowedExternalDomains
-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`.
+> [!NOTE]
+> Please note that this parameter is in Private Preview.
+
+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.
 
 ```yaml
 Type: List
@@ -178,7 +181,10 @@ Accept wildcard characters: False
 ```
 
 ### -BlockedExternalDomains
-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`.
+> [!NOTE]
+> Please note that this parameter is in Private Preview.
+
+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.
 
 ```yaml
 Type: List
@@ -193,14 +199,18 @@ Accept wildcard characters: False
 ```
 
 ### -CommunicationWithExternalOrgs
-Indicates how the users get assigned by this policy can communicate with the external orgs. There are 5 options:
+> [!NOTE]
+> Please note that this parameter is in Private Preview.
+
+Indicates how users assigned to the policy can communicate with external organizations (domains). This setting has 5 possible values:
 
-- OrganizationDefault: the users of this policy will follow the federation settings defined in TenantFederationConfiguration
-- AllowAllExternalDomains: the users are open to communicate with all domains
-- 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: users follow the federation settings specified in `TenantFederationConfiguration`. This is the default value.
+- AllowAllExternalDomains: users are allowed to communicate with all domains.
+- AllowSpecificExternalDomains: users can communicate with external domains listed in `AllowedExternalDomains`.
+- BlockSpecificExternalDomains: users are blocked from communicating with domains listed in `BlockedExternalDomains`.
+- BlockAllExternalDomains: users cannot communicate with any external domains.
 
+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.
 ```yaml
 Type: String
 Parameter Sets: (All)
diff --git a/teams/teams-ps/teams/Set-CsExternalAccessPolicy.md b/teams/teams-ps/teams/Set-CsExternalAccessPolicy.md
@@ -142,8 +142,7 @@ In this example, the Global policy is updated to allow Teams-ACS federation for
 New-CsExternalAccessPolicy -Identity GranularFederationExample -CommunicationWithExternalOrgs "AllowSpecificExternalDomains" -AllowedExternalDomains @("example1.com", "example2.com")
 Set-CsTenantFederationConfiguration -CustomizeFederation $true
 ```
-
-In this example, we create an ExternalAccessPolicy named "GranularFederationExample" that allows communication with specific external domains, namely `example1.com` and `example2.com`. The federation policy is set to restrict communication to only these allowed domains. After that, we still have to enable the `CustomizeFederation` setting in the TenantFederationConfiguration to allow the federation settings as defined in the ExternalAccessPolicy to work.
+In this example, we create an ExternalAccessPolicy named "GranularFederationExample" that allows communication with specific external domains, namely `example1.com` and `example2.com`. The federation policy is set to restrict communication to only these allowed domains.
 
 ## PARAMETERS
 
@@ -187,7 +186,10 @@ Accept wildcard characters: False
 ```
 
 ### -AllowedExternalDomains
-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`
+> [!NOTE]
+> Please note that this parameter is in Private Preview.
+
+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.
 ```yaml
 Type: List
 Parameter Sets: (All)
@@ -202,7 +204,10 @@ Accept wildcard characters: False
 ```
 
 ### -BlockedExternalDomains
-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`
+> [!NOTE]
+> Please note that this parameter is in Private Preview.
+
+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.
 ```yaml
 Type: List
 Parameter Sets: (All)
@@ -217,14 +222,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:
 
-- OrganizationDefault: the users of this policy will follow the federation settings defined in TenantFederationConfiguration.
-- AllowAllExternalDomains: the users are open to communicate with all domains.
-- 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: users follow the federation settings specified in `TenantFederationConfiguration`. This is the default value.
+- AllowAllExternalDomains: users are allowed to communicate with all domains.
+- AllowSpecificExternalDomains: users can communicate with external domains listed in `AllowedExternalDomains`.
+- BlockSpecificExternalDomains: users are blocked from communicating with domains listed in `BlockedExternalDomains`.
+- BlockAllExternalDomains: users cannot communicate with any external domains.
 
+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.
 ```yaml
 Type: String
 Parameter Sets: (All)
diff --git a/teams/teams-ps/teams/Set-CsTenantFederationConfiguration.md b/teams/teams-ps/teams/Set-CsTenantFederationConfiguration.md
@@ -14,6 +14,9 @@ ms.date: 12/11/2024
 # Set-CsTenantFederationConfiguration
 
 ## SYNOPSIS
+> [!NOTE]
+> Starting May 5, 2025, Skype Consumer Interoperability with Teams is no longer supported and the parameter AllowPublicUsers can no longer be used.
+
 Manages federation configuration settings for your Skype for Business Online tenants.
 These settings are used to determine which domains (if any) your users are allowed to communicate with.
 
@@ -509,7 +512,7 @@ Accept wildcard characters: False
 ```
 
 ### -RestrictTeamsConsumerToExternalUserProfiles
-Defines if a user is restriced to collaboration with Teams Consumer (TFL) user only in Extended Directory.
+Defines if a user is restricted to collaboration with Teams Consumer (TFL) user only in Extended Directory.
 Possible values: True, False
 
 ```yaml
