The old adage of “I put my pants on one leg at a time”... but add on, “and then I lay on my bed and struggle so hard my Apple Watch asks me if I want to start a workout”

PowerShell Wednesday is here, and we are learning about... PowerShell Parameter Binding Join us for a deep dive with @swsamwa, Lead Documentarian for PowerShell at Microsoft. Live @ 2PM EST (every Wednesday) 📺

Did you know you can type ¯\_(ツ)_/¯ and more on Windows by press WIN + Period (.)? 👀

I always thought it was just my org You get on here and listen to the "experts" whose environments are apparently hardened against nation state actors (they aren')), and you feel behind, like a failure It's all a lie, you aren't a failure, and you're doing better than you think

Happy Halloween! Sadly not actually dressed up today, but a fun callback to my favorite costume which just so happens to be my Slack and Zoom pic at work 😊

These are the same functions that I use to pull policies, assignments, and statuses from the Graph. Sometimes you just don't have the time for Invoke-RestMethod, but don't want all of the #MSGraph modules... enter the Honda Civic version. Reliable, consistent, and effective.

The first time I heard about the "XY Problem", it blew my mind. I'd seen it for years. When someone asks for help with a weird workaround, and only later do you realize they were trying to solve something completely different that has a much easier solution. @AllwaysHyPe 1/3

Managing #Intune doesn’t have to feel complicated, I promise. 😊 In Part 2 of my Microsoft Graph series, I show how to use #MSGraph and #PowerShell to simplify your workflows without adding extra layers or tools. https://t.co/mBIriPTfEo

🚨If your #PowerShell CI/CD pipelines are failing, it's probably not because they're broken. Many GitHub workflows use Install-Module and the PowerShell Gallery is currently impacted by the Azure Front Door outage. 🎛️PowerShell gallery Status Page:

Remember when people thought #PowerShell would take away jobs? @AllwaysHyPe draws a great parallel between that moment and the current wave of AI anxiety. Her reminder: “You’re not getting paid to write code. You’re getting paid to solve business problems.” 1/2

Had a great time chatting with @AndrewPlaTech on the @PowerShellpod about #Intune, #PowerShell, IntuneStack, #DevOps and getting started on your #automation journey. https://t.co/gWoeiJF6S5

Microsoft docs Update 💡 SSL Inspection isn't supported on endpoints required for Microsoft Store API. https://t.co/2zO33hk2oZ #MSIntune #MSDocsUpdate

One of the things I’ve been the most excited about this year. #PowerShellDSC #PowerShell #DSC

Still in testing, but it’s a pattern anyone can use to manage Intune like any other Infrastructure as Code system. https://t.co/APoUi7QpTB

That idea became IntuneStack, a CI/CD workflow for Intune policy. It runs in GitHub Actions, uses OIDC for authentication, enforces code quality with Pester and PSScriptAnalyzer, and promotes policies automatically based on success criteria.

What if #Intune policy could promote itself based on success criteria I set in advance? 🧵 No more ClickOps. Just deploy, evaluate, and promote. Dev, Test, and Prod not as separate environments, but as 'containers'. Prod wouldn't be special, just the last deployment stop.

If you're still using client secrets in your GitHub Actions workflows, spend 10 minutes setting up federated credentials instead. No more secret rotation, no more worrying about leaks. Just works. https://t.co/I7vnKu95hY

I built a #PowerShell function that handles the token exchange and works for both GitHub Actions (OIDC) and local development (interactive auth). Same code, different auth paths depending on where it runs. https://t.co/S7kRKYfy9x

In your GitHub workflow, set permissions to request the token, then grab it using the GitHub OIDC endpoint. I added a debug step to verify the token is being passed correctly, helps to catch auth issues early before they hit your actual script.

Setup in Entra: - App Registration → Certificates & secrets → Federated credentials - Add credential, choose GitHub Actions - Specify your org/repo/branch - Save In your workflow, request the OIDC token and exchange it for a #MSGraph access token. No client secrets!

What sold me: I can configure the federated cred to only trust a specific branch in my repo. Fork my repo? Can't auth. Create a rogue branch? Can't auth. Only my designated branch can get tokens. That's a 2nd layer of protection from my Monday morning brain sans coffee.