Merge branch 'master' into patch-28

chrisda · web-flow · commit 7f42fb7ea1a0 · 2020-02-04T14:09:33.000-08:00
diff --git a/exchange/docs-conceptual/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2.md b/exchange/docs-conceptual/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2.md
@@ -18,7 +18,7 @@ description: "Learn how to download and use the Exchange Online PowerShell V2 mo
 
 # Use the Exchange Online PowerShell V2 module
 
-The Exchange Online PowerShell V2 module (abbreviated as the EXO V2 module) enables admins to connect to their Exchange Online environment in Office 365 to retrieve data, create new objects, update existing objects, remove objects as well as configure Exchange Online & its features.
+The Exchange Online PowerShell V2 module (abbreviated as the EXO V2 module) enables admins to connect to their Exchange Online environment in Office 365 to retrieve data, create new objects, update existing objects, remove objects as well as configure Exchange Online and its features.
 
 ## Report bugs and issues
 
@@ -34,9 +34,11 @@ Connect-ExchangeOnline -EnableErrorReporting -LogDirectoryPath <Path to store lo
 
 ## How the EXO V2 module works
 
-The Exchange Online PowerShell V2 module contains a small set of new cmdlets that are optimized for bulk data retrieval scenarios (think: thousands and thousands of objects). It also contains the 700 or more older remote PowerShell cmdlets baked into the same module. Note that after you install the EXO V2 module from the PowerShell Gallery, you only see new cmdlets in the module. You'll see the older remote PowerShell cmdlets after you create a session to connect to your Exchange Online environment. All the cmdlets in the V2 module use Modern auth for authentication. You can't use Basic auth in the EXO V2 module.
+The Exchange Online PowerShell V2 module contains a small set of new cmdlets that are optimized for bulk data retrieval scenarios (think: thousands and thousands of objects). Until you create a session to connect to your Exchange Online organization, you'll only see these new cmdlets in the module. After you connect to your Exchange Online organization, you'll see all of the older remote PowerShell cmdlets.
 
-The new cmdlets in the EXO V2 module are meant to replace their older, less efficient equivalents. However, the original cmdlets are still available in the EXO V2 module for backwards compatibility.
+The EXO V2 module use Modern authentication for all cmdlets. You can't use Basic authentication in the EXO V2 module; however, you still need to configure the Basic authentication setting in WinRM as described later in this topic.
+
+The new cmdlets in the EXO V2 module are meant to replace their older, less efficient equivalents. However, the original cmdlets are still available in the EXO V2 module for backwards compatibility **after** you create a session to connect to your Exchange Online organization.
 
 The new cmdlets in the EXO V2 module are listed in the following table:
 
@@ -57,7 +59,7 @@ The new cmdlets in the EXO V2 module are listed in the following table:
 
 You can download the EXO V2 module from the PowerShell gallery [here](https://www.powershellgallery.com/packages/ExchangeOnlineManagement/).
 
-> [!NOTE]
+> [!NOTE] 
 > The latest version of PowerShell that's currently supported for the EXO V2 module is PowerShell 5.1. Support for PowerShell 6.0 or later is currently a work in progress and will be released soon. This also implies that EXO PowerShell V2 module won't work in Linux or Mac as of now. Support for Linux and Mac is a work in progress and will be announced soon.
 
 ### What do you need to know before you begin?
@@ -88,7 +90,7 @@ You can download the EXO V2 module from the PowerShell gallery [here](https://ww
   winrm get winrm/config/client/auth
   ```
 
-  If you don't see the value `Basic = true`, you need to run this command to enable basic authentication for WinRM:
+  If you don't see the value `Basic = true`, you need to run this command to enable Basic authentication for WinRM:
 
   ```
   winrm set winrm/config/client/auth @{Basic="true"}
@@ -98,6 +100,9 @@ You can download the EXO V2 module from the PowerShell gallery [here](https://ww
 
   > The WinRM client cannot process the request. Basic authentication is currently disabled in the client configuration. Change the client configuration and try the request again.
 
+  > [!NOTE] 
+  > We never send the username and password combination here, but the Basic auth header is required to transport the session's OAuth token, since the client-side WinRM implementation has no support for OAuth.
+
 ### Install the EXO V2 module
 
 To install the EXO V2 module for the first time, run the following commands:
@@ -123,11 +128,11 @@ To install the EXO V2 module for the first time, run the following commands:
    ```
 
    **Notes**:
-
+   
    - You need to configure this setting only once on your computer. Read more about execution policies [here](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_execution_policies).
-
+   
    - If you don't do this step, you'll receive the following error when you try to connect:
-
+   
      > Files cannot be loaded because running scripts is disabled on this system. Provide a valid certificate with which to sign the files.
 
 3. Close and re-open the elevated Windows PowerShell window to get the changes from the previous steps.
@@ -272,7 +277,7 @@ The following example returns all properties for the 10 mailboxes:
 Get-EXOMailbox -ResultSize 10 -PropertySets All
 ```
 
-> [!NOTE]
+> [!NOTE]  
 > We highly discourage using the _PropertySets_ parameter with the value `All` because it slows down the cmdlet and reduces reliability. Always use the _PropertySets_ and _Properties_ parameters to retrieve only the requires properties.
 
 ## Release notes
diff --git a/exchange/exchange-ps/exchange/organization/Set-OrganizationConfig.md b/exchange/exchange-ps/exchange/organization/Set-OrganizationConfig.md
@@ -30,6 +30,7 @@ Set-OrganizationConfig
  [-AppsForOfficeEnabled <Boolean>]
  [-AsyncSendEnabled <Boolean>]
  [-AuditDisabled <Boolean>]
+ [-AutodiscoverPartialDirSync <Boolean>]
  [-AutoEnableArchiveMailbox <Boolean>]
  [-AutoExpandingArchive]
  [-BookingsEnabled <Boolean>]
@@ -542,6 +543,26 @@ Accept pipeline input: False
 Accept wildcard characters: False
 ```
 
+### -AutodiscoverPartialDirSync
+This parameter is available only in the cloud-based service.
+
+The AutodiscoverPartialDirSync parameter is for scenarios where tenants have Directory Synced some of their Active Directory users into the cloud, but still have on-premises Exchange users that are not Directory Synced. Setting this parameter to $true will cause unknown users to be redirected to the on-premises endpoint and will allow on-premises users to discover their mailbox automatically. Online email addresses will be susceptible to enumeration. We recommend full Directory Sync for all Active Directory users and leaving this parameter with the default $false.
+
+After you enable AutodiscoverPartialDirSync, it will take approximately 3 hours to fully saturate across the cloud.
+
+```yaml
+Type: Boolean
+Parameter Sets: Default
+Aliases:
+Applicable: Exchange Online
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
 ### -AutoEnableArchiveMailbox
 This parameter is available only in the cloud-based service.
 
diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOSiteDataEncryptionPolicy.md b/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOSiteDataEncryptionPolicy.md
@@ -14,7 +14,7 @@ ms.reviewer:
 
 ## SYNOPSIS
 
-.
+Validates the encryption of a Group Site, Team Site, or OneDrive for Business site if a Customer Key has been registered for the site.
 
 ## SYNTAX
 
@@ -24,7 +24,9 @@ Get-SPOSiteDataEncryptionPolicy [-Identity] <SpoSitePipeBind> [<CommonParameters
 
 ## DESCRIPTION
 
-.
+When a Customer Key has been configured in the Azure tenant, it is possible to set and subsequently verify the encryption status of a SharePoint Online or OneDrive for Business site. This cmdlet verifies the encryption status of the particular site.
+
+This cmdlet will return an error if the Azure tenant has not been configured with a Customer Key. See the Related Links section for more information on how to configure the Customer Key.
 
 ## EXAMPLES
 
@@ -34,13 +36,13 @@ Get-SPOSiteDataEncryptionPolicy [-Identity] <SpoSitePipeBind> [<CommonParameters
 Get-SPOSiteDataEncryptionPolicy https://contoso.sharepoint.com/sites/Research
 ```
 
-.
+Verifies the encryption of the site https://contoso.sharepoint.com/sites/Research.
 
 ## PARAMETERS
 
 ### -Identity
 
-.
+The URL of the Site Collection.
 
 ```yaml
 Type: SpoSitePipeBind
@@ -58,4 +60,28 @@ Accept wildcard characters: False
 
 This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction, and -WarningVariable. For more information, see [about_CommonParameters](https://go.microsoft.com/fwlink/p/?LinkID=113216).
 
-## NOTES
+## OUTPUTS
+### System.String
+
+The URI of the primary key.
+
+### System.String
+
+The URI of the secondary key.
+
+### System.Object
+
+The encryption status for the geo. Possible states include:
+
+* Unregistered: Customer Key encryption has not yet been applied.
+* Registering: Customer Key encryption has been applied and your files are in the process of being encrypted. If your geo is in this state, you'll also be shown information on what percentage of sites in the geo are complete so that you can monitor encryption progress.
+* Registered: Customer Key encryption has been applied, and all files in all sites have been encrypted.
+* Rolling: A key roll is in progress. If your geo is in this state, you'll also be shown information on what percentage of sites have completed the key roll operation so that you can monitor progress.
+
+## RELATED LINKS
+
+[Register-SPODataEncryptionPolicy](https://docs.microsoft.com/powershell/module/sharepoint-online/register-spodataencryptionpolicy)
+
+[Controlling your data in Office 365 using Customer Key](https://docs.microsoft.com/microsoft-365/compliance/controlling-your-data-using-customer-key)
+
+[Office 365: Setting up Customer Key for SharePoint Online and OneDrive for Business](https://docs.microsoft.com/microsoft-365/compliance/controlling-your-data-using-customer-key#office-365-setting-up-customer-key-for-sharepoint-online-and-onedrive-for-business)
diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOUnifiedGroup.md b/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOUnifiedGroup.md
@@ -14,7 +14,7 @@ ms.reviewer:
 
 ## SYNOPSIS
 
-.
+Retrieves the Preferred Data Location for the specified Office 365 Group.
 
 ## SYNTAX
 
@@ -24,23 +24,22 @@ Get-SPOUnifiedGroup [-GroupAlias] <string> [<CommonParameters>]
 
 ## DESCRIPTION
 
-.
+Retrieves the Preferred Data Location (PDL) for the specified Office 365 Group. The customer tenant must be multi-geo enabled.
 
 ## EXAMPLES
 
 ### Example 1
 
 ```powershell
-Get-SPOUnifiedGroup -GroupAlias <string>
+Get-SPOUnifiedGroup -GroupAlias EUTeam
 ```
-
-.
+Returns the PDL for the Office 365 Group named 'EUTeam'.
 
 ## PARAMETERS
 
 ### -GroupAlias
 
-.
+The alias of the Office 365 Group.
 
 ```yaml
 Type: String
@@ -59,3 +58,7 @@ Accept wildcard characters: False
 This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction, and -WarningVariable. For more information, see [about_CommonParameters](https://go.microsoft.com/fwlink/p/?LinkID=113216).
 
 ## NOTES
+
+## RELATED LINKS
+
+[Move a SharePoint site to a different geo location](https://docs.microsoft.com/office365/enterprise/move-sharepoint-between-geo-locations)
diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOUnifiedGroupMoveState.md b/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOUnifiedGroupMoveState.md
@@ -14,7 +14,7 @@ ms.reviewer:
 
 ## SYNOPSIS
 
-.
+Returns the state of an Office 365 Group move between Preferred Data Locations.
 
 ## SYNTAX
 
@@ -24,23 +24,23 @@ Get-SPOUnifiedGroupMoveState [-GroupAlias] <string> [<CommonParameters>]
 
 ## DESCRIPTION
 
-.
+Retrieves the state of the Office 365 Group move to the Preferred Data Location (PDL) for the specified. The customer tenant must be multi-geo enabled.
 
 ## EXAMPLES
 
 ### Example 1
 
 ```powershell
-Get-SPOUnifiedGroupMoveState -GroupAlias <string>
+Get-SPOUnifiedGroupMoveState -GroupAlias EUTeam
 ```
 
-.
+Returns the status of the move between geos for the Office 365 Group named 'EUTeam'.
 
 ## PARAMETERS
 
 ### -GroupAlias
 
-.
+The alias of the Office 365 Group.
 
 ```yaml
 Type: String
@@ -92,4 +92,22 @@ Accept wildcard characters: False
 
 This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction, and -WarningVariable. For more information, see [about_CommonParameters](https://go.microsoft.com/fwlink/p/?LinkID=113216).
 
+## OUTPUTS
+
+### System.Object
+
+The move status for the Office 365 Group. Possible values are:
+
+* Ready to Trigger: The move has not started.
+* Scheduled: The move is in queue but has not yet started.
+* InProgress (n/4): The move is in progress in one of the following states: Validation (1/4), Backup (2/4), Restore (3/4), Cleanup (4/4).
+* Success: The move has completed successfully.
+* Failed: The move failed.
+
 ## NOTES
+
+You can also apply the `-Verbose` option to see additional information about the move.
+
+## RELATED LINKS
+
+[Move a SharePoint site to a different geo location](https://docs.microsoft.com/office365/enterprise/move-sharepoint-between-geo-locations)
diff --git a/sharepoint/sharepoint-ps/sharepoint-online/New-SPOMigrationEncryptionParameters.md b/sharepoint/sharepoint-ps/sharepoint-online/New-SPOMigrationEncryptionParameters.md
@@ -14,7 +14,7 @@ ms.reviewer:
 
 ## SYNOPSIS
 
-{{Fill in the Synopsis}}
+Creates a new random encryption key for a migration job or package.
 
 ## SYNTAX
 
@@ -24,28 +24,43 @@ New-SPOMigrationEncryptionParameters [<CommonParameters>]
 
 ## DESCRIPTION
 
-{{Fill in the Description}}
+Creates a random encryption key for submission of a migration job or creation of a migration package. For use with [`Submit-SPOMigrationJob`](), [`ConvertTo-SPOMigrationEncryptedPackage`](ConvertTo-SPOMigrationEncryptedPackage.md), and [`Set-SPOMigrationPackageAzureSource`](Set-SPOMigrationPackageAzureSource.md) in the `-EncryptedParameter` parameter for each cmdlet.
 
 ## EXAMPLES
 
 ### EXAMPLE 1
 
 ```powershell
-{{ Add example code here }}
+$o = New-SPOMigrationEncryptionParameters
 ```
 
-{{ Add example description here }}
+Outputs a random encryption key and saves it in the `$o` variable.
 
 ## PARAMETERS
 
 ### CommonParameters
 
 This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction, and -WarningVariable. For more information, see [about_CommonParameters](https://go.microsoft.com/fwlink/?LinkID=113216).
 
+## OUTPUTS
+
+### System.Byte
+
+EncryptionKey: The randomly generated encryption key using [System.Security.Cryptography.AesCryptoServiceProvider](https://docs.microsoft.com/dotnet/api/system.security.cryptography.aescryptoserviceprovider) class.
+
+### Microsoft.Online.SharePoint.Migration.SPMigrationJobEncryptionMethod
+
+EncryptionMethod: The encryption algorithm used to generate the EncryptionKey. Currently hardcoded to AES256BC.
+
 ## RELATED LINKS
 
+[Submit-SPOMigrationjob](Submit-SPOMigrationJob.md)
+
+[ConvertTo-SPOMigrationEncryptedPackage](ConvertTo-SPOMigrationEncryptedPackage.md)
+
+[Set-SPOMigrationPackageAzureSource](Set-SPOMigrationPackageAzureSource.md)
+
 [Introduction to the SharePoint Online management shell](https://support.office.com/en-us/article/introduction-to-the-sharepoint-online-management-shell-c16941c3-19b4-4710-8056-34c034493429)
 
 [SharePoint Online Management Shell Download](https://www.microsoft.com/en-US/download/details.aspx?id=35588)
 
-[Get-SPOAppErrors](Get-SPOAppErrors.md)
diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Remove-SPOMultiGeoCompanyAllowedDataLocation.md b/sharepoint/sharepoint-ps/sharepoint-online/Remove-SPOMultiGeoCompanyAllowedDataLocation.md
@@ -14,7 +14,7 @@ ms.reviewer:
 
 ## SYNOPSIS
 
-.
+Use this cmdlet to remove a multi geo allowed location.
 
 ## SYNTAX
 
@@ -24,23 +24,22 @@ Remove-SPOMultiGeoCompanyAllowedDataLocation [-Location] <string> [-WhatIf] [-Co
 
 ## DESCRIPTION
 
-.
+Removes a specified multi-geo location that was previously allowed by [Set-SPOMultiGeoCompanyAllowedDataLocation](Set-SPOMultiGeoCompanyAllowedDataLocation.md).
 
 ## EXAMPLES
 
 ### Example 1
 
 ```powershell
-
+Remove-SPOMultiGeoCompanyAllowedDataLocation -Location AUS
 ```
-
-.
+Removes AUS (Australia) as an allowed mutli-geo location.
 
 ## PARAMETERS
 
 ### -Location
 
-.
+The Preferred Data Location (PDL) to remove.
 
 ```yaml
 Type: String
@@ -93,3 +92,7 @@ Accept wildcard characters: False
 This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction, and -WarningVariable. For more information, see [about_CommonParameters](https://go.microsoft.com/fwlink/p/?LinkID=113216).
 
 ## NOTES
+
+## RELATED LINKS
+
+[Set-SPOMultiGeoCompanyAllowedDataLocation](Set-SPOMultiGeoCompanyAllowedDataLocation.md)
diff --git a/skype/skype-ps/skype/Get-CsTeamsMobilityPolicy.md b/skype/skype-ps/skype/Get-CsTeamsMobilityPolicy.md
@@ -34,6 +34,9 @@ The TeamsMobilityPolicy allows Admins to control Teams mobile usage for users.
 
 The Get-CsTeamsMobilityPolicy cmdlet allows administrators to get all teams mobility policies.
 
+NOTE: Please note that this cmdlet was deprecated and then removed from this PowerShell module. This reference will continue to be listed here for legacy purposes.
+
+
 ## EXAMPLES
 
 ### Example 1
diff --git a/skype/skype-ps/skype/Set-CsOnlinePSTNGateway.md b/skype/skype-ps/skype/Set-CsOnlinePSTNGateway.md
diff --git a/teams/teams-ps/teams/teams.md b/teams/teams-ps/teams/teams.md
