I configure it this morning by following the documentation by adding a password on Client location,configuring a new app registration and setting the O365 API permissions(3 of them)
I have configure a single Client by adding the tenandid,client value and secret value(no not the id
)Get MSOL status seems to pass partially as I the probe date changes and a few of the grey "lights" turn red or green
But when scanning a Client,none of the data is able to be retrieved
Checking the commands I think it appears that the Connect-Msolservice part in one of the scripts is the root cause
Output:
Connect-Msolservice : One or more errors occurred. At C:\Windows\temp\Office365\OOFStatus.ps1:249 char:2 + Connect-Msolservice -cred $cred + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : OperationStopped: (:) [Connect-MsolService], AggregateException + FullyQualifiedErrorId : System.AggregateException,Microsoft.Online.Administration.Automation.ConnectMsolService Method not found: 'Microsoft.Identity.Client.PublicClientApplicationBuilder Microsoft.Identity.Client.Broker.BrokerExtension.WithBroker(Microsoft.Identity.Client.PublicClientApplicationBuilder, Microsoft.Identity.Client.BrokerOptions)'. At C:\Program Files\WindowsPowerShell\Modules\ExchangeOnlineManagement\3.7.2\netFramework\ExchangeOnlineManagement.psm1:754 char:21 + throw $_.Exception.InnerException; + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : OperationStopped: (:) [], MissingMethodException + FullyQualifiedErrorId : Method not found: 'Microsoft.Identity.Client.PublicClientApplicationBuilder Microsoft.Id entity.Client.Broker.BrokerExtension.WithBroker(Microsoft.Identity.Client.PublicClientApplicationBuilder, Microsof t.Identity.Client.BrokerOptions)'. WARNING: The version '1.4.8.1' of module 'PackageManagement' is currently in use. Retry the operation after closing the applications.
Now I know this plugin has been updated quite a while back and Microsoft has been moving lots of stuff around to use graph instead.
Could the registered app API permission be the issue?
Theres also this from the exec_MSOLStatus.ps1 script:
#Endpoint URI to get Service Communication Messages
$Uri = "https://manage.office.com/api/v1.0/$Ten ... s/Messages"
#Get the last run time of this script from the registry and query for incidents happened or updates posted after that time only
$CurrentDateTime = (Get-Date).ToUniversalTime()
$CurrentDateTime = $CurrentDateTime.ToString("MM/dd/yyyy HH:mm:ss")
$LastRunTimeOfThisScript = GetLastRunTimeFromReg $CurrentDateTime
$Culture = Get-Culture
#Call the API to Update the property, look for incidents only ($_.MessageType -eq "Incident" -and)-and (($_.LastUpdatedTime).ToDateTime($Culture)).ToUniversalTime() -gt $LastRunTimeOfThisScript
$Responses = (Invoke-RestMethod -Uri $uri -Headers $Headers -Method Get).Value | Where { $_.Workload -in ($Workloads) }
The $uri immediately returns a 404 - File or directory not found
I really would like this to work as this is quite an exciting thing to play with
