Technology | Fitness | Food
Did you know that GitHub Copilot is now sensing hard coded credentials and giving you a warning? It’s not perfect, but even if something looks like hard coded creds it will flag it, as on another script I had, it contained numbers that looked like they could be private, and it gave me a warning about it. Honestly, I rather find more potentials credentials then not. That’s it for today, hope you have a great day!
If you have GitHub Copilot, you may or may not know about this little tip, but wanted to let you know just in case. It has saved me so much time and it can be applied to a lot of scenarios.
Here is the prompt, “Can you add the export to markdown capability from #file:Test-365ACCompanyName.ps1 to #file:Test-365ACStreetAddress.ps1”
And what this does is it adds the functionality of exporting to markdown to the new file the same I did in CompanyName, but adapts it to fit StreetAddress. Further more, it adds Help for it and creates the parameter for it(with ValidatePattern).
From this:
<#
.SYNOPSIS
Tests whether users have a street address and generates a report.
.DESCRIPTION
The Test-365ACStreetAddress function tests whether users have a street address and generates a report.
It takes a list of users as input and checks if each user has a street address.
The function generates a report that includes the user's display name and whether they have a street address.
The report can be exported to an Excel file or an HTML file.
.PARAMETER Users
Specifies the list of users to test. If not provided, it retrieves all users from the Microsoft Graph API.
.PARAMETER TenantID
The ID of the tenant to connect to. Required if using app-only authentication.
.PARAMETER ClientID
The ID of the client to use for app-only authentication. Required if using app-only authentication.
.PARAMETER CertificateThumbprint
The thumbprint of the certificate to use for app-only authentication. Required if using app-only authentication.
.PARAMETER AccessToken
The access token to use for authentication. Required if using app-only authentication.
.PARAMETER InteractiveLogin
Specifies whether to use interactive login. If this switch is present, interactive login will be used. Otherwise, app-only authentication will be used.
.PARAMETER OutputExcelFilePath
Specifies the file path to export the report as an Excel file. The file must have a .xlsx extension.
.PARAMETER OutputHtmlFilePath
Specifies the file path to export the report as an HTML file. The file must have a .html extension.
.PARAMETER TestedProperty
Specifies the name of the property being tested. Default value is 'Has Street Address'.
.EXAMPLE
Test-365ACStreetAddress -Users $users -OutputExcelFilePath "C:\\Reports\\StreetAddressReport.xlsx"
This example tests the specified list of users for street addresses and exports the report to an Excel file.
.EXAMPLE
Test-365ACStreetAddress -OutputExcelFilePath "C:\\Reports\\StreetAddressReport.xlsx"
This example retrieves all users from the Microsoft Graph API, tests them for street addresses, and exports the report to an Excel file.
#>
Function Test-365ACStreetAddress {
[CmdletBinding()]
param
(
[Parameter(ValueFromPipeline = $true)]
[array]$Users = (Get-MgUser -All -Property DisplayName, StreetAddress | Select-Object DisplayName, StreetAddress),
[Parameter(Mandatory = $false)]
[string]$TenantID,
[Parameter(Mandatory = $false)]
[string]$ClientID,
[Parameter(Mandatory = $false)]
[string]$CertificateThumbprint,
[Parameter(Mandatory = $false)]
[string]$AccessToken,
[Parameter(Mandatory = $false)]
[switch]$InteractiveLogin,
[ValidatePattern('\\.xlsx$')]
[string]$OutputExcelFilePath,
[ValidatePattern('\\.html$')]
[string]$OutputHtmlFilePath,
[string]$TestedProperty = 'Has Street Address'
)
BEGIN {
if ($InteractiveLogin) {
Write-PSFMessage "Using interactive login..." -Level Host
Connect-MgGraph -Scopes "User.Read.All", "AuditLog.read.All" -NoWelcome
}
else {
Write-PSFMessage "Using app-only authentication..." -Level Host
Connect-MgGraph -ClientId $ClientID -TenantId $TenantID -CertificateThumbprint $CertificateThumbprint -Scopes "User.Read.All", "AuditLog.Read.All"
}
$results = @()
}
PROCESS {
foreach ($user in $Users) {
$hasStreetAddress = [bool]($user.StreetAddress)
$result = [PSCustomObject]@{
'User Display Name' = $user.DisplayName
$TestedProperty = $hasStreetAddress
}
$results += $result
}
}
END {
$totalTests = $results.Count
$passedTests = ($results | Where-Object { $_.$TestedProperty }).Count
$failedTests = $totalTests - $passedTests
if ($OutputExcelFilePath) {
Export-365ACResultToExcel -Results $results -OutputExcelFilePath $OutputExcelFilePath -TotalTests $totalTests -PassedTests $passedTests -FailedTests $failedTests -TestedProperty $TestedProperty
}
elseif ($OutputHtmlFilePath) {
Export-365ACResultToHtml -Results $results -OutputHtmlFilePath $OutputHtmlFilePath -TotalTests $totalTests -PassedTests $passedTests -FailedTests $failedTests -TestedProperty $TestedProperty
}
else {
Write-Output $results
}
}
}
To this:
<#
.SYNOPSIS
Tests whether users have a street address and generates a report.
.DESCRIPTION
The Test-365ACStreetAddress function tests whether users have a street address and generates a report.
It takes a list of users as input and checks if each user has a street address.
The function generates a report that includes the user's display name and whether they have a street address.
The report can be exported to an Excel file, an HTML file, or a Markdown file.
.PARAMETER Users
Specifies the list of users to test. If not provided, it retrieves all users from the Microsoft Graph API.
.PARAMETER TenantID
The ID of the tenant to connect to. Required if using app-only authentication.
.PARAMETER ClientID
The ID of the client to use for app-only authentication. Required if using app-only authentication.
.PARAMETER CertificateThumbprint
The thumbprint of the certificate to use for app-only authentication. Required if using app-only authentication.
.PARAMETER AccessToken
The access token to use for authentication. Required if using app-only authentication.
.PARAMETER InteractiveLogin
Specifies whether to use interactive login. If this switch is present, interactive login will be used. Otherwise, app-only authentication will be used.
.PARAMETER OutputExcelFilePath
Specifies the file path to export the report as an Excel file. The file must have a .xlsx extension.
.PARAMETER OutputHtmlFilePath
Specifies the file path to export the report as an HTML file. The file must have a .html extension.
.PARAMETER OutputMarkdownFilePath
Specifies the file path to export the report as a Markdown file. The file must have a .md extension.
.PARAMETER TestedProperty
Specifies the name of the property being tested. Default value is 'Has Street Address'.
.EXAMPLE
Test-365ACStreetAddress -Users $users -OutputExcelFilePath "C:\\Reports\\StreetAddressReport.xlsx"
This example tests the specified list of users for street addresses and exports the report to an Excel file.
.EXAMPLE
Test-365ACStreetAddress -OutputExcelFilePath "C:\\Reports\\StreetAddressReport.xlsx"
This example retrieves all users from the Microsoft Graph API, tests them for street addresses, and exports the report to an Excel file.
#>
Function Test-365ACStreetAddress {
[CmdletBinding()]
param
(
[Parameter(ValueFromPipeline = $true)]
[array]$Users = (Get-MgUser -All -Property DisplayName, StreetAddress | Select-Object DisplayName, StreetAddress),
[Parameter(Mandatory = $false)]
[string]$TenantID,
[Parameter(Mandatory = $false)]
[string]$ClientID,
[Parameter(Mandatory = $false)]
[string]$CertificateThumbprint,
[Parameter(Mandatory = $false)]
[string]$AccessToken,
[Parameter(Mandatory = $false)]
[switch]$InteractiveLogin,
[ValidatePattern('\\.xlsx$')]
[string]$OutputExcelFilePath,
[ValidatePattern('\\.html$')]
[string]$OutputHtmlFilePath,
[ValidatePattern('\\.md$')]
[string]$OutputMarkdownFilePath,
[string]$TestedProperty = 'Has Street Address'
)
BEGIN {
if ($InteractiveLogin) {
Write-PSFMessage "Using interactive login..." -Level Host
Connect-MgGraph -Scopes "User.Read.All", "AuditLog.read.All" -NoWelcome
}
else {
Write-PSFMessage "Using app-only authentication..." -Level Host
Connect-MgGraph -ClientId $ClientID -TenantId $TenantID -CertificateThumbprint $CertificateThumbprint -Scopes "User.Read.All", "AuditLog.Read.All"
}
$results = @()
}
PROCESS {
foreach ($user in $Users) {
$hasStreetAddress = [bool]($user.StreetAddress)
$result = [PSCustomObject]@{
'User Display Name' = $user.DisplayName
$TestedProperty = $hasStreetAddress
}
$results += $result
}
}
END {
$totalTests = $results.Count
$passedTests = ($results | Where-Object { $_.$TestedProperty }).Count
$failedTests = $totalTests - $passedTests
if ($OutputExcelFilePath) {
Export-365ACResultToExcel -Results $results -OutputExcelFilePath $OutputExcelFilePath -TotalTests $totalTests -PassedTests $passedTests -FailedTests $failedTests -TestedProperty $TestedProperty
Write-PSFMessage "Excel report saved to $OutputExcelFilePath" -Level Host
}
elseif ($OutputHtmlFilePath) {
Export-365ACResultToHtml -Results $results -OutputHtmlFilePath $OutputHtmlFilePath -TotalTests $totalTests -PassedTests $passedTests -FailedTests $failedTests -TestedProperty $TestedProperty
Write-PSFMessage "HTML report saved to $OutputHtmlFilePath" -Level Host
}
elseif ($OutputMarkdownFilePath) {
Export-365ACResultToMarkdown -Results $results -OutputMarkdownFilePath $OutputMarkdownFilePath -TotalTests $totalTests -PassedTests $passedTests -FailedTests $failedTests -TestedProperty $TestedProperty
Write-PSFMessage "Markdown report saved to $OutputMarkdownFilePath" -Level Host
}
else {
Write-PSFMessage -Level Output -Message ($results | Out-String)
}
}
}
And here is the source Test-365ACCompanyName.ps1 code
<#
.SYNOPSIS
Tests if users have a company name property and generates test results.
.DESCRIPTION
The Test-365ACCompanyName function tests if users have a company name property and generates test results. It takes an array of users as input and checks if each user has a company name property. The test results are stored in an array of custom objects, which include the user's display name and the result of the test.
.PARAMETER Users
Specifies the array of users to test. Each user should have a DisplayName and CompanyName property.
.PARAMETER TenantID
The ID of the tenant to connect to. Required if using app-only authentication.
.PARAMETER ClientID
The ID of the client to use for app-only authentication. Required if using app-only authentication.
.PARAMETER CertificateThumbprint
The thumbprint of the certificate to use for app-only authentication. Required if using app-only authentication.
.PARAMETER AccessToken
The access token to use for authentication. Required if using app-only authentication.
.PARAMETER InteractiveLogin
Specifies whether to use interactive login. If this switch is present, interactive login will be used. Otherwise, app-only authentication will be used.
.PARAMETER OutputExcelFilePath
Specifies the path to the output Excel file. If provided, the test results will be exported to an Excel file.
.PARAMETER OutputHtmlFilePath
Specifies the path to the output HTML file. If provided, the test results will be exported to an HTML file.
.PARAMETER OutputMarkdownFilePath
Specifies the path to the output Markdown file. If provided, the test results will be exported to a Markdown file.
.PARAMETER TestedProperty
Specifies the name of the tested property. Default value is 'Has Company Name'.
.INPUTS
An array of users with DisplayName and CompanyName properties.
.OUTPUTS
If OutputExcelFilePath or OutputHtmlFilePath is not provided, the function outputs an array of custom objects with the user's display name and the result of the test.
.EXAMPLE
$users = Get-MgUser -All -Property DisplayName, CompanyName | Select-Object DisplayName, CompanyName
Test-365ACCompanyName -Users $users -OutputExcelFilePath 'C:\\TestResults.xlsx'
This example tests if the users have a company name property and exports the test results to an Excel file.
#>
Function Test-365ACCompanyName {
[CmdletBinding()]
param
(
[Parameter(ValueFromPipeline = $true)]
[array]$Users = (Get-MgUser -All -Property DisplayName, CompanyName | Select-Object DisplayName, CompanyName),
[Parameter(Mandatory = $false)]
[string]$TenantID,
[Parameter(Mandatory = $false)]
[string]$ClientID,
[Parameter(Mandatory = $false)]
[string]$CertificateThumbprint,
[Parameter(Mandatory = $false)]
[string]$AccessToken,
[Parameter(Mandatory = $false)]
[switch]$InteractiveLogin,
[ValidatePattern('\\.xlsx$')]
[string]$OutputExcelFilePath,
[ValidatePattern('\\.html$')]
[string]$OutputHtmlFilePath,
[ValidatePattern('\\.md$')]
[string]$OutputMarkdownFilePath,
[string]$TestedProperty = 'Has Company Name'
)
BEGIN {
if ($InteractiveLogin) {
Write-PSFMessage "Using interactive login..." -Level Host
Connect-MgGraph -Scopes "User.Read.All", "AuditLog.read.All" -NoWelcome
}
else {
Write-PSFMessage "Using app-only authentication..." -Level Host
Connect-MgGraph -ClientId $ClientID -TenantId $TenantID -CertificateThumbprint $CertificateThumbprint -Scopes "User.Read.All", "AuditLog.Read.All"
}
$results = @()
}
PROCESS {
foreach ($user in $Users) {
$hasCompanyName = [bool]($user.CompanyName)
$result = [PSCustomObject]@{
'User Display Name' = $user.DisplayName
$TestedProperty = $hasCompanyName
}
$results += $result
}
}
END {
$totalTests = $results.Count
$passedTests = ($results | Where-Object { $_.$TestedProperty }).Count
$failedTests = $totalTests - $passedTests
if ($OutputExcelFilePath) {
Export-365ACResultToExcel -Results $results -OutputExcelFilePath $OutputExcelFilePath -TotalTests $totalTests -PassedTests $passedTests -FailedTests $failedTests -TestedProperty $TestedProperty
Write-PSFMessage "Excel report saved to $OutputExcelFilePath" -Level Host
}
elseif ($OutputHtmlFilePath) {
Export-365ACResultToHtml -Results $results -OutputHtmlFilePath $OutputHtmlFilePath -TotalTests $totalTests -PassedTests $passedTests -FailedTests $failedTests -TestedProperty $TestedProperty
Write-PSFMessage "HTML report saved to $OutputHtmlFilePath" -Level Host
}
elseif ($OutputMarkdownFilePath) {
Export-365ACResultToMarkdown -Results $results -OutputMarkdownFilePath $OutputMarkdownFilePath -TotalTests $totalTests -PassedTests $passedTests -FailedTests $failedTests -TestedProperty $TestedProperty
Write-PSFMessage "Markdown report saved to $OutputMarkdownFilePath" -Level Host
}
else {
Write-PSFMessage -Level Output -Message ($results | Out-String)
}
}
}
And yes, it did write out the whole function again, I didn’t manipulate it at all, so after reviewing you can literally just copy it in, and not have to worry about forgetting a “(” or “{”. I know it’s not a huge lift, but you can also do “Can you also do this for #file:Test-365ACZipcode.ps1” and it will.
I’ve used this prompt syntax for other functions as well with great results. Have you used anything like this before?
You can see more uses of it at GitHub – 365AutomatedCheck
Here is a quick use of OpenAI / ChatGPT to remove Windows processes. If it doesn’t get it right the first time, it usually is a good enough base to only need an edit or 2 for simpler scripts. Not bad for going 2/2 on no edits needed!
PROMPT 1:
Me:
You are a powershell expert, can you write me a script to find all processes running then show me them in a window and I can select which ones I want to delete?
ChatGPT:
Certainly! Here’s a PowerShell script that will retrieve all running processes, display them in a GUI window using Out-GridView, and then terminate the selected processes:
# Get all running processes
$processes = Get-Process | Select-Object Id, Name, CPU, Path
# Display processes in a GridView for selection
$selectedProcesses = $processes | Out-GridView -Title "Select processes to terminate" -PassThru
# Terminate selected processes
$selectedProcesses | ForEach-Object {
try {
Stop-Process -Id $_.Id -Force
Write-Host "Terminated process: $($_.Name) with ID: $($_.Id)"
} catch {
Write-Warning "Failed to terminate process: $($_.Name) with ID: $($_.Id)"
}
}Steps:
Out-GridView. You can select multiple processes by holding down the Ctrl key and clicking on them.Note: Ensure you have the required permissions to terminate processes. Also, be cautious about which processes you terminate, as some are essential for the proper functioning of your system.
Review 1:
You can see that it created the first prompt perfectly, and no edits were necessary.
Selected the processes and gave me a GUI to delete the ones I don’t need anymore
PROMPT 2:
ME:
Can you make it so I can select which one I want see beween ram and cpu?
ChatGPT:
Of course! We can add an initial prompt to let you select between viewing processes based on RAM or CPU usage.
Here’s the updated script:
# Get all running processes
$processes = Get-Process | Select-Object Id, Name, CPU, WS
# Prompt the user to choose between CPU and RAM
$choice = $host.ui.PromptForChoice("Selection", "Choose the metric to display top 5 processes:", @("CPU", "RAM"), 0)
# Display the top 5 processes based on the selected metric
if ($choice -eq 0) {
$topProcesses = $processes | Sort-Object CPU -Descending | Select-Object -First 5
} else {
$topProcesses = $processes | Sort-Object WS -Descending | Select-Object -First 5
}
# Display processes in a GridView for selection
$selectedProcesses = $topProcesses | Out-GridView -Title "Select processes to terminate" -PassThru
# Terminate selected processes
$selectedProcesses | ForEach-Object {
try {
Stop-Process -Id $_.Id -Force
Write-Host "Terminated process: $($_.Name) with ID: $($_.Id)"
} catch {
Write-Warning "Failed to terminate process: $($_.Name) with ID: $($_.Id)"
}
}
Now, when you run the script, it will first prompt you to choose between CPU and RAM. After you make your selection, it will display the top 5 processes based on that metric. You can then select which processes you want to terminate.
Review 2:
As you can see this worked exactly how I wanted it to and gave me the option to pick the top 5 highest of ram or cpu usage, then allowed me to delete.
Let me set the stage… previously we had a batch file in our startup script to add/remove network drives. It worked great and didn’t have any issues. We moved away from an on-site file server to a cloud solution with local cache. They created a new batch file for us which worked perfectly… until we started looking at integrating Intune computers. Luckily, early on we caught this, and realized we needed a PowerShell script instead of a batch script. We reached out to the vendor with knowing they had PowerShell experience and asked if they could recreate the script using PowerShell. They came back with a quote of $1,500.
I looked at the batch script again, and said there is no way it costs that much to convert an already working batch script to PowerShell. So what did I do? I opened up the 26 line batch script, skimmed over it, then copied it into ChatGPT, and told it to convert the script to PowerShell. It created a PowerShell function within the script and when I followed up with an additional prompt to see if a certain drive was still present to delete it, it created that as well. It was 98% done, I only had to fill in our company data and one part they had an additional parameter that wasn’t needed. All less than 15 minutes. For context, this was with ChatGPT with GPT-4 back in early May 2023, as it is even better now.
Is ChatGPT always this accurate? No, but when you search on Google, Stack Overflow, or any other site, is it always accurate? I like to think of ChatGPT, Azure OpenAI, etc as a smart intern where you trust, but verify the work before implementing. Always test in a development environment as some code take down infrastructure(Same with other sites/LLMs)
Now, not only did I save the company $1,500, I saved time from all the meetings, paperwork(Purchase Order and misc), and testing with the vendor which I used to work on other projects!
Hope you found this helpful and gets you thinking of using ChatGPT, Azure OpenAI, etc more, but please make sure you know what you are testing and/or are in a complete test environment. And if for some reason you take down something in production by accident, let someone know asap what you were doing, so that it can be quickly resolved if you aren’t sure how to fix it.
I’m just going to cut to the chase on this one..
copilot "How to filter ID column not being empty and if it isn't empty it starts with a number and the other column named sideindicator having a r in it using powershell and importexcel and both criteria must be true?"╔═════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════╗
║Q: How to filter ID column not being empty and if it isn't empty it starts with a number and the other column named sideindicator having a r in it using powershell and importexcel and both criteria must be true? ║
║═════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════║
║1: $data = Import-Excel -Path "C:\Path\To\File.xlsx" ║
║2: $data | Where-Object {$_.ID -and $_.ID -match '^\d' -and $_.SideIndicator -eq 'r'} ║
╚═════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════╝How about that? Nice little RegEx in there too! Yes this does work, as I used it this morning for a real life solution.
Download Doug Finke’s PowerShellAI module, get your OpenAI API key, and start having some fun! And if for some reason you still haven’t downloaded his ImportExcel module get that too! And want to hear a little more about Doug, check him out on the PowerShell Podcast and find out how ImportExcel is created.
That’s enough for today, I don’t want to take away your time from playing with this!
PowerShell Gallery:
PowerShellAI
GitHub:
PowerShellAI