3.0.0-beta.1

Author: GruberMarkus

docs/CHANGELOG.md

@@ -16,7 +16,7 @@
 -->
 
 
-## <a href="https://github.com/GruberMarkus/Export-RecipientPermissions/releases/tag/vX.X.X" target="_blank">vX.X.X</a> - YYYY-MM-DD
+## <a href="https://github.com/GruberMarkus/Export-RecipientPermissions/releases/tag/v3.0.0-beta.1" target="_blank">v3.0.0-beta.1</a> - 2023-01-11
   _**Breaking:** Microsoft removes support for Remote PowerShell connections to Exchange Online starting June 1, 2023. See https://techcommunity.microsoft.com/t5/exchange-team-blog/announcing-deprecation-of-remote-powershell-rps-protocol-in/ba-p/3695597 for details.  
   Export-RecipientPermissions no longer uses Remote PowerShell to connect to Exchange Online and to Exchange on-premises. This brings some possibly breaking changes, which are detailed in the following release notes._
 ### Changed
@@ -32,8 +32,8 @@
     - On-prem only:
       - .Identity is now the canonical name (CN) only and no longer has the sub attributes .DomainId and .Parent
         - All the data formerly held in the sub attributes is still there, as .Identity is in the 'example.com/OU1/OU2/ObjectA' format  
+  - Reduced the default value of '`ParallelJobsExchange`' from '`$ExchangeConnectionUriList.count * 3`' to '`$ExchangeConnectionUriList.count`' as local Exchange PowerShell sessions are not as stable as Remote PowerShell sessions 
 - Adopted sample code and documentation to reflect changes in the '`$Grantor`' and '`$Trustee`' variables
-- Reduced the default value of '`ParallelJobsExchange`' from '`$ExchangeConnectionUriList.count * 3`' to '`$ExchangeConnectionUriList.count`' as local Exchange PowerShell sessions are not as stable as Remote PowerShell sessions 
 - Use Get-EXO* cmdlets in Exchange Online where possible
 - Upgrade to ExchangeOnlineManagement v3.1.0
 ### Added