Skip to content

Releases: MSEndpointMgr/IntuneEnhancedInventory

IntuneEnhancedInventory 1.2

Choose a tag to compare

@JankeSkanke JankeSkanke released this 14 Oct 13:18

IMPORTANT!
Version 1.2 requires use of version 3.5.0 of the Invoke-CustomInventoryAzureFunction.ps1 to be used in Proactive Remediations
This version of the Azure Function will work for any custom log you want to send securely to Log Analytics
This version will return a new payload back to the PR script that dynamically handles the status per log-type ingested

Full changelog can be found here: Changelog

Example code for adding a custom log

$LogPayLoad = New-Object -TypeName PSObject 
$LogPayLoad | Add-Member -NotePropertyMembers @{$LogName1 = $Logdata1}
$LogPayLoad | Add-Member -NotePropertyMembers @{$LogName2 = $Logdata2}
# Construct main payload to send to LogCollectorAPI
$MainPayLoad = [PSCustomObject]@{
	AzureADTenantID = $AzureADTenantID
	AzureADDeviceID = $AzureADDeviceID
	LogPayloads = $LogPayLoad
}

IntuneEnhancedInventory 1.1

Choose a tag to compare

@JankeSkanke JankeSkanke released this 28 Jan 12:29

IMPORTANT!
Version 1.1 requires use of version 3.0.0 of the Invoke-CustomInventoryAzureFunction.ps1 to be used in Proactive Remediations
This version of the Azure Function will work for any custom log you want to send securely to Log Analytics

Example code for adding a custom log

$LogPayLoad = New-Object -TypeName PSObject 
$LogPayLoad | Add-Member -NotePropertyMembers @{$LogName1 = $Logdata1}
$LogPayLoad | Add-Member -NotePropertyMembers @{$LogName2 = $Logdata2}
# Construct main payload to send to LogCollectorAPI
$MainPayLoad = [PSCustomObject]@{
	AzureADTenantID = $AzureADTenantID
	AzureADDeviceID = $AzureADDeviceID
	LogPayloads = $LogPayLoad
}

**Full Changelog**: https://github.com/MSEndpointMgr/IntuneEnhancedInventory/compare/v1.0...v1.1

IntuneEnhancedInventory

Choose a tag to compare

@JankeSkanke JankeSkanke released this 16 Jan 18:56

This solutions allows you secure our current custom inventory solution by removing secrets from the code running locally on clients. It also uses parts of CloudLaps solution for client verification to make sure only existing and active clients in your environment is allowed to submit data to your log workspace in Azure.