Access Lifecycle Check

Summary

OpenAI Workspace Agents, FedRAMP Moderate availability, the OpenAI-Microsoft partnership update, Anthropic-Amazon compute expansion, and the Sora shutdown all point to one Wednesday operator question: when AI access expands, shifts, or disappears, who owns the lifecycle before teams build on the wrong surface?

What Changed

• Workspace Agents point to reusable agent surfaces inside business workspaces.
• FedRAMP Moderate availability expands the regulated-access surface for ChatGPT Enterprise and the API Platform.
• OpenAI and Microsoft updated their partnership structure, creating a dependency-map refresh signal.
• Anthropic and Amazon expanded their compute collaboration for up to 5 gigawatts of capacity.
• Sora discontinuation keeps the sunset/export/migration question on the table.

Why It Matters

AI access is no longer a yes-or-no inventory question. Teams need to know whether each AI surface is approved, piloted, sunsetting, or blocked, and who owns evidence, fallback, communication, and exceptions.

Action Block

Run a 30-minute access lifecycle check:

1. List three AI surfaces people actually use or are requesting this week.
2. Mark each as approved, pilot, sunset, or blocked.
3. Name the admin owner, evidence owner, and sunset/migration owner.
4. Confirm export and fallback paths.
5. Send one plain-language memo about what is allowed, changing, ending, blocked, and who approves exceptions.