-
Notifications
You must be signed in to change notification settings - Fork 583
/
AuditRecordAuditLabel.PS1
74 lines (64 loc) · 4.08 KB
/
AuditRecordAuditLabel.PS1
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
# AuditRecordAuditLabel.PS1
# https://github.com/12Knocksinna/Office365itpros/blob/master/AuditRecordAuditLabel.PS1
# A script to look for audit records for the application of retention labels and report those which
# are applied by an auto-label policy.
[array]$Modules = Get-Module | Select-Object -ExpandProperty Name
If ("ExchangeOnlineManagement" -notin $Modules) {
Write-Host "Please connect to the Exchange Online Management module and then restart the script"
break
}
# Retention label to check for - change this to your preferred label name
$RetentionLabel = "Teams recordings"
$TotalSeconds = 0
# Start and end date for the audit scan. By default, we look for 14 days, but you can choose any value you like up to 365 (assuming Office 365 E5)
$StartDate = (Get-Date).AddDays(-14); $EndDate = (Get-Date).AddDays(1)
$OutputCSVFile = "C:\temp\TaggedTeamsRecordings.csv"
# Find the audit records
[array]$Records = Search-UnifiedAuditLog -Operations TagApplied -StartDate $StartDate -EndDate $EndDate -Formatted -ResultSize 5000 -SessionCommand ReturnLargeSet
If (!$Records) {
Write-Host "No audit records found - exiting!"; break
}
# Sort to remove duplicate audit records
$Records = $Records | Sort-Object Identity -Unique
# Check the audit records for those for auto-label policies which applied the retention label we're interested in
$TaggedRecordings = [System.Collections.Generic.List[Object]]::new()
ForEach ($Rec in $Records) {
$AuditData = $Rec.AuditData | ConvertFrom-Json
If (($AuditData.DestinationLabel -eq $RetentionLabel) -and ($AuditData.UserType -eq "CustomPolicy")) {
$RecordingFileName = $AuditData.DestinationFileName
$DateLoc = ($RecordingFileName.IndexOf("-202")+1)
$RDate = $RecordingFileName.SubString($DateLoc,8)
$TimeLoc = $DateLoc + 9
$RTime = $RecordingFileName.SubString($TimeLoc,4)
$RecordingDateTime = $RDate + $RTime
[datetime]$RecordingDate = [datetime]::ParseExact($RecordingDateTime,"yyyyMMddHHmm",$null)
[datetime]$TaggingDate = Get-Date($AuditData.CreationTime)
$TimeToTag = ($TaggingDate - $RecordingDate)
$TotalSeconds = $TotalSeconds + $TimeToTag.TotalSeconds
$TimeToTagFormatted = "{0:dd}d:{0:hh}h:{0:mm}m" -f $TimeToTag
# Add the data about our record
$DataLine = [PSCustomObject] @{
Workload = $AuditData.Workload
Recording = $AuditData.DestinationFileName
"Retention Label" = $AuditData.DestinationLabel
"Tagging Date" = Get-Date($AuditData.CreationTime) -format 'dd-MMM-yyyy HH:mm:ss'
"Recording date" = Get-Date($RecordingDate) -format 'dd-MMM-yyy HH:mm:ss'
"Days to label" = $TimeToTagFormatted
Site = $AuditData.SiteURL
FullURL = $AuditData.ObjectId }
$TaggedRecordings.Add($DataLine)
} # End if
} # End ForEach
Clear-Host
# All done
$TaggedRecordings | Export-CSV -NoTypeInformation $OutputCSVFile
Write-Host ("{0} audit records found for auto-applying the {1} retention label between {2} and {3}" -f $TaggedRecordings.Count, $RetentionLabel, $StartDate, $EndDate)
$AverageSeconds = $TotalSeconds/$TaggedRecordings.Count
$AverageTimeToTag = [timespan]::fromseconds($AverageSeconds)
$AverageTimeToTagFormatted = "{0:dd}d:{0:hh}h:{0:mm}m" -f $AverageTimeToTag
Write-Host ("Average elapsed time to auto-label recordings: {0}" -f $AverageTimeToTagFormatted)
Write-Host ("The report file is available in {0}." -f $OutputCSVFile)
# An example script used to illustrate a concept. More information about the topic can be found in the Office 365 for IT Pros eBook https://gum.co/O365IT/
# and/or a relevant article on https://office365itpros.com or https://www.practical365.com. See our post about the Office 365 for IT Pros repository # https://office365itpros.com/office-365-github-repository/ for information about the scripts we write.
# Do not use our scripts in production until you are satisfied that the code meets the need of your organization. Never run any code downloaded from the Internet without
# first validating the code in a non-production environment.