Merge branch 'master' into patch-27

Author: chrisda

exchange/exchange-ps/exchange/devices/Get-ActiveSyncDeviceStatistics.md

@@ -16,7 +16,7 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service.
 
 Use the Get-ActiveSyncDeviceStatistics cmdlet to retrieve the list of mobile devices configured to synchronize with a specified user's mailbox and return a list of statistics about the mobile devices.
 
-Note: In Exchange 2013 or later, use the Get-MobileDeviceStatistics cmdlet instead. If you have scripts that use Get-ActiveSyncDeviceStatistics, update them to use Get-MobileDeviceStatistics.
+**Note**: This cmdlet works best in Exchange 2010. In later versions of Exchange Server or Exchange Online, use the Get-MobileDeviceStatistics cmdlet instead. If you have scripts that use Get-ActiveSyncDeviceStatistics, update them to use Get-MobileDeviceStatistics.
 
 For information about the parameter sets in the Syntax section below, see Exchange cmdlet syntax (https://technet.microsoft.com/library/bb123552.aspx).
 

exchange/exchange-ps/exchange/mailboxes/Search-Mailbox.md

@@ -16,6 +16,8 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service.
 
 Use the Search-Mailbox cmdlet to search a mailbox and copy the results to a specified target mailbox, delete messages from the source mailbox, or both.
 
+**Note**: In cloud-based environments, the Search-Mailbox cmdlet is being deprecated in favor of [New-ComplianceSearch](https://docs.microsoft.com/powershell/module/exchange/policy-and-compliance-content-search/new-compliancesearch) and related eDiscovery cmdlets.
+
 For information about the parameter sets in the Syntax section below, see Exchange cmdlet syntax (https://technet.microsoft.com/library/bb123552.aspx).
 
 ## SYNTAX

exchange/exchange-ps/exchange/policy-and-compliance-audit/Search-UnifiedAuditLog.md

@@ -244,10 +244,6 @@ The RecordType parameter filters the log entries by record type. Valid values ar
 
 - MicrosoftTeams
 
-- MicrosoftTeamsAddOns
-
-- MicrosoftTeamsSettingsOperation
-
 - OneDrive
 
 - PowerBIAudit

exchange/exchange-ps/exchange/users-and-groups/Add-UnifiedGroupLinks.md

@@ -32,6 +32,9 @@ Office 365 groups are group objects that are available across Office 365 service
 
 You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see Find the permissions required to run any Exchange cmdlet (https://technet.microsoft.com/library/mt432940.aspx).
 
+> [!NOTE] 
+> Only members can be owners of a group, so you must first add a user as member before adding it as an owner.
+
 ## EXAMPLES
 
 ### -------------------------- Example 1 --------------------------

exchange/exchange-ps/exchange/users-and-groups/New-DynamicDistributionGroup.md

@@ -24,22 +24,22 @@ For information about the parameter sets in the Syntax section below, see Exchan
 ```
 New-DynamicDistributionGroup [-Name] <String> -IncludedRecipients <None | MailboxUsers | Resources | MailContacts | MailGroups | MailUsers | AllRecipients>
  [-ConditionalCompany <MultiValuedProperty>]
- [-ConditionalCustomAttribute1 <MultiValuedProperty>] 
- [-ConditionalCustomAttribute10 <MultiValuedProperty>] 
- [-ConditionalCustomAttribute11 <MultiValuedProperty>] 
- [-ConditionalCustomAttribute12 <MultiValuedProperty>] 
- [-ConditionalCustomAttribute13 <MultiValuedProperty>] 
- [-ConditionalCustomAttribute14 <MultiValuedProperty>] 
- [-ConditionalCustomAttribute15 <MultiValuedProperty>] 
- [-ConditionalCustomAttribute2 <MultiValuedProperty>] 
- [-ConditionalCustomAttribute3 <MultiValuedProperty>] 
- [-ConditionalCustomAttribute4 <MultiValuedProperty>] 
- [-ConditionalCustomAttribute5 <MultiValuedProperty>] 
- [-ConditionalCustomAttribute6 <MultiValuedProperty>] 
- [-ConditionalCustomAttribute7 <MultiValuedProperty>] 
- [-ConditionalCustomAttribute8 <MultiValuedProperty>] 
- [-ConditionalCustomAttribute9 <MultiValuedProperty>] 
- [-ConditionalDepartment <MultiValuedProperty>] 
+ [-ConditionalCustomAttribute1 <MultiValuedProperty>]
+ [-ConditionalCustomAttribute10 <MultiValuedProperty>]
+ [-ConditionalCustomAttribute11 <MultiValuedProperty>]
+ [-ConditionalCustomAttribute12 <MultiValuedProperty>]
+ [-ConditionalCustomAttribute13 <MultiValuedProperty>]
+ [-ConditionalCustomAttribute14 <MultiValuedProperty>]
+ [-ConditionalCustomAttribute15 <MultiValuedProperty>]
+ [-ConditionalCustomAttribute2 <MultiValuedProperty>]
+ [-ConditionalCustomAttribute3 <MultiValuedProperty>]
+ [-ConditionalCustomAttribute4 <MultiValuedProperty>]
+ [-ConditionalCustomAttribute5 <MultiValuedProperty>]
+ [-ConditionalCustomAttribute6 <MultiValuedProperty>]
+ [-ConditionalCustomAttribute7 <MultiValuedProperty>]
+ [-ConditionalCustomAttribute8 <MultiValuedProperty>]
+ [-ConditionalCustomAttribute9 <MultiValuedProperty>]
+ [-ConditionalDepartment <MultiValuedProperty>]
  [-ConditionalStateOrProvince <MultiValuedProperty>]
  [-Alias <String>]
  [-ArbitrationMailbox <MailboxIdParameter>]
@@ -69,7 +69,7 @@ New-DynamicDistributionGroup [-Name] <String> -RecipientFilter <String>
  [-PrimarySmtpAddress <SmtpAddress>]
  [-RecipientContainer <OrganizationalUnitIdParameter>]
  [-SendModerationNotifications <Never | Internal | Always>]
- [-WhatIf]  [<CommonParameters>]
+ [-WhatIf] [<CommonParameters>]
 ```
 
 ## DESCRIPTION
@@ -704,10 +704,12 @@ Valid input for this parameter is an organizational unit (OU) or domain that's v
 
 - GUID
 
-If you don't use this parameter, the default value is typically the Users container in the domain of the Exchange server that you're connected to (also known as the recipient scope). You can change the recipient scope for the current PowerShell session by using the Set-AdServerSettings cmdlet.
+If you don't use this parameter, the default value is typically the Users container in the domain of the Exchange server that you're connected to (also known as the recipient scope). In on-premises Exchange, you can change the recipient scope for the current PowerShell session by using the Set-AdServerSettings cmdlet.
 
 If you don't use the RecipientContainer parameter, the location of the dynamic distribution group is used for the RecipientContainer property (the default location, or the value you specify for the OrganizationalUnit parameter).
 
+**Note**: Although this parameter is available in Exchange Online, there's only one usable OU in an Exchange Online organization, so using this parameter has no effect.
+
 ```yaml
 Type: OrganizationalUnitIdParameter
 Parameter Sets: (All)
@@ -750,6 +752,8 @@ If you don't use this parameter, the default value is the OU where the object wa
 
 Note that the RecipientContainer property can't be blank. The group is always limited to looking for recipients in a specific location (the value you specify for this parameter, or the location where the group was created).
 
+**Note**: Although this parameter is available in Exchange Online, there's only one usable OU in an Exchange Online organization, so using this parameter has no effect.
+
 ```yaml
 Type: OrganizationalUnitIdParameter
 Parameter Sets: (All)

skype/skype-ps/skype/Get-CsTenantNetworkRegion.md

@@ -11,6 +11,7 @@ ms.reviewer:
 # Get-CsTenantNetworkRegion
 
 ## SYNOPSIS
+Returns information about the network region setting in the tenant. Tenant network region is used for Location Based Routing.
 
 ## SYNTAX
 
@@ -26,21 +27,34 @@ Get-CsTenantNetworkRegion [-Tenant <System.Guid>] [-Filter <String>] [-LocalStor
 ```
 
 ## DESCRIPTION
-{{Fill in the Description}}
+A network region interconnects various parts of a network across multiple geographic areas. 
+
+A network region contains a collection of network sites. For example, if your organization has many sites located in India, then you may choose to designate “India” as a network region.
+
+Location Based Routing is a feature which allows PSTN toll bypass to be restricted for users based upon policy and the user’s geographic location at the time of an incoming or outgoing PSTN call. 
+
+Location-Based Routing leverages the same network regions, sites, and subnets concept that is available in Skype for Business Server. It is now available in O365 for Teams clients. For toll bypass restricted locations, each IP subnet and PSTN gateway for that location are associated to a network site by the administrator. A user’s location is determined by the IP subnet which the user’s Teams endpoint(s) is connected to at the time of a PSTN call. A user may have multiple Teams clients located at different sites, in which case Location-Based Routing will enforce each client’s routing separately depending on the location of its endpoint.
 
 ## EXAMPLES
 
-### Example 1
+###-------------------------- Example 1 --------------------------
+```powershell
+PS C:\> Get-CsTenantNetworkRegion
+```
+
+The command shown in Example 1 returns the list of network regions for the current tenant.
+
+###-------------------------- Example 2 --------------------------
 ```powershell
-PS C:\> {{ Add example code here }}
+PS C:\> Get-CsTenantNetworkRegion -Identity RedmondRegion
 ```
 
-{{ Add example description here }}
+The command shown in Example 2 returns the network region within the scope of RedmondRegion.
 
 ## PARAMETERS
 
 ### -Filter
-{{Fill Filter Description}}
+The Filter parameter allows you to limit the number of results based on filters you specify.
 
 ```yaml
 Type: String
@@ -55,7 +69,7 @@ Accept wildcard characters: False
 ```
 
 ### -Identity
-{{Fill Identity Description}}
+The Identity parameter is a unique identifier that designates the scope. It specifies the collection of tenant network region to be returned.
 
 ```yaml
 Type: XdsGlobalRelativeIdentity
@@ -70,7 +84,7 @@ Accept wildcard characters: False
 ```
 
 ### -LocalStore
-{{Fill LocalStore Description}}
+PARAMVALUE: SwitchParameter
 
 ```yaml
 Type: SwitchParameter
@@ -85,7 +99,7 @@ Accept wildcard characters: False
 ```
 
 ### -Tenant
-{{Fill Tenant Description}}
+Globally unique identifier (GUID) of the tenant account whose network regions are being returned.
 
 ```yaml
 Type: System.Guid

skype/skype-ps/skype/Get-CsTenantNetworkSite.md

@@ -11,6 +11,7 @@ ms.reviewer:
 # Get-CsTenantNetworkSite
 
 ## SYNOPSIS
+Returns information about the network site setting in the tenant. Tenant network site is used for Location Based Routing.
 
 ## SYNTAX
 
@@ -26,21 +27,34 @@ Get-CsTenantNetworkSite [-Tenant <System.Guid>] [-Filter <String>] [-LocalStore]
 ```
 
 ## DESCRIPTION
-{{Fill in the Description}}
+A network site represents a location where your organization has a physical venue, such as offices, a set of buildings, or a campus. Network sites are defined as a collection of IP subnets.
+
+A best practice for Location Bsed Routing (LBR) is to create a separate site for each location which has unique PSTN connectivity.  Each network site must be associated with a network region. Sites may be created as LBR or non-LBR enabled. A non-LBR enabled site may be created to allow LBR enabled users to make PSTN calls when they roam to that site. Note that network sites may also be used for emergency calling enablement and configuration.
+
+Location Based Routing is a feature which allows PSTN toll bypass to be restricted for users based upon policy and the user’s geographic location at the time of an incoming or outgoing PSTN call. 
+
+Location-Based Routing leverages the same network regions, sites, and subnets concept that is available in Skype for Business Server. It is now available in O365 for Teams clients. For toll bypass restricted locations, each IP subnet and PSTN gateway for that location are associated to a network site by the administrator. A user’s location is determined by the IP subnet which the user’s Teams endpoint(s) is connected to at the time of a PSTN call. A user may have multiple Teams clients located at different sites, in which case Location-Based Routing will enforce each client’s routing separately depending on the location of its endpoint.
 
 ## EXAMPLES
 
-### Example 1
+###-------------------------- Example 1 --------------------------
+```powershell
+PS C:\> Get-CsTenantNetworkSite
+```
+
+The command shown in Example 1 returns the list of network sites for the current tenant.
+
+###-------------------------- Example 2 --------------------------
 ```powershell
-PS C:\> {{ Add example code here }}
+PS C:\> Get-CsTenantNetworkSite -Identity siteA
 ```
 
-{{ Add example description here }}
+The command shown in Example 2 returns the network site within the scope of siteA.
 
 ## PARAMETERS
 
 ### -Filter
-{{Fill Filter Description}}
+The Filter parameter allows you to limit the number of results based on filters you specify.
 
 ```yaml
 Type: String
@@ -55,7 +69,7 @@ Accept wildcard characters: False
 ```
 
 ### -Identity
-{{Fill Identity Description}}
+The Identity parameter is a unique identifier that designates the scope. It specifies the collection of tenant network site to be returned.
 
 ```yaml
 Type: XdsGlobalRelativeIdentity
@@ -70,7 +84,7 @@ Accept wildcard characters: False
 ```
 
 ### -LocalStore
-{{Fill LocalStore Description}}
+PARAMVALUE: SwitchParameter
 
 ```yaml
 Type: SwitchParameter
@@ -85,7 +99,7 @@ Accept wildcard characters: False
 ```
 
 ### -Tenant
-{{Fill Tenant Description}}
+Globally unique identifier (GUID) of the tenant account whose network sites are being returned.
 
 ```yaml
 Type: System.Guid

skype/skype-ps/skype/Get-CsTenantNetworkSubnet.md

@@ -11,6 +11,7 @@ ms.reviewer:
 # Get-CsTenantNetworkSubnet
 
 ## SYNOPSIS
+Returns information about the network subnet setting in the tenant. Tenant network subnet is used for Location Based Routing.
 
 ## SYNTAX
 
@@ -26,21 +27,34 @@ Get-CsTenantNetworkSubnet [-Tenant <System.Guid>] [-Filter <String>] [-LocalStor
 ```
 
 ## DESCRIPTION
-{{Fill in the Description}}
+IP subnets at the location where Teams endpoints can connect to the network must be defined and associated to a defined network in order to enforce toll bypass.
+
+Multiple subnets may be associated with the same network site, but multiple sites may not be associated with a same subnet. This association of subnets enables Location-Based routing to locate the endpoints geographically to determine if a given PSTN call should be allowed. Both IPv4 and IPv6 subnets are supported. When determining if a Teams endpoint is located at a site an IPv6 address will be checked for a match first.
+
+Location Based Routing is a feature which allows PSTN toll bypass to be restricted for users based upon policy and the user’s geographic location at the time of an incoming or outgoing PSTN call. 
+
+Location-Based Routing leverages the same network regions, sites, and subnets concept that is available in Skype for Business Server. It is now available in O365 for Teams clients. For toll bypass restricted locations, each IP subnet and PSTN gateway for that location are associated to a network site by the administrator. A user’s location is determined by the IP subnet which the user’s Teams endpoint(s) is connected to at the time of a PSTN call. A user may have multiple Teams clients located at different sites, in which case Location-Based Routing will enforce each client’s routing separately depending on the location of its endpoint.
 
 ## EXAMPLES
 
-### Example 1
+###-------------------------- Example 1 --------------------------
+```powershell
+PS C:\> Get-CsTenantNetworkSubnet
+```
+
+The command shown in Example 1 returns the list of network subnets for the current tenant.
+
+###-------------------------- Example 2 --------------------------
 ```powershell
-PS C:\> {{ Add example code here }}
+PS C:\> Get-CsTenantNetworkSubnet -Identity '2001:4898:e8:25:844e:926f:85ad:dd70'
 ```
 
-{{ Add example description here }}
+The command shown in Example 2 returns the IPv6 format network subnet within the scope of '2001:4898:e8:25:844e:926f:85ad:dd70'.
 
 ## PARAMETERS
 
 ### -Filter
-{{Fill Filter Description}}
+The Filter parameter allows you to limit the number of results based on filters you specify.
 
 ```yaml
 Type: String
@@ -55,7 +69,7 @@ Accept wildcard characters: False
 ```
 
 ### -Identity
-{{Fill Identity Description}}
+The Identity parameter is a unique identifier that designates the scope. It specifies the collection of tenant network subnet to be returned.
 
 ```yaml
 Type: XdsGlobalRelativeIdentity
@@ -70,7 +84,7 @@ Accept wildcard characters: False
 ```
 
 ### -LocalStore
-{{Fill LocalStore Description}}
+PARAMVALUE: SwitchParameter
 
 ```yaml
 Type: SwitchParameter
@@ -85,7 +99,7 @@ Accept wildcard characters: False
 ```
 
 ### -Tenant
-{{Fill Tenant Description}}
+Globally unique identifier (GUID) of the tenant account whose network subnets are being returned.
 
 ```yaml
 Type: System.Guid