How to Run a Free Trial and Find Out Whether Your Team Uses Claude Enterprise Well

If your company already pays for Claude Enterprise, you can learn how those licenses are used without buying anything new for several weeks: turn on the Compliance API, connect it to a partner that offers a free trial, and measure for 14 to 30 days.

Giving the whole team a Claude account is easy. The hard part comes afterwards, when you need to answer three questions: who actually uses it, what data is being pasted into chats, and whether anyone is sharing information they should not. The admin console does not show the content of conversations. That is what the Compliance API is for, and more than 100 security platforms already connect to it.

What the Compliance API is

It is an Anthropic REST API, included in Claude Enterprise, that gives your security tools visibility into what happens inside your Claude organization. It costs nothing extra: it comes with the plan, but only the Primary Owner can turn it on (Anthropic).

With a Compliance Access Key, a partner can read:

Conversations: chats, uploaded files and projects.
Cowork and Claude Code sessions: prompts, responses, tool calls, skills and artifacts.
Add-ins: Claude for Microsoft 365 and Claude Science (beta).
Activity Feed: sign-ins, administrator actions and configuration changes.
Directory: users, roles and groups.

The API can also delete chats, files and projects, which helps when answering privacy requests (technical documentation).

Partners you can try without paying

There are two families of tools. Content tools (DLP, DSPM, insider risk) read chats and files and tell you which sensitive data was shared. Log tools (SIEM, pipelines) receive the Activity Feed and show you who signs in, when, and what changes. For a complete trial, combine one of each.

Partner	Family	Free offer	Duration	What it shows you about Claude
Check Point Workforce AI Security	Content	Free trial on request	Not published	Usage by user and by surface (web, desktop, mobile), exposed PII and credentials
Nightfall AI	Content	Free trial through sales@nightfall.ai	Not published	PII, PHI, PCI, secrets and source code in chats and files (monitoring only)
Varonis	Content	Free Data Risk Assessment, with full platform access and an analyst	For the length of the assessment	Claude usage, possible misuse and risk in the context of permissions and data
Strac	Content	Proof of value in your own environment	Not published	PHI, PII, PCI, secrets and credentials in conversations
Sumo Logic	Logs	Trial with no card; becomes a Free account afterwards	30 days (1 GB/day, 20 users)	Activity Feed through the Claude Compliance API app
Elastic	Logs	Elastic Cloud trial with no card	14 days	Audit and usage activity for detection and investigation
Cribl	Logs	Cribl.Cloud Free plan, permanent	No limit (up to 1 TB/day)	Normalizes, masks and routes events to another tool; does not analyze on its own

Trials of content tools are requested from the sales team, and their length is negotiated. Log tools can be activated on their own from the vendor's website. Microsoft Purview also has a Claude connector, but it is in preview and requires pay-as-you-go billing, so it is not free. The full list of more than 100 partners is in the Claude Help Center.

Step by step: setting up the trial

The full trial takes about 30 days; the technical setup fits in an afternoon.

Define the goal and scope. Pick 2 or 3 concrete questions, for example "who is not using their license?" or "is customer data being shared?". Inform Legal and Human Resources, and review your acceptable use policy before reading conversations.
Turn on the Compliance API. The Primary Owner goes to Organization settings > API, enables the Compliance API and creates a Compliance Access Key under Keys > Create key (Anthropic).
Grant only the permissions needed. For the log tool, read:compliance_activities is enough. Give the content tool the user-data permission as well, and never the delete permission.
Request the trials. Activate the free account of the log tool from its website. For the content tool, write to the sales team and ask for a trial that covers at least 30 days.
Connect the key. In the partner's console, add the Claude integration and paste the key. In Nightfall, for example, it is Integrations > Add Integration > Claude Enterprise (Nightfall).
Let the data flow. Allow at least a day for the first events to appear. Review the dashboards once a week.
Close with a report. On day 30, compare what you found with your initial questions and decide whether to buy, switch partners or adjust policies.
Revoke the key when you finish. If you do not continue with a partner, delete its key in Organization settings > API and ask them to delete the data they stored during the trial.

What to measure during the trial

Using Claude "appropriately" means two things: the licenses you pay for are used, and data that must stay inside the company is not exposed. These signals answer both.

Signal	What it indicates	Where you see it
Licenses with no sign-in in 30 days	Spend on accounts nobody uses	Log tool (Activity Feed)
Usage by team and by surface (web, desktop, Claude Code)	Where training is needed and where Claude already adds value	Content or log tool
PII, card or health data in prompts and files	Regulatory and privacy risk	Content tool (DLP)
Credentials, API keys or source code pasted into chats	Direct security risk	Content tool (DLP)
Role or SSO changes, or keys created outside the process	Governance gaps in administration	Log tool
Connectors and MCP servers enabled	Internal data Claude can read	Content or posture tool
Projects shared with sensitive information	Unnecessary internal exposure	Content tool (DSPM)

Findings are an opportunity to train the team, not to punish it. Most exposures come from people who did not know which data is allowed in Claude.

Conclusion

The Compliance API already comes with your Claude Enterprise, and several of the platforms that connect to it can be tried for free. In a few weeks you can go from "we handed out licenses" to "we know how they are used". The only requirement is for the Primary Owner to turn on the API and create a key with the minimum permissions.

Start this week: pick one content partner and one log partner, define the pilot, and schedule the results meeting 30 days out.