Merge pull request MicrosoftDocs#1212 from bjwhalen/patch-6

Update Get-CsTeamsUpgradePolicy.md

Author: kenwith

skype/skype-ps/skype/Get-CsTeamsUpgradePolicy.md

@@ -26,19 +26,20 @@ Get-CsTeamsUpgradePolicy [-Tenant <guid>] [-Filter <string>] [<CommonParameters>
 ```
 
 ## DESCRIPTION
-TeamsUpgradePolicy allows administrators to manage the transition from Skype for Business to Teams. This cmdlet returns the set of instances of this policy. As an organization with Skype for Business starts to adopt Teams, administrators can manage client behavior for their end user using the concept of "mode", which defines where routing behavior (e.g in which client do chats and calls land). In the future, mode will also be used to define client behavior in Teams client in terms of what functionality will be available.  TeamsUpradePolicy can be granted either on a per user basis or on a tenant-wide basis.  In addition, prior to upgrading to TeamsOnly mode administrators can use TeamsUpgradePolicy to trigger notifications in the Skype for Business client to inform users of the pending upgrade. 
+TeamsUpgradePolicy allows administrators to manage the transition from Skype for Business to Teams. This cmdlet returns the set of instances of this policy. As an organization with Skype for Business starts to adopt Teams, administrators can manage client behavior for their end user using the concept of "mode", which defines where routing behavior (e.g in which client do chats and calls land). In the future, mode will also be used to define client behavior in Teams client in terms of what functionality will be available.  TeamsUpgradePolicy can be granted either on a per user basis or on a tenant-wide basis.  In addition, prior to upgrading to TeamsOnly mode, administrators can use TeamsUpgradePolicy to trigger notifications in the Skype for Business client to inform users of the pending upgrade. 
 
 NOTES: 
-   All relevant instances of TeamsUpgradePolicy are built into the system, so there is no corresponding New cmdlet.
-
-   Instances with mode set to SfBWithTeamsCollab are not yet functional. From a routing perspective, this will behave like SfBOnly mode.
+  - Except for on-premise versions of Skype for Business Server, all relevant instances of TeamsUpgradePolicy are built into the system, so there is no corresponding New cmdlet. 
+  - If you are using Skype for Business Server, there are no built-in instances and you'll need to create one. Also, only the NotifySfBUsers property is available. Mode is not present
+  - Instances with mode set to SfBWithTeamsCollab are not yet functional. From a routing perspective, this will behave like SfBOnly mode.
+  - Action property is redundnant with the combination of NotifySfBUsers and Mode. It will eventually be removed.  
 
 IMPORTANT:  TeamsUpgradePolicy will replace TeamsInteropPolicy. Components that previously honored TeamsInteropPolicy are being updated to honor TeamsUpgradePolicy instead. During the transition, use of these 2 policies must be coordinated during the transition. After transition is complete, TeamsInteorpPolicy will be removed.
 
 
 ## EXAMPLES
 
-### Example 1: List all instances of TeamsUpgradePolicy
+### Example 1: List all instances of TeamsUpgradePolicy (Skype for Business Online)
 ```
 PS C:\> Get-CsTeamsUpgradePolicy
 
@@ -121,6 +122,17 @@ Action         : None
 
 List the global instance of TeamsUpgradePolicy
 
+### Example 3: List all instances of TeamsUpgradePolicy in an on-premises environment
+```
+PS C:\> Get-CsTeamsUpgradePolicy -Identity Global
+
+Identity       : Global
+Description    : Notifications are disabled
+NotifySfbUsers : False
+
+```
+
+List all on-premises instances (if any) of TeamsUpgradePolicy
 ## PARAMETERS