The following error occurs while configuring Azure AD registered app under Archive Collectors - Exchange Online in Arctera Admin portal:
Powershell connection attempt failed, check your information and try again. Exchange Web Services connection attempt failed, check your information and try again. Graph API token generation attempt failed, check your information and app api permissions and try again.

In order for the O365 Sync configuration to save successfully in Arctera a self-signed cert needs to be used as per Microsoft's documentation HERE in Step 3. This is also detailed in the Setting up modern authentication in Azure AD for Exchange Online sync. Not using a self-signed cert will cause Arctera Unified Platform to fail to decrypt it and the settings won't save.
Review the API permissions and roles for the registered app in Azure AD, and ensure they are correctly applied.
Review the ClientID, Tenant Name, and certificate password are correct.
NOTE: For all above scenarios please review the Step-By-Step Guide on settings up Modern Authentication for the O365 Sync.
If the connection still won't work then use the following steps to connect to Exchange Online from a PowerShell prompt with administrator privileges.
Edit the lines below with the correct information, copy all of it, copy it into the PowerShell prompt, and hit ENTER:
## set the Tenant ID (directory ID or the available primary domain).
$tenantID = 'demo.onmicrosoft.com'
## Set the Exo_V2_App Application (client) ID
$appID = '8c8301ba-23a8-4705-a658-63a2d0e4bfd4'
## Set the certificate file path (.pfx). The cert location will be wherever you ran the command from to create the Self-Signed Cert from and if you followed this article it will be at the below path.
$CertificateFilePath = 'C:\EVSyncCert.pfx'
## Get the PFX password
$pfxPassword = ''
## Connect to Exchange Online
Connect-ExchangeOnline -CertificateFilePath $CertificateFilePath -CertificatePassword (ConvertTo-SecureString -String $pfxPassword -AsPlainText -Force) -AppID $appID -Organization $tenantID
Ensure users information can be retrieved via the ExoMailbox cmdlet. If successful then it should work, but if not please create a case with Support.
Get-ExoMailbox -Identity john.smith@demo.onmicrosoft.com
This can happen for many reasons. Common causes listed:
To resolve the issue investigate the following solutions:
When trying to save the Azure AD registered app configuration for the Exchange Online O365 Sync connector it fails to connect due to a generic PowerShell connection error.