Forward Technologies

The Microsoft 365 companion apps (Calendar, People, and Files) were supposed to streamline everyday workflows.

Instead, they’re being retired only a year after launch.

Microsoft and admins are now removing them from devices.

Evaluating a potential new client, this server hasn’t been rebooted in two years. I asked the client if they had a backup. Their answer made me think it’s probably better to pass on this particular opportunity…

The official release of macOS 27 Golden Gate officially brings the Intel era of macOS to an end.

RIP macOS Intel support: 2006–2026 🪦💐

Your Conditional Access policies aren’t necessarily protected by Conditional Access. Unless you turn this on.

Microsoft Entra has a feature called Protected Actions that’s worth knowing about.

By default, an admin who already has the required permissions can modify or delete your Conditional Access policies using the authentication from their existing session. With Entra’s default sign-in frequency of up to 90 days, that authentication could be weeks old.

Protected Actions changes that.

It lets you apply a Conditional Access policy directly to specific high-risk permissions, including the permissions used to create, modify, or delete Conditional Access policies themselves.

That means the admin can be challenged for fresh authentication at the moment they perform the protected action, regardless of which role granted them the permission.

In other words, you’re using Conditional Access to protect the ability to change Conditional Access.

‼️ BREAKING: Microsoft’s September 2026 Patch Tuesday fixes a record-breaking 966 flaws.

⚠️ 2 actively exploited zero-days
🔴 105 total Critical flaws, including:
💥 81 remote code ex*****on
⬆️ 20 privilege escalation

Windows 11 is finally getting a battery status widget that will show an overview of all your connected devices on the lock screen or Widgets Board.

‼️ Microsoft says an outage that began in Exchange Online is now also hitting Teams, SharePoint and Defender XDR

The company says it still has not identified what is causing the failures

Microsoft first logged the incident as EX1464935 at 17:30 UTC and now tracks it as MO1465074:

We've identified an issue with an authentication component which is contributing to impact. To address this, we've developed a remediation strategy and we're applying it to a portion of infrastructure to test its efficacy. Once we've confirmed this resolves impact, we'll apply the solution more broadly. For more information, please see EX1464935 in the admin center.

Microsoft is not having a good day

Obviously, ‘vibe coded’

Cyber security in South America…