Merge pull request #8490 from tomkau/patch-13

Updates related to ACS

Author: tiburd

skype/skype-ps/skype/Get-CsExternalAccessPolicy.md

@@ -13,7 +13,7 @@ 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) 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.
+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 (ACS)](/azure/communication-services/concepts/teams-interop); 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.
 
@@ -46,7 +46,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.
-(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.
+(Microsoft Teams only) Communicate with users who are using custom applications built with [Azure Communication Services (ACS)](/azure/communication-services/concepts/teams-interop). This policy setting only applies if ACS federation has been enabled at the tenant level using the cmdlet [Set-CsTeamsAcsFederationConfiguration](/powershell/module/teams/set-csteamsacsfederationconfiguration).
 
 3.
 Access Skype for Business Server over the Internet, without having to first log on to your internal network.

skype/skype-ps/skype/Grant-CsExternalAccessPolicy.md

@@ -15,9 +15,9 @@ ms.reviewer: rogupta
 ## SYNOPSIS
 
 Enables you to assign an external access policy to a user or a group of users.
-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 Microsoft Teams or 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) communicate with users who are using custom applications built with [Azure Communication Services (ACS)](/azure/communication-services/concepts/teams-interop); 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.
-Please note: althought the _Applies to_ section does not mention it, this cmdlet also applies to Microsoft Teams.
 
 ## SYNTAX
 
@@ -42,9 +42,12 @@ Note that enabling federation will not automatically provide users with this cap
 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) Communicate with users who are using custom applications built with [Azure Communication Services (ACS)](/azure/communication-services/concepts/teams-interop). This policy setting only applies if ACS federation has been enabled at the tenant level using the cmdlet [Set-CsTeamsAcsFederationConfiguration](/powershell/module/teams/set-csteamsacsfederationconfiguration).
 
 3.
+Communicate with people who have SIP accounts with a public instant messaging service such as Skype.
+
+4.
 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.
 

skype/skype-ps/skype/New-CsExternalAccessPolicy.md

@@ -15,7 +15,7 @@ ms.reviewer: rogupta
 
 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) 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.
+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 (ACS)](/azure/communication-services/concepts/teams-interop); 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.
 
@@ -45,7 +45,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.
-(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.
+(Microsoft Teams only) Communicate with users who are using custom applications built with [Azure Communication Services (ACS)](/azure/communication-services/concepts/teams-interop). This policy setting only applies if ACS federation has been enabled at the tenant level using the cmdlet [Set-CsTeamsAcsFederationConfiguration](/powershell/module/teams/set-csteamsacsfederationconfiguration).
 
 3.
 Access Skype for Business Server over the Internet, without having to first log on to your internal network.
@@ -78,9 +78,15 @@ New-CsExternalAccessPolicy -Identity site:Redmond -EnableFederationAccess $True
 The command shown in Example 1 creates a new external access policy that has the Identity site:Redmond; upon creation, this policy will automatically be assigned to the Redmond site.
 Note that this new policy sets both the EnableFederationAccess and the EnableOutsideAccess properties to True.
 
+### -------------------------- Example 2 ------------------------
+```
+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.
 
-### -------------------------- EXAMPLE 2 -------------------------- 
+### -------------------------- EXAMPLE 3 -------------------------- 
 ```
 $x = New-CsExternalAccessPolicy -Identity RedmondAccessPolicy -InMemory
 
@@ -93,7 +99,7 @@ $x.EnableOutsideAccess = $True
 Set-CsExternalAccessPolicy -Instance $x
 ```
 
-Example 2 demonstrates the use of the InMemory parameter; this parameter enables you to create an in-memory-only instance of an external access policy.
+Example 3 demonstrates the use of the InMemory parameter; this parameter enables you to create an in-memory-only instance of an external access policy.
 After it has been created, you can modify the in-memory-only instance, then use the Set-CsExternalAccessPolicy cmdlet to transform the virtual policy into a real external access policy.
 
 To do this, the first command in the example uses the New-CsExternalAccessPolicy cmdlet and the InMemory parameter to create a virtual policy with the Identity RedmondAccessPolicy; this virtual policy is stored in a variable named $x.

skype/skype-ps/skype/Set-CsExternalAccessPolicy.md

@@ -13,7 +13,7 @@ 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) 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.
+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; 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.
@@ -51,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.
-(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.
+(Microsoft Teams only) Communicate with users who are using custom applications built with [Azure Communication Services (ACS)](/azure/communication-services/concepts/teams-interop). This policy setting only applies if ACS federation has been enabled at the tenant level using the cmdlet [Set-CsTeamsAcsFederationConfiguration](/powershell/module/teams/set-csteamsacsfederationconfiguration).
 
 3.
 Access Skype for Business Server over the Internet, without having to first log on to your internal network.