ISSUE: Scan Shortcuts step fails with error 'Guid should contain 32 digits with 4 dashes'

Overview

The Shortcut Scan step fails with the error below:

Guid should contain 32 digits with 4 dashes (xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx). [ProcessResult]

Unfortunately, this error is not helpful.  The actual error is in the Exchange backend log. 

2023-07-06T16:01:25|DEBUG|ABC Co|192.168.150.254|T:318|Execute_GetEVMailArchiveShortcuts | ||2 |eb009091-f524-4fb8-825c-0f18bba84a32| ||Command: [GetEVMailArchiveShortcuts] | Id: [eb009091-f524-4fb8-825c-0f18bba84a32] is starting.
2023-07-06T16:01:25|INFO |ABC Co|192.168.150.254|T:318|Execute_GetEVMailArchiveShortcuts | ||2 |eb009091-f524-4fb8-825c-0f18bba84a32| ||Starting: Scanning for EVShortcuts Mmm@mydomain.com/2. Is O365: True. Target: Mailbox
2023-07-06T16:01:25|INFO |ABC Co|192.168.150.254|T:78 |CommandExecutor | || || ||Having Slots for 225 Ingestion Commands and Received 0 from DB Command Queue (Processing: 0)
2023-07-06T16:01:25|ERROR|ABC Co|192.168.150.254|T:318|ScriptBase | ||2 |eb009091-f524-4fb8-825c-0f18bba84a32| ||Cannot parse ClientId. Value: [f74404a2-0fd8-4ee5-8aa2-2 60d253135a5]

Cause

Notice there is a space in the "Value"  between the 2 and 6 highlighted above. This is the ClientID (app id) that is entered in the Oauth configuration within the Credential Editor.  

Solution

Modify the Oauth config entry in the Credential Editor with the correct ID and in the correct format (no spaces).  

The following article explains how to use the Credential Editor.