dfo

@IAMERICAbooted Feeling this too.

Try doing this in orgs with over 50k SharePoint sites. Welcome to my world :P learn.microsoft.com/en-us/copilot/…

@techspence My pain from exchange to m365 was chasing Outlook password prompts. Uuuuugh

Migrating Microsoft Exchange to M365

@ZackKorman @UK_Daniel_Card Just generating ideas

Good news: I’m starting a new company, which means that at some point in the future everyone is getting another hoodie.

@paulsanders87 I can’t sit down because there’s no room on the couch between wife, kids, toys and clothes 🤣

Story of my life …

@ZackKorman It’s all theater!

ISO27001 and SOC2 aren’t perfect, but you’re fooling yourself if you think your CISO’s vendor assessment process is better.

@romualpiecyk @mderooij Servers/systems connecting must trust it. Things like third party email gateways, servers where the trust list is not automatically updating.

@mderooij Doesn’t it trust it already by default?

PSA: In 1 month, Exchange Online requires trusting DigiCert Root G2 CA chain to avoid disruption xf.ms/DigiCertRootG2

@ZackKorman I appreciate your skills in Skills tho

I’m going to make a video explaining why skills scanners are dumb then never talk about skills again because I hate this topic so much and it’s beyond stupid that it’s getting this much attention.

@IAMERICAbooted To me this is probably the hardest part

One thing you can do for your orgs regarding AI security: start thinking about how you can block AI from reading certain data even when you have AI service principals in your environment. Luckily for me, I started researching and testing this a year ago.

@HackingDave Have you tried HellDivers 2?

This is why arc raiders is honestly one of the craziest games ever built. The variance in lobbies, what you can do - just an incredible game lol. Amazing 🤣🤣

@IAMERICAbooted @NathanMcNulty Gemini has been doing good enough. Guess it’s time to try Claude tho 😬

@dfowler_ @NathanMcNulty Copilot sucks. It takes hours or days compared to what I can do with other AI solutions

It really is. I have my bots write me fully functional scripts now with very little revision just using generic prompts.

@NathanMcNulty @IAMERICAbooted Which are you guys using? M365 Copilot has been a crapshoot for Powershell so far but it’s all I have for work 😄

@IAMERICAbooted And the logging, output, and error handling are 100x better than anything I've ever written, because I never do those things 🤣

@H3KTlC Add an annoying ass background to the emails too for extra spice!

immediately doing this

comic sans for a work email is wiillllldddd

@IAMERICAbooted @plankers See Sharp

@plankers R Go Nim Rust ASSembly Erlang awk lua

B. FORTRAN. HASKELL. JAVA.

@systemofdoom IS1202804 in Service Health for me

Sam posted this two days ago, and was still a problem this morning. Some of our admins can't PIM up at all.

@SamErde Yeah it’s frustrating

@dfowler_ I hate that these status advisories are hidden behind a login. I need to activate a role to even view them?! 😂

Anyone else getting persistent errors while trying to activate some roles in #EntraID PIM?

@SamErde They finally sent a service health incident about 45 minutes ago. IS1202804

@dfowler_ Oh shoot. Is there any mention in the status page?

@ITguySoCal Loop the results through Get-EXOMobileDeviceStatistics to see if the device is actually syncing recently.

Run this before 3/1/26 to identify which users won't be able to connect to Exchange Online after Microsoft Blocks ActiveSync versions less than version 16.1 Get-MobileDevice | Where-Object {($_.ClientType -eq 'EAS' -or $_.ClientType -match 'ActiveSync') -and $_.ClientVersion -and ([version]$_.ClientVersion -lt [version]'16.1')} | Sort-Object UserDisplayName | Select-Object UserDisplayName, UserPrincipalName, DeviceId, DeviceModel

@alitajran The script can return a lot of old devices. Loop through and run Get-EXOMobileDeviceStatistics to get the LastSuccessSync to see if the devices are even connecting anymore.

Starting March 1, 2026, devices using Exchange ActiveSync (EAS) versions lower than 16.1 will no longer be able to connect to Exchange Online! Microsoft is making a change to improve security and reliability in Exchange Online for ActiveSync devices! EAS 16.1 was introduced in June 2016 and provides enhanced compatibility and security. 𝐖𝐡𝐞𝐧 𝐭𝐡𝐢𝐬 𝐰𝐢𝐥𝐥 𝐡𝐚𝐩𝐩𝐞𝐧: This change begins taking effect on March 1, 2026. 𝐇𝐨𝐰 𝐭𝐡𝐢𝐬 𝐚𝐟𝐟𝐞𝐜𝐭𝐬 𝐲𝐨𝐮𝐫 𝐨𝐫𝐠𝐚𝐧𝐢𝐳𝐚𝐭𝐢𝐨𝐧: Organizations using mobile devices with native email apps to access Exchange Online mailboxes via EAS protocol. Apple devices added support for EAS 16.1 in iOS 10 and are unlikely to be affected. The Gmail app and Samsung Mail will have updated versions available before the deadline. For other apps, you should contact your device or application vendor if they are using EAS versions lower than 16.1. 𝐖𝐡𝐚𝐭 𝐰𝐢𝐥𝐥 𝐡𝐚𝐩𝐩𝐞𝐧: - Devices running EAS versions lower than 16.1 will no longer connect to Exchange Online. - Devices using Outlook Mobile are not impacted because they do not use EAS. - This change applies only to Exchange Online, not Exchange Server. 𝐖𝐡𝐚𝐭 𝐲𝐨𝐮 𝐜𝐚𝐧 𝐝𝐨 𝐭𝐨 𝐩𝐫𝐞𝐩𝐚𝐫𝐞: - Verify that all mobile devices and applications are updated to EAS version 16.1 or higher before March 1, 2026. - Admins can generate a report of devices using older EAS versions with the following PowerShell command: Get-MobileDevice | Where-Object {($_.ClientType -eq 'EAS' -or $_.ClientType -match 'ActiveSync') -and $_.ClientVersion -and (version$_.ClientVersion -lt version'16.1')} | Sort-Object UserDisplayName | Select-Object UserDisplayName, UserPrincipalName, DeviceId, DeviceModel - Communicate this change to your helpdesk and end users, and ask them to update if possible. - Update internal documentation as needed. - For assistance, contact your device or application vendor. #Microsoft365 #ExchangeOnline #ActiveSync

@H3KTlC Haha check out what some orgs used to name their email servers in public dns. Cartoon character names, planets, etc

what kind of mental illness is naming your dashboards like they’re pets