August 19, 2026

Google Workspace Has a Deadline, Plus 2 Tech Stories

Mike York Daily Briefs Artificial Intelligence (AI), Broadcast Regulation, Disney, fcc, fda, Google, Google Workspace, Medical Devices

Wednesday’s news has three very different versions of the same basic problem: the rules underneath a technology system matter a lot more than most people notice until somebody changes them.

For Google Workspace administrators, that means old security-log rules are about to stop behaving the way they used to. For Disney and ABC, it means arguing in federal court over where the FCC’s legitimate power to regulate broadcast licenses ends and unconstitutional pressure on speech might begin. And at the FDA, regulators are trying to figure out what “safe and effective” even means when a medical device can generate different answers instead of behaving like a traditional machine.

Google Workspace admins have an August 31 cleanup job

If you administer Google Workspace and use audit logs, the security investigation tool, custom alerts or reporting rules, there is a deadline hiding at the end of August that is worth dealing with before it becomes a September surprise.

Google has been replacing a number of legacy Admin log events with newer event names, types, reporting frequencies and conditions. The old and new versions have existed side by side during the transition. After August, the legacy versions go away.

This does not mean Gmail, Drive or Docs suddenly stop working. It matters to the people responsible for watching what happens inside a Workspace organization. Saved investigations built on the old events will stop working, existing queries and reports may need changes, and some automatically migrated alert rules can end up meaning something broader than the administrator intended.

Google’s own example is the part that got my attention. A rule designed to alert on one particular Gmail setting change can, after migration, start alerting on every Gmail setting change if multiple legacy conditions were involved. Congratulations: the security tool technically still works, but now it screams often enough that everybody learns to ignore it. That is not really an improvement.

If your organization actually uses Workspace security investigations or custom rules, review Google’s migration table before August 31. Check saved investigations, queries, reports and alerts tied to Admin log events, then test the migrated rules to make sure they still mean what you think they mean. If you have never configured any of this, there is probably nothing to do. MSPs, IT administrators and businesses that have invested in Workspace monitoring should not assume the migration handled every detail correctly.

Reliable automation

Automation is wonderful until it quietly stops working three Tuesdays ago. Raymond Tec builds integrations with logging, monitoring, and failure handling in mind so the boring work stays automated without becoming mysterious.

Disney and ABC are asking a court to stop an early FCC review

Disney and ABC have sued to stop the Federal Communications Commission from moving forward with an unusually early review of licenses held by eight ABC-owned television stations.

The word stations matters here. The FCC does not give ABC one national permission slip to be a television network. Local stations use public airwaves under individual licenses, and that gives the government legitimate regulatory authority over technical operation and compliance with communications law. What it does not give the government is a First Amendment exemption.

Disney says the accelerated review is retaliation for ABC programming and editorial decisions disliked by President Donald Trump and his administration. The FCC disputes that. It says the review grew out of an investigation into whether Disney’s diversity policies amounted to unlawful discrimination, which Disney denies. FCC Chairman Brendan Carr has also emphasized that no final licensing decision has been made.

That makes the important question narrower than whichever political team somebody happens to be cheering for. Regulators need enough authority to enforce the laws they are responsible for enforcing. But if broadcast-license scrutiny can be accelerated because government officials dislike a network’s speech, the license itself starts looking a lot like leverage over editorial decisions.

Right now, retaliation is Disney’s allegation, not a court finding. The FCC has offered another explanation, and the case is just beginning. U.S. District Judge Loren AliKhan has asked the parties to propose a schedule and ordered the FCC to notify the court if it moves toward a process that could revoke the licenses. This one is worth watching because the eventual boundary the court draws matters well beyond ABC.

The rules around technology matter too

Platforms, privacy, speech, competition, surveillance, copyright, and regulation increasingly determine what technology companies can build and what the rest of us have to live with. Browse more Raymond Tec News for practical coverage of technology policy and digital rights.

The FDA is asking what “competent” medical AI should mean

The Food and Drug Administration is wrestling with a deceptively simple question: how do you prove that a generative AI system is competent enough to participate in medical care?

Axios reports that the FDA is considering a “competency-based” approach for generative-AI-enabled medical devices, roughly borrowing the idea that a physician is evaluated on whether they can perform particular tasks safely and effectively. This is still a discussion paper, not a new rule or approval standard, and that distinction matters.

The problem it is trying to solve is real, though. Traditional device testing makes sense when a machine behaves predictably: give it the same input under the same conditions and you expect essentially the same result. Generative AI is messier. Outputs can vary, models can be updated, and a good benchmark score does not necessarily tell you whether the system remains reliable across thousands of real patients and clinical situations.

The FDA has already been asking how developers and hospitals should monitor these systems after deployment and detect performance drift. A competency-based approach would push the question toward the actual job being performed and the consequences when the AI gets it wrong. An AI system drafting routine paperwork and one influencing a diagnosis may both be “medical AI,” but they plainly do not carry the same risk.

There is nothing patients need to do because of this paper today. What I find encouraging is the framing: regulators are starting to move beyond treating AI like ordinary software with a test score stapled to it. In medicine, the question cannot just be whether the model is impressive. It has to be whether it is reliably good enough at the specific thing we are trusting it to do — and whether somebody notices when that stops being true.

Turning on AI is the easy part

Deciding what an AI tool should be allowed to see, who should use it, what work it should perform, and what happens when it gets something wrong is the more interesting problem. Raymond Tec helps businesses connect and automate the tools they actually use without treating every new feature like a button that obviously needs to be switched on.

None of these stories is really about a flashy new gadget. They are about governance: what a monitoring rule actually watches, what authority comes with a broadcast license, and how we decide an AI system is trustworthy enough for medicine. That stuff can look like paperwork right up until the rule underneath the system is wrong. Then suddenly it is the whole story.

Still in a reading mood? The Raymond Tec News archive covers security, AI, small-business technology, policy, and the places technology collides with ordinary life — without requiring a computer-science degree to get through it.

Google Workspace Has a Deadline, Plus 2 Tech Stories