Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
v3.0.0 - 2023-01-13
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
$Grantor
' and '$Trustee
' lose some sub attributes, so you may have to adopt your 'GrantorFilter
' and 'TrusteeFilter
' code:.RecipientType.Value
' is now '.RecipientType
'.RecipientTypeDetails.Value
' is now '.RecipientTypeDetails
'.PrimarySmtpAddress
' no longer has the sub attributes .Local, .Domain and .Address.EmailAddresses
' (an array) no longer has the sub attributes .PrefixString, .IsPrimaryAddress, .SmtpAddress and .ProxyAddressString.Identity
' is now the canonical name (CN) only and no longer has the sub attributes .DomainId and .ParentParallelJobsExchange
' from '$ExchangeConnectionUriList.count * 3
' to '$ExchangeConnectionUriList.count
' as local Exchange PowerShell sessions are not as stable as Remote PowerShell sessions$Grantor
' and '$Trustee
' variablesAdded
ExportModerators
', 'ExportRequireAllSendersAreAuthenticated
', 'ExportAcceptMessagesOnlyFrom
', 'ExportResourceDelegates
'. See 'README
' for details.README
': 'I receive an error message when connecting to Exchange on premises'Fixed