Issue

The Office 365 module logs:
Error: A positional parameter cannot be found that accepts argument when Archive Shuttle is collecting mailboxes.

2018-10-11 11:55:32Z|5856| 11|TRACE| GetDeletedUsers|Checking user - [er'ma'sa@example.com]
2018-10-11 11:55:32Z|5856| 11|TRACE| ExecuteCommand|ExecutePsCommand | Get-Msoluser -SearchString 'er'ma'sa'
2018-10-11 11:55:32Z|5856| 11|ERROR| ProcessPowerShellErrors|Errors were detected. Review the following:
2018-10-11 11:55:32Z|5856| 11|ERROR| ProcessPowerShellErrors|A positional parameter cannot be found that accepts argument 'masa'. System.Array SynchronousExecuteEnumerate(System.Object, System.Collections.Hashtable, Boolean)
A positional parameter cannot be found that accepts argument 'masa'.
at System.Management.Automation.CmdletParameterBinderController.VerifyArgumentsProcessed(ParameterBindingException originalBindingException)
at System.Management.Automation.CmdletParameterBinderController.BindCommandLineParametersNoValidation(Collection`1 arguments)
at System.Management.Automation.CmdletParameterBinderController.BindCommandLineParameters(Collection`1 arguments)
at System.Management.Automation.CommandProcessor.BindCommandLineParameters()
at System.Management.Automation.CommandProcessorBase.DoPrepare(IDictionary psDefaultParameterValues)
at System.Management.Automation.Internal.PipelineProcessor.Start(Boolean incomingStream)
at System.Management.Automation.Internal.PipelineProcessor.SynchronousExecuteEnumerate(Object input, Hashtable errorResults, Boolean enumerate)

Solution

This error is returned when an email address contains special character(s) in the prefix. For example, er’ma’sa@example.com. Archive Shuttle is running a PowerShell command that logs the error above:

Get-Msoluser -SearchString 'er'ma'sa'

Apostrophes are valid characters in Office 365 and Archive Shuttle is able to ingest data into such mailbox. Archive Shuttle will log the error but will continue to ingest the items.
The error stems from PowerShell where Microsoft does not have the error resolved.
It’s also possible that the PowerShell script is incorrect in Archive Shuttle.
Microsoft has a knowledge base article for special characters: https://support.microsoft.com/en-us/help/2439357/error-message-when-you-try-to-create-a-user-name-that-contains-a-speci