Merge branch 'master' into patch-2

Author: kenwith

exchange/docs-conceptual/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2.md

@@ -21,12 +21,7 @@ description: "Learn how to download and use the Exchange Online PowerShell V2 mo
 The Exchange Online PowerShell V2 module (abbreviated as the EXO V2 module) enables admins to connect to their Exchange Online environment in Microsoft 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
-
-The Exchange Online PowerShell V2 module is currently in Preview. If you have any feedback, concerns, or are facing any issues with the EXO V2 module, contact us at exocmdletpreview[at]service[dot]microsoft[dot]com (email address intentionally obscured to help prevent spam).
-
-When you report an issue, be sure to include the log files in your email message.
-
-To generate the log files, replace \<Path to store log file\> with the output folder you want, and run the following command:
+When you report an issue, be sure to include the log files in your email message. To generate the log files, replace \<Path to store log file\> with the output folder you want, and run the following command:
 
 ```PowerShell
 Connect-ExchangeOnline -EnableErrorReporting -LogDirectoryPath <Path to store log file> -LogLevel All
@@ -275,7 +270,21 @@ Get-EXOMailbox -ResultSize 10 -PropertySets All
 
 ## Release notes
 
-### Current release: Version 0.4578.0
+### Current release: Version 1.0.1
+
+- This is the General Availability (GA) version of the EXO PowerShell V2 Module. It is stable and ready for use in production environments.
+
+- Get-ExoMobileDeviceStatistics cmdlet now supports Identity parameter.
+
+- Improved reliability of session auto-reconnect in certain cases where a script was running for ~50 minutes and threw a "Cmdlet not found" error due to a bug in auto-reconnect logic.
+
+- Fixed data-type issues of two commonly used "User" and "MailboxFolderUser" attributes for easy migration of scripts.
+
+- Enhanced support for filters as it now supports four more operators: EndsWith, Contains, Not and NotLike support. Check online documentation for attributes that aren't supported in filters.
+
+### Previous releases
+
+#### Version 0.4578.0
 
 - Added support for configuring the Briefing Email for your organization at the user level with **Set-UserBriefingConfig** and **Get-UserBriefingConfig** cmdlets.
 
@@ -291,8 +300,6 @@ Get-EXOMailbox -ResultSize 10 -PropertySets All
 
 - Optimized memory usage when a session is created by re-using any existing module with a new session instead of creating a new one every time session is imported.
 
-### Previous releases
-
 #### Version 0.4368.1
 
 - Added support for Security & Compliance Center PowerShell cmdlets using the **Connect-IPPSSession** cmdlet.

sharepoint/docs-conceptual/sharepoint-pnp/sharepoint-pnp-cmdlets.md

@@ -20,6 +20,7 @@ If your main OS is Windows 10, or if you have [PowerShellGet](https://github.com
 |**SharePoint Version**|**Command to install**|
 |------------------|------------------|
 |SharePoint Online|```Install-Module SharePointPnPPowerShellOnline ```|
+|SharePoint 2019|```Install-Module SharePointPnPPowerShell2019```|
 |SharePoint 2016|```Install-Module SharePointPnPPowerShell2016```|
 |SharePoint 2013|```Install-Module SharePointPnPPowerShell2013```|
 

sharepoint/sharepoint-ps/sharepoint-server/Remove-SPAccessServicesDatabaseServer.md

@@ -13,7 +13,7 @@ ms.reviewer:
 # Remove-SPAccessServicesDatabaseServer
 
 ## SYNOPSIS
-{{Fill in the Synopsis}}
+Removes a server configured to host Access Services databases.
 
 
 ## SYNTAX
@@ -26,23 +26,24 @@ Remove-SPAccessServicesDatabaseServer [-ServiceContext] <SPServiceContextPipeBin
 ```
 
 ## DESCRIPTION
-{{Fill in the Description}}
+This cmdlet removes an Access Services database server hosting Access Services databases.
 
 
 ## EXAMPLES
 
 ### ------------------EXAMPLE------------------
 ```
- {{ Add example code here }}
+Remove-SPAccessServicesDatabaseServer -DatabaseServer SQLSVR01 -DatabaseServerGroup DEFAULT
 ```
 
-{{ Add example description here }}
-
+This example removes the SQL Server named SQLSVR01 from the DEFAULT group as an Access Services database server.
 
 ## PARAMETERS
 
 ### -AssignmentCollection
-{{Fill AssignmentCollection Description}}
+Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used.
+
+When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur.
 
 ```yaml
 Type: SPAssignmentCollection
@@ -74,7 +75,7 @@ Accept wildcard characters: False
 ```
 
 ### -DatabaseServer
-{{Fill DatabaseServer Description}}
+Specifies the name of the SQL Server.
 
 ```yaml
 Type: AccessServicesDatabaseServerPipeBind
@@ -90,7 +91,7 @@ Accept wildcard characters: False
 ```
 
 ### -DatabaseServerGroup
-{{Fill DatabaseServerGroup Description}}
+The name of the Access Services database server group containing the SQL Server object to remove.
 
 ```yaml
 Type: AccessServicesDatabaseServerGroupPipeBind
@@ -106,7 +107,7 @@ Accept wildcard characters: False
 ```
 
 ### -Force
-{{Fill Force Description}}
+Prompts you for confirmation before running the cmdlet.
 
 ```yaml
 Type: SwitchParameter
@@ -122,7 +123,7 @@ Accept wildcard characters: False
 ```
 
 ### -ServiceContext
-{{Fill ServiceContext Description}}
+Specifies the service context.
 
 ```yaml
 Type: SPServiceContextPipeBind