Blog Post

Microsoft Sentinel Blog
4 MIN READ

Help Protect your Exchange Environment With Microsoft Sentinel

nilepagn's avatar
nilepagn
Icon for Microsoft rankMicrosoft
Aug 09, 2023
 TL;DR; Sentinel + Exchange Servers or Exchange Online = better protected   [ Spoiler ]   We recently published two solutions in the Sentinel content hub catalog to assist you with better...
NicolasLepagnez_1-1689176621248.png
Updated Dec 11, 2024
Version 3.0
analytics
Content
data collection
solutions
what's new
Workbooks
nilepagn's avatar
Icon for Microsoft rankMicrosoft
Joined April 06, 2017
View Profile
Microsoft Sentinel Blog

Microsoft Sentinel is a cloud-native SIEM, enriched with AI and automation to provide expansive visibility across your digital environment.

JPTam's avatar
JPTam
Copper Contributor
Aug 21, 2024

Hi,

I tried to deploy this solution via ARM template. After setting needed permissions for managed identity, runbook gave following warning
General : Configuration file version 2.0 is outdated. Features could not work correctly. Supported version is 2.4
I updated the GlobalConfiguration variable to v2.5 manually from Github and got rid of this warning.

After this the runbook started having following errors (with currently newest 7.6.0.1 version)
Connect-AzAccount : Method 'get_SerializationSettings' in type 'Microsoft.Azure.Management.Internal.Resources.ResourceManagementClient' from assembly 'Microsoft.Azure.PowerShell.Clients.ResourceManager, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' does not have an implementation. At line:497 char:34 + $AzureContext = (Connect-AzAccount -Identity).context + ~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : NotSpecified: (:) [Connect-AzAccount], TypeLoadException + FullyQualifiedErrorId : System.TypeLoadException,Microsoft.Azure.Commands.Profile.ConnectAzureRmAccountCommand

You cannot call a method on a null-valued expression. At line:517 char:9 + $ModuleGraphToken = [Microsoft.Azure.Commands.Common.Authenti ... +  + CategoryInfo : InvalidOperation: (:) [], RuntimeException + FullyQualifiedErrorId : InvokeMethodOnNull

Connect-MgGraph : Must specify 'AccessToken'. At line:520 char:9 + Connect-MgGraph -AccessToken $ModuleGraphToken.AccessToken + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : InvalidArgument: (:) [Connect-MgGraph], ArgumentException + FullyQualifiedErrorId : cd34f5fc-a467-4129-b0a7-5fb1678578c4,Microsoft.Graph.PowerShell.Authentication.Cmdlets.ConnectMgGraph


Get-MgUser : Authentication needed, call Connect-MgGraph. At line:1 char:82 + ... | ForEach {Get-MgUser -UserId $_.ExternalDirectoryObjectId -Property ... + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : NotSpecified: (:) [Get-MgUser_Get], AuthenticationException + FullyQualifiedErrorId : Microsoft.Graph.PowerShell.Cmdlets.GetMgUser_Get


Perhaps I'll try deploying the whole solution manually