MicrosoftDocs · tiburd · Oct 7, 2021 · Jul 8, 2020 · May 17, 2021 · May 17, 2021
diff --git a/skype/skype-ps/skype/Get-CsExternalAccessPolicy.md b/skype/skype-ps/skype/Get-CsExternalAccessPolicy.md
@@ -1,10 +1,9 @@
 ---
 external help file: Microsoft.Rtc.Management.dll-help.xml
 online version: https://docs.microsoft.com/powershell/module/skype/get-csexternalaccesspolicy
-applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019
+applicable: Microsoft Teams, Skype for Business Online, Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019
 title: Get-CsExternalAccessPolicy
 schema: 2.0.0
-manager: bulenteg
 author: tomkau
 ms.author: tomkau
 ms.reviewer: rogupta
@@ -14,9 +13,9 @@ ms.reviewer: rogupta
 
 ## SYNOPSIS
 Returns information about the external access policies that have been configured for use in your organization.
-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 have SIP accounts with a public instant messaging (IM) provider such as Windows Live; and, 3) access Skype for Business Server over the Internet, without having to log on to your internal network.
-This cmdlet was introduced in Lync Server 2010.
+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) organize Microsoft Teams meetings that can be joined by users of custom applications built using Azure Communication Services (ACS); 3) access Skype for Business Server over the Internet, without having to log on to your internal network; and, 4) communicate with users who have SIP accounts with a public instant messaging (IM) provider such as Skype.
 
+This cmdlet was introduced in Lync Server 2010.
 
 ## SYNTAX
 
@@ -41,13 +40,21 @@ That might be sufficient to meet your communication needs.
 If it doesn't meet your needs, you can use external access policies to extend the ability of your users to communicate and collaborate.
 External access policies can grant (or revoke) the ability of your users to do any or all of the following:
 
-1. Communicate with people who have SIP accounts with a federated organization.
+1.
+Communicate with people who have SIP accounts with a federated organization.
 Note that enabling federation alone will not provide users with this capability.
 Instead, you must enable federation and then assign users an external access policy that gives them the right to communicate with federated users.
-2. Communicate with people who have SIP accounts with a public instant messaging service such as Windows Live.
-3. Access Skype for Business Server over the Internet, without having to first log on to your internal network.
+
+2.
+(Microsoft Teams only) Organize Teams meetings that can be joined by users of custom applications built using Azure Communication Services (ACS). This policy setting only applies if ACS Teams federation has been enabled at the tenant level using the cmdlet Set-CsTeamsAcsFederationConfiguration.
+
+3.
+Access Skype for Business Server over the Internet, without having to first log on to your internal network.
 This enables your users to use Skype for Business and log on to Skype for Business Server from an Internet café or other remote location.
 
+4.
+Communicate with people who have SIP accounts with a public instant messaging service such as Skype.
+
 The Get-CsExternalAccessPolicy cmdlet provides a way for you to return information about all of the external access policies that have been configured for use in your organization.
 
 
@@ -293,4 +300,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable
 [Remove-CsExternalAccessPolicy](Remove-CsExternalAccessPolicy.md)
 
 [Set-CsExternalAccessPolicy](Set-CsExternalAccessPolicy.md)
-
diff --git a/skype/skype-ps/skype/New-CsExternalAccessPolicy.md b/skype/skype-ps/skype/New-CsExternalAccessPolicy.md
@@ -1,10 +1,9 @@
 ---
 external help file: Microsoft.Rtc.Management.dll-help.xml
 online version: https://docs.microsoft.com/powershell/module/skype/new-csexternalaccesspolicy
-applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019
+applicable: Microsoft Teams, Skype for Business Online, Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019
 title: New-CsExternalAccessPolicy
 schema: 2.0.0
-manager: bulenteg
 author: tomkau
 ms.author: tomkau
 ms.reviewer: rogupta
@@ -15,15 +14,17 @@ ms.reviewer: rogupta
 ## SYNOPSIS
 
 Enables you to create a new 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 have SIP accounts with a public instant messaging (IM) provider such as MSN; and, 3) access Skype for Business Server over the Internet, without having to log on to your internal network.
+
+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) organize Microsoft Teams meetings that can be joined by users of custom applications built using Azure Communication Services (ACS); 3) access Skype for Business Server over the Internet, without having to log on to your internal network; and, 4) communicate with users who have SIP accounts with a public instant messaging (IM) provider such as Skype.
+
 This cmdlet was introduced in Lync Server 2010.
 
 For information about external access in Microsoft Teams, see [Manage external access in Microsoft Teams](/microsoftteams/manage-external-access) and [Teams and Skype interoperability](/microsoftteams/teams-skype-interop) for specific details.
 
 ## SYNTAX
 
-```
-New-CsExternalAccessPolicy [-Tenant <Guid>] [-Description <String>] [-EnableFederationAccess <Boolean>]
+```powershell
+New-CsExternalAccessPolicy [-Tenant <Guid>] [-Description <String>] [-EnableFederationAccess <Boolean>] [-EnableAcsFederationAccess <Boolean>]
  [-EnableXmppAccess <Boolean>] [-EnablePublicCloudAccess <Boolean>]
  [-EnablePublicCloudAudioVideoAccess <Boolean>] [-EnableOutsideAccess <Boolean>] [-Identity] <XdsIdentity>
  [-InMemory] [-Force] [-WhatIf] [-Confirm] [<CommonParameters>]
@@ -44,12 +45,15 @@ Note that enabling federation alone will not provide users with this capability.
 Instead, you must enable federation and then assign users an external access policy that gives them the right to communicate with federated users.
 
 2.
-Communicate with people who have SIP accounts with a public instant messaging service such as MSN.
+(Microsoft Teams only) Organize Teams meetings that can be joined by users of custom applications built using Azure Communication Services (ACS). This policy setting only applies if ACS Teams federation has been enabled at the tenant level using the cmdlet Set-CsTeamsAcsFederationConfiguration.
 
 3.
 Access Skype for Business Server over the Internet, without having to first log on to your internal network.
 This enables your users to use Skype for Business and log on to Skype for Business Server from an Internet café or other remote location.
 
+4.
+Communicate with people who have SIP accounts with a public instant messaging service such as Skype.
+
 When you install Skype for Business Server, a global external access policy is automatically created for you.
 In addition to the global policy, you can also create custom external access policies at either the site or the per-user scope.
 If you create an external access policy at the site scope, that policy will automatically be assigned to the site upon creation.
@@ -62,6 +66,7 @@ In addition, you can have only one external access policy per site: if the Redmo
 
 The following parameters are not applicable to Skype for Business Online/Microsoft Teams: Description, EnableXmppAccess, Force, Identity, InMemory, PipelineVariable, and Tenant
 
+
 ## EXAMPLES
 
 
@@ -158,6 +163,25 @@ Accept pipeline input: False
 Accept wildcard characters: False
 ```
 
+### -EnableAcsFederationAccess
+Indicates whether Teams meeting organized by the user can be joined by users of customer applications built using Azure Communication Services (ACS). This policy setting only applies if ACS Teams federation has been enabled at the tenant level using the cmdlet Set-CsTeamsAcsFederationConfiguration. 
+
+To enable for all users, use the Set-CsExternalAccessPolicy cmdlet to update the global policy, setting the value to True. It can be disabled for selected users by assigning them a policy with federation disabled.
+
+To enable just for a selected set of users, use the Set-CsExternalAccessPolicy cmdlet to update the global policy, setting the value to False. Then assign selected users a policy with federation enabled.
+
+```yaml
+Type: Boolean
+Parameter Sets: (All)
+Aliases: 
+Applicable: Microsoft Teams
+Required: False
+Position: Named
+Default value: True
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
 ### -EnableOutsideAccess
 Indicates whether the user is allowed to connect to Skype for Business Server over the Internet, without logging on to the organization's internal network.
 The default value is False.
@@ -343,3 +367,4 @@ Creates new instances of the Microsoft.Rtc.Management.WritableConfig.Policy.Exte
 
 [Set-CsExternalAccessPolicy](Set-CsExternalAccessPolicy.md)
 
+
diff --git a/skype/skype-ps/skype/Set-CsExternalAccessPolicy.md b/skype/skype-ps/skype/Set-CsExternalAccessPolicy.md
@@ -4,7 +4,6 @@ online version: https://docs.microsoft.com/powershell/module/skype/set-csexterna
 applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019
 title: Set-CsExternalAccessPolicy
 schema: 2.0.0
-manager: bulenteg
 author: tomkau
 ms.author: tomkau
 ms.reviewer: rogupta
@@ -14,23 +13,25 @@ ms.reviewer: rogupta
 
 ## SYNOPSIS
 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 have SIP accounts with a public instant messaging (IM) provider such as MSN and 3) access Skype for Business Server over the Internet, without having to log on to your internal network.
+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) organize Microsoft Teams meetings that can be joined by users of custom applications built using Azure Communication Services (ACS); 3) access Skype for Business Server over the Internet, without having to log on to your internal network; and, 4) communicate with users who have SIP accounts with a public instant messaging (IM) provider such as Skype.
+
+
 This cmdlet was introduced in Lync Server 2010.
 
 
 ## SYNTAX
 
 ### Identity (Default)
 ```
-Set-CsExternalAccessPolicy [-Tenant <Guid>] [-Description <String>] [-EnableFederationAccess <Boolean>]
+Set-CsExternalAccessPolicy [-Tenant <Guid>] [-Description <String>] [-EnableFederationAccess <Boolean>] [-EnableAcsFederationAccess <Boolean>]
  [-EnableXmppAccess <Boolean>] [-EnablePublicCloudAccess <Boolean>]
  [-EnablePublicCloudAudioVideoAccess <Boolean>] [-EnableOutsideAccess <Boolean>] [[-Identity] <XdsIdentity>]
  [-Force] [-WhatIf] [-Confirm] [<CommonParameters>]
 ```
 
 ### Instance
 ```
-Set-CsExternalAccessPolicy [-Tenant <Guid>] [-Description <String>] [-EnableFederationAccess <Boolean>]
+Set-CsExternalAccessPolicy [-Tenant <Guid>] [-Description <String>] [-EnableFederationAccess <Boolean>] [-EnableAcsFederationAccess <Boolean>]
  [-EnableXmppAccess <Boolean>] [-EnablePublicCloudAccess <Boolean>]
  [-EnablePublicCloudAudioVideoAccess <Boolean>] [-EnableOutsideAccess <Boolean>] [-Instance <PSObject>]
  [-Force] [-WhatIf] [-Confirm] [<CommonParameters>]
@@ -50,7 +51,7 @@ Note that enabling federation alone will not provide users with this capability.
 Instead, you must enable federation and then assign users an external access policy that gives them the right to communicate with federated users.
 
 2.
-Communicate with people who have SIP accounts with a public instant messaging service such as MSN.
+(Microsoft Teams only) Organize Teams meetings that can be joined by users of custom applications built using Azure Communication Services (ACS). This policy setting only applies if ACS Teams federation has been enabled at the tenant level using the cmdlet Set-CsTeamsAcsFederationConfiguration.
 
 3.
 Access Skype for Business Server over the Internet, without having to first log on to your internal network.
@@ -60,6 +61,9 @@ After an external access policy has been created, you can use the `Set-CsExterna
 For example, by default the global policy does not allow users to communicate with people who have accounts with a federated organization.
 If you would like to grant this capability to all of your users you can call the `Set-CsExternalAccessPolicy` cmdlet and set the value of the global policy's EnableFederationAccess property to True.
 
+4.
+Communicate with people who have SIP accounts with a public instant messaging service such as Skype.
+
 The following parameters are not applicable to Skype for Business Online/Microsoft Teams: Description, EnableXmppAccess, Force, Identity, Instance, PipelineVariable, and Tenant
 
 ## EXAMPLES
@@ -105,6 +109,22 @@ This collection is piped to the `Where-Object` cmdlet, which picks out only thos
 The filtered collection is then piped to the `Set-CsExternalAccessPolicy` cmdlet, which takes each policy and sets the EnableFederationAccess property to True.
 The net result: all external access policies that allow public cloud access will also allow federation access.
 
+### -------------------------- Example 5 ------------------------
+```
+Set-CsExternalAccessPolicy -Identity Global  -EnableAcsFederationAccess $false
+New-CsExternalAccessPolicy -Identity AcsFederationAllowed  -EnableAcsFederationAccess $true
+```
+
+In this example, the Global policy is updated to disallow Teams-ACS federation for all users, then a new external access policy instance is created with Teams-ACS federation enabled and which can be assigned to selected users for which Team-ACS federation will be allowed.
+
+### -------------------------- Example 5 ------------------------
+```
+Set-CsExternalAccessPolicy -Identity Global  -EnableAcsFederationAccess $true
+New-CsExternalAccessPolicy -Identity AcsFederationNotAllowed  -EnableAcsFederationAccess $false
+```
+
+In this example, the Global policy is updated to allow Teams-ACS federation for all users, then a new external access policy instance is created with Teams-ACS federation disabled and which can then be assigned to selected users for which Team-ACS federation will not be allowed.
+
 
 ## PARAMETERS
 
@@ -184,6 +204,25 @@ Accept pipeline input: False
 Accept wildcard characters: False
 ```
 
+### -EnableAcsFederationAccess
+Indicates whether Teams meeting organized by the user can be joined by users of customer applications built using Azure Communication Services (ACS). This policy setting only applies if ACS Teams federation has been enabled at the tenant level using the cmdlet Set-CsTeamsAcsFederationConfiguration. 
+
+To enable for all users, use the Set-CsExternalAccessPolicy cmdlet to update the global policy, setting the value to True. It can be disabled for selected users by assigning them a policy with federation disabled.
+
+To enable just for a selected set of users, use the Set-CsExternalAccessPolicy cmdlet to update the global policy, setting the value to False. Then assign selected users a policy with federation enabled.
+
+```yaml
+Type: Boolean
+Parameter Sets: (All)
+Aliases: 
+Applicable: Microsoft Teams
+Required: False
+Position: Named
+Default value: True
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
 ### -EnablePublicCloudAccess
 Indicates whether the user is allowed to communicate with people who have SIP accounts with a public Internet connectivity provider such as MSN.
 Read [Manage external access in Microsoft Teams](/microsoftteams/manage-external-access) to get more information about the effect of this parameter in Microsoft Teams.
@@ -359,4 +398,3 @@ Instead, the cmdlet configures instances of the Microsoft.Rtc.Management.Writabl
 [New-CsExternalAccessPolicy](New-CsExternalAccessPolicy.md)
 
 [Remove-CsExternalAccessPolicy](Remove-CsExternalAccessPolicy.md)
-
diff --git a/teams/teams-ps/teams/Get-CsTeamsAcsFederationConfiguration.md b/teams/teams-ps/teams/Get-CsTeamsAcsFederationConfiguration.md
@@ -0,0 +1,79 @@
+---
+external help file: Microsoft.TeamsCmdlets.PowerShell.Custom.dll-Help.xml
+Module Name: MicrosoftTeams
+title: Get-CsTeamsAcsFederationConfiguration
+author: tomkau
+ms.author: tomkau
+online version: https://docs.microsoft.com/powershell/module/teams/get-csteamsacsfederationconfiguration
+schema: 2.0.0
+---
+
+# Get-CsTeamsAcsFederationConfiguration
+
+## SYNOPSIS
+
+**Important:** Functionality described in this document is currently in limited preview and only authorized organizations have access. This preview version is provided without a service-level agreement, and is not recommended for production workloads. Certain features might not be supported or might have constrained capabilities. For more information, see [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/).
+
+This cmdlet is used to retrieve the federation configuration between Teams and Azure Communication Services (ACS).
+
+## SYNTAX
+
+```powershell
+Get-CsTeamsAcsFederationConfiguration
+```
+
+## DESCRIPTION
+
+Federation between Teams and Azure Communication Services (ACS) allows users of custom solutions built with ACS to connect and communicate with Teams users over voice, video, chat, and more. For more information, see [Teams interoperability](/azure/communication-services/concepts/teams-interop).
+
+This cmdlet is used retrieve the Teams and ACS federation configuration for a Teams tenant.
+
+You must be a Teams service admin, a Teams communication admin, or Global Administrator for your organization to run the cmdlet.
+
+## Examples
+
+### Example 1
+In this example, federation has been enabled for just one ACS resource.
+
+```powershell
+Get-CsTeamsAcsFederationConfiguration
+```
+```Output
+Identity             : Global
+AllowedAcsResources  : {'faced04c-2ced-433d-90db-063e424b87b1'}
+BlockedAcsResources  : {}
+EnableAcsUsers       : True
+AllowAllAcsResources : False
+```
+
+### Example 2
+In this example, federation is enabled for all ACS resources except for two.
+
+```powershell
+Get-CsTeamsAcsFederationConfiguration
+```
+```Output
+Identity             : Global
+AllowedAcsResources  : {}
+BlockedAcsResources  : {'bf19b7db-6960-41e5-a139-2aa373474354','dac4607d-d2d0-40e5-84df-6f32ebd1251b'}
+EnableAcsUsers       : True
+AllowAllAcsResources : True
+```
+
+## PARAMETERS
+
+## INPUTS
+
+## OUTPUTS
+
+## NOTES
+
+## RELATED LINKS
+
+[Set-CsTeamsAcsFederationConfiguration](Set-CsTeamsAcsFederationConfiguration.md)
+
+[New-CsExternalAccessPolicy](/powershell/module/skype/new-csexternalaccesspolicy?view=skype-ps)
+
+[Set-CsExternalAccessPolicy](/powershell/module/skype/set-csexternalaccesspolicy?view=skype-ps)
+
+[Grant-CsExternalAccessPolicy](/powershell/module/skype/grant-csexternalaccesspolicy?view=skype-ps)