Claude teams received three changes that deserve one coordinated admin review: the July 24 announcement of Claude Opus 5, Microsoft 365 connector write tools, and Cowork remote sessions on web and mobile. The practical issue is not simply which feature is new. It is whether model access, delegated Microsoft permissions, and remote-agent controls are deliberate, documented, and tested before users rely on them for real work.
Quick Answer
Claude administrators should treat these updates as a readiness exercise. Confirm which users can select Opus 5 and at which effort settings; decide whether Microsoft 365 write tools are appropriate and complete both the Claude permission and Microsoft Entra consent steps; and review Cowork’s organization, remote-session, network, and trusted-device controls before wider use. This matters to teams using AI alongside CRM, collaboration, and customer-data workflows because permissions and operating context determine what a tool can actually do.
TL;DR
- Claude Opus 5: Anthropic’s July 24 release notes confirm the model launch. Seat defaults, effort defaults, availability, and pricing details in the July 24 email should be verified in each organization’s Claude settings rather than treated as universal public policy.
- Microsoft 365 connector: Write capabilities require two layers: updated Microsoft Entra consent and enabled write tools in Claude. Start with a restricted pilot and a draft-only email test.
- Cowork: Current public documentation describes web and mobile remote sessions as beta and gradually rolling out, beginning with Max. The email’s August 3/default-on statement was not corroborated by the public documentation reviewed.
- Governance: Remote sessions, Microsoft Graph scopes, connector permissions, and data-handling boundaries should be reviewed together—not feature by feature.
- Vantage Point relevance: A practical AI rollout connects workflow design, identity controls, data quality, and adoption across Salesforce, HubSpot, and connected systems.
What Changed
1. Claude Opus 5 launched
Anthropic’s Claude release notes list a Claude Opus 5 launch on July 24, 2026 and point readers to its product announcement. That confirms the launch, but the public release notes reviewed do not establish a universal entitlement matrix for standard versus premium seats, a default model or effort setting, or a pricing comparison.
A July 24 email notice describes Opus 5 as available immediately, says premium seats default to it at high effort across Claude chat, Cowork, and Claude Code, and says standard seats can select it. Those are useful tenant-specific operational signals, but they should be treated as notice-based until an administrator verifies the behavior in the organization’s current plan, model-access, and billing settings. Do not make a purchase, budget, or policy decision based on benchmark, “most advanced,” or price-comparison language from an email alone.
For Enterprise teams, Anthropic documents model-access controls that can govern the models and effort levels users can access. That makes a quick role and spend review more useful than a blanket assumption that every seat behaves the same way.
2. The Microsoft 365 connector can take write actions
Anthropic now documents write tools for the Microsoft 365 connector. With the appropriate permissions enabled, Claude can send or organize email, create and manage drafts, manage calendar events, update mailbox settings, and create or update files in OneDrive and SharePoint. Teams remains read-only.
This is not a single switch. Anthropic’s setup guide says organizations that consented before write tools launched need a Microsoft Entra Global Administrator to approve the updated permission set, then an admin must enable the desired write tools in Claude. A connector-wide setting does not replace a deliberate review of which write capabilities should be available. The email’s June 7 install-date and default-status distinction was not independently corroborated in the public guides reviewed; confirm the present configuration in the tenant instead.
Microsoft explains that delegated permissions let an application act on behalf of a signed-in user, but do not let it access data that user cannot already access. That is an important guardrail, not a substitute for least-privilege design, data classification, conditional access, or testing.
3. Cowork can run remote sessions on web and mobile
Anthropic’s current Cowork documentation says web and mobile Cowork uses remote sessions in beta. Sessions and files are associated with the Claude account, work can continue after a laptop is closed, and scheduled tasks can run without a device online. Desktop remains important for capabilities that reach local files, local connectors, browser use, or computer use; a remote session can use those local resources only through an online Claude Desktop app and connected folders.
The July 24 email stated that web/mobile Cowork would turn on August 3 and be on by default. The official documentation reviewed instead says the feature was available beginning July 7 and is rolling out over several weeks, starting with Max and expanding to more plans. It does not corroborate a universal August 3 or default-on rollout. Check the organization setting and each plan’s actual availability before communicating a date to users.
Who Is Affected?
| Group | What may change | Decision to make |
|---|---|---|
| Claude organization owners | Model access, connector enablement, Cowork availability | Define approved users, use cases, and escalation owner. |
| Microsoft Entra Global Administrators | Consent to updated delegated Graph scopes | Review the exact requested scopes and approve only after a security review. |
| Microsoft 365 administrators | Enterprise app assignment, conditional access, audit review | Pilot with a small security group and retain a rollback path. |
| Team and Enterprise users | Model selection, remote sessions, connector actions | Train users on approved data, confirmation steps, and task boundaries. |
| CRM, RevOps, and IT teams | AI outputs can affect customer and operational workflows | Map where Salesforce, HubSpot, Microsoft 365, and integrations exchange data. |
What Admins Should Do Now
- Inventory the current state. Record the plan, seat types, model-entitlement settings, connector status, Cowork status, and who owns each control. Capture screenshots or change records before altering defaults.
- Verify Opus 5 in the tenant. Check the model selector, role-based model access, effort choices, usage controls, and any plan-specific limits. Communicate only the behavior users can actually see.
- Separate consent from enablement for Microsoft 365. Have a Microsoft Entra Global Administrator review and approve the updated permissions. Then enable only the individual Claude write tools the pilot needs. Do not treat successful consent as proof that write actions are enabled, or vice versa.
- Run a low-risk pilot. Restrict the enterprise application to a small group, use a test mailbox and non-production SharePoint library, and begin with creating a draft email to the user—not sending email externally.
- Review Cowork controls before expansion. In Organization settings, review the Cowork toggle, remote-session control, network-access policy, persistent approval setting, and trusted-device requirement. For managed devices, assess the documented MDM controls for local MCP servers and desktop extensions.
- Make the workflow explicit. Define which tasks may read, draft, send, create, update, or delete. Require human review for customer communications, calendar changes, system-of-record updates, and any workflow that moves data between platforms.
- Connect the rollout to operating systems. Teams evaluating AI-assisted CRM work should align the pilot with AI-driven personalization and analytics, system integration and data migration, and advisory and change management—not deploy an isolated tool without process ownership.
Permissions and Readiness Checklist
| Area | Verify before enabling | Practical control |
|---|---|---|
| Opus 5 access | Model appears for the intended seat/role; effort options and usage limits are understood | Pilot high-effort work with bounded tasks; monitor usage before broad default changes. |
| Entra consent | Global Administrator has reviewed the current updated delegated scopes | Document scope review and use Entra assignment to limit the pilot group. |
| Claude connector tools | Each write tool is intentionally set to Allow or Ask | Begin with drafts and file creation; avoid broad send/delete access initially. |
| Microsoft Graph data | Users only reach data they already can access; existing conditional-access policies apply | Validate MFA, device compliance, group assignment, and DLP behavior. |
| Cowork remote sessions | Organization setting, remote-session policy, network policy, and trusted-device requirements are understood | Enable by cohort; turn off persistent approval for sensitive pilots. |
| Local access | Connected folders, desktop app state, browser use, MCP servers, and extensions are reviewed | Limit connected folders and use MDM controls where appropriate. |
| Monitoring | Teams know the available evidence and gaps | Review Microsoft 365 audit logs and organizational telemetry; do not assume Cowork is covered by audit logs, Compliance API, or data exports. |
Governance and Security Guidance
The Microsoft 365 connector uses delegated permissions: Claude acts in the context of a signed-in user and cannot bypass that user’s existing Microsoft 365 access. Anthropic also documents that connector access can be gated in Claude organization settings and restricted through Entra assignment and conditional access. Those controls support a least-privilege rollout.
Write actions raise the operational risk. Anthropic notes that sent email includes an agent-initiated attribution header, while file and calendar writes are not currently tagged. Attachments are not supported in connector write actions, and limits apply to writes, sends, and recipients. Build controls around the actions that have the greatest business impact: sending external messages, changing meetings, altering mailbox rules, and modifying shared files.
Cowork remote sessions run in isolated, temporary sandboxes on Anthropic-managed infrastructure. Anthropic says remote sessions have no access to a private network by default, use enforceable egress controls, and use short-lived session credentials. But remote execution also changes the data-processing context: work and any local files opened through the desktop bridge are processed on Anthropic’s servers under the applicable commercial commitments. Admins should assess this against their data classification and retention policy.
One critical monitoring caveat: Anthropic’s Cowork architecture guide says Cowork activity is not currently captured in audit logs, the Compliance API, or data exports. The July 24 email’s assertion about OpenTelemetry coverage for web/mobile Cowork was not independently corroborated in the public sources reviewed. Ask Anthropic or validate in your telemetry environment before relying on it for a control objective.
For teams connecting AI to revenue operations, this is also a data-quality question. Use HubSpot technology services and Salesforce implementation and advisory work to establish ownership, record-quality standards, and human approval points before AI-generated actions reach customer-facing systems.
Timeline
| Date / status | Verified interpretation |
|---|---|
| July 7, 2026 | Anthropic release notes document Microsoft 365 connector write tools and Cowork web/mobile availability, with Cowork rolling out over several weeks starting with Max. |
| July 24, 2026 | Anthropic release notes document the Claude Opus 5 launch. |
| July 24 email notice | States seat/default behavior, effort behavior, a June 7 installation distinction, and an August 3 Cowork/default-on rollout. Treat these as notice-based until verified in the relevant organization. |
| Before broad rollout | Complete scope review, configure individual tools, pilot with a limited group, test, train, and document rollback. |
How Vantage Point Helps
Vantage Point helps organizations turn AI product changes into governed operating workflows. We can assess data readiness, identity and permission boundaries, Salesforce and HubSpot process impacts, integration architecture, and user adoption so a pilot has clear controls and a path to scale. If your team is evaluating Claude alongside Salesforce, HubSpot, Microsoft 365, or connected systems, talk with Vantage Point about a practical AI and CRM implementation plan.
FAQ
Is Claude Opus 5 automatically available to every business user?
Not necessarily. Anthropic’s July 24 release notes confirm the launch, while the email describes seat-specific behavior. Administrators should verify their current plan, seat type, model-entitlement settings, and model selector before telling users that Opus 5 is default or available.
What must happen before Claude can write to Microsoft 365?
Two things must happen: a Microsoft Entra Global Administrator must consent to the updated permissions, and a Claude admin must enable the appropriate write tools. An organization should then test with a low-risk action, such as drafting an email to the user without sending it.
Which Microsoft 365 actions can Claude take when write tools are enabled?
Anthropic documents actions for email, drafts, categories, inbox rules, automatic replies, calendar events, and OneDrive/SharePoint files. Teams remains read-only, and attachment-based email actions are not supported.
Do Microsoft 365 connector permissions bypass a user’s existing access?
No. The connector uses delegated permissions, so it acts on behalf of the signed-in user and cannot access data the user could not otherwise access. Administrators should still apply least privilege, group assignment, conditional access, and data-loss-prevention controls.
Is Cowork on web and mobile generally available for every plan?
The public Cowork article describes web and mobile remote sessions as beta and gradually rolling out, beginning with Max and expanding to more plans. Check current plan availability and organization settings instead of relying on a universal rollout date.
Does a remote Cowork session gain unrestricted access to a laptop or private network?
No. Anthropic says remote sessions run in isolated cloud sandboxes and cannot reach private or internal network addresses by default. Access to local files, browser use, or local connectors requires the Claude Desktop app to be online and is limited by connected folders and configured permissions.
Can we use Microsoft 365 or Cowork logs as our complete audit record?
No. Microsoft 365 Graph activity can be reviewed in Microsoft 365 audit logs, but Anthropic says Cowork activity is not currently captured in audit logs, the Compliance API, or data exports. Design monitoring around the evidence each system actually provides.
How should Vantage Point support a Claude rollout?
Vantage Point can help align AI capabilities with CRM workflow design, integration boundaries, data quality, permission models, and adoption plans. The goal is a controlled pilot that creates useful work without adding unmanaged data or process risk.
