@rafal_fitt @namitguy

#OpenIntuneBaseline Windows v4.0 is here! 🎉 Highlights include: * Continuing to be the most agile and cutting-edge Intune baseline on the planet! * A shake-up of Compliance policies, allowing true grace period granularity (and ditching the EAS Password policy because it's 🗑️) * Edge settings for days! Simple support for the Edge Management Service and security hardening and user experience improvements. * Updated M365 Apps Security baseline alignment. * Fixed MS breaking the in-box app removal policy. * Defender behaviour tweaks based on real customer feedback, not arbitrary check-boxes. * Deprecated and obsolete settings sent to live on a farm. As always: ✅ Take what you want ✅ Change what doesn't suit your environment ✅ Test it before yeeting to 40,000 endpoints on Friday afternoon ❌ Don't treat any security baseline as a magical compliance button Check out the full release notes at: stte.me/oib26h2 Then, head on over to the OIB Deployer to deploy the new and updated policies, or check your current config vs 4.0 with the Settings Validator! https://deploy[.]openintunebaseline.com And, uhh, keep an eye on Friday, too ;) #OIB #Windows #EndpointSecurity #Community #Capybara

The Edge Management Service has so many hidden gems. However, if you're using the #OpenIntuneBaseline, you're already benefitting from a *required* user prompt and significantly reduced forced restart period from the Edge defaults 😉

Really @Blizzard_Ent? I created my BattleNet account to play Vanilla WoW in 2004. My account can legally drink in the US, and you KNOW this. You also know that I already have a Credit Card attached to my account. I won't get started on how stupid the whole @GOVUK age verification is, but companies who are consistently failing to apply a single braincell trying to comply need to be called out.

@m0bilej0n @AdamGell

Massive Security win! You can now manage policies for #VSCode in #Intune! As of the #Windows June Preview Update (26200.8524), MS have unblocked the VSCode ADMX registry path, meaning that uploading the ADMX shipped with a VSCode install allows you to create a policy to deploy allowed extensions (either by publisher or individually), as well as things like control chat capabilities and MCP servers - All of which have been proven as a serious supply chain attack or data exfiltration risks! VSCode policy docs: code.visualstudio.com/docs/e…

So that's basically the entire point of the OIBID I've added. If the GUID in the description matches, it doesn't matter what the policy name is (which was my first crude implementation). The only thing I'm not doing (cos it's much harder to do) is per-policy settings checks.

🚨#OIB #Windows v3.8 & #OIBDeployer updates! I've just released v3.8 of the Windows OIB, which adds some cool things, as well as squashing a bunch of #community submitted bugs! Most importantly, I'm adding policy tracking through unique "OIBID"s, meaning much more flexible options when it comes to policy management through my OIB Deployer tool! Speaking of which, I've updated that too! A small face-lift (including dark mode!), API call improvements, and the functionality to support the new OIBID checks. Full Windows v3.8 Changelog here: stte.me/oibwin3dot8 Deploy or Update it in your tenant here: stte.me/deployoib To everyone that continues to provide support, feedback, and trust in this little project that's gotten way bigger than I ever thought it would - Thank you. 💛

Have you run a debloat tool or something, cos "display" should absolutely bring up exactly what you want immediately

So you're saying it's not normal that I know every single setting I've put in my OpenIntuneBaseline? Huh...