-
Title
Active Roles Web Interface fails from showing EXO objects -
Description
No EXO objects appear in the Web Interface:
Note that Active Roles v8.0.1 LTS shows below error when searching EXO objects via the QuicSearch functionality:
-
Cause
This issue occurs when connecting to EXO natively via a Script Module, see sample below:
Function EXOTest() {
$logfile = "C:\Temp\EXOConnection.log"
$Credentials = "C:\Software\AzO365Credentials.xml"
$MyCredentials = Import-Clixml -Path $Credentials
Connect-ExchangeOnline -ShowBanner:$false -Credential $MyCredentials
...
Disconnect-ExchangeOnline -Confirm:$false | Out-Null
}
The Disconnect-ExchangeOnline cmdlet closes all EXO connections created by the ARS Workflow as well as the EXO connection created by the ARS WI causing this issue. -
Resolution
Status:
The Active Roles Product Team has raised Enhancement request #432180 to disconnect the last EXO connection created by the last executed Workflow so that no other EXO connections are affected.
Workaround1:
Use the Active Roles Workflow builtin activity called "O365 script execution configuration" to connect to EXO:
Workaround2:
Install the ExchangeOnlineManagement module v3.2.0 and use switch prefix to disconnect the exact connection created by the Workflow when it last run. See sample below:Connect-ExchangeOnline -Prefix "MyConnection"
$myConnections = (Get-ConnectionInformation).Where({$_.ModulePrefix -eq "MyConnection"})
$myConnection | Disconnect-ExchangeOnline -Confirm:$false