Tag: enterprise-ai
Claude inference hooks cannot see a screenshot
Anthropic now lets an Enterprise organisation put its own server in front of every prompt and return allow or deny before the model runs. It is the strongest inline control Claude has shipped. It also never receives raw image bytes, so a screenshot of the document you are trying to stop walks straight through, and the failure mode when your server goes down is a setting somebody has to choose.
Claude US-only inference costs 1.1x and that is the cheapest part
The Enterprise console offers one toggle that keeps all model inference in US regions for a 10 per cent surcharge. Underneath it are two independent settings, one of which is a one-way door you set when you create a workspace and can never change. The surcharge is the part everybody reads and the least expensive of the three costs.
The Claude Enterprise admin console has 25 sections and no map
Claude Enterprise puts 25 settings sections behind one nav, grouped into four blocks that do not match how anybody actually governs AI. Here is the whole tree, what each block controls, and the six settings worth opening on your first day as an Owner rather than the twenty-five you will otherwise scroll past.
Why your Claude Microsoft 365 connector is still read only
Anthropic shipped write tools for the Microsoft 365 connector on July 7, 2026, and left them switched off for every organization that had connected before that date. Nothing in the product says so. Here is how to check in ten seconds, the two admin gates in two different consoles, the scope that deserves a second look, and the write path already running in your building that will derail the diagnosis.
An MCP server is unreviewed code with your file system in scope
Treat every MCP server as untrusted code that runs with the access your agent has, because that is what it is. Anthropic docs say the directory lists connectors but does not security-audit them. A registry of approved servers with nothing enforcing it is a memo. The control that binds is a managed allowlist matched by URL or command, never by name.
Claude is allowed in regulated finance, but it has no EU data residency
Two objections kill most regulated-finance AI conversations before they start. The first, that Anthropic does not permit Claude for regulated work, is false: Claude for Financial Services exists, banks run it, and the usage policy names finance high-risk, not forbidden. The second is real and almost nobody states it plainly: first-party Claude Enterprise has no EU data residency at all. There is no "eu" inference region and workspace storage is US-only. If you are FCA-regulated, that is the fact to design around, and the only EU route runs through a hyperscaler.
Your Claude Code deny rules are not a security boundary
Before you hand Claude Code to hundreds of people you add deny rules for .env and credentials and feel locked down. You are not. Those rules govern Claude own tools, not a Python one-liner that opens the same file, and the control that actually holds, the OS sandbox, reads your whole machine by default and fails open when it cannot start. The baseline worth setting is real. Its dangerous gaps are the defaults you never changed.
Your locked-down Claude sandbox is a holding pattern, not a destination
Giving everyone Claude inside an isolated VM, no sensitive data allowed, feels like the safe way to start. It is a fine way to start. The trouble is what happens when you leave people there: the leak it was built to stop walks out by copy-paste anyway, the friction recruits the shadow AI you were trying to prevent, and the value never compounds because nothing in an ephemeral box survives the session. A sandbox is a scaffold. Scaffolds come down.
Blocking the personal Claude account is an identity problem, not a network one
Your CISO trusts the control posture Microsoft gives Copilot. To get Claude to the same bar, do not reach for tenant restrictions: that header only fires on your network, so it is theater the moment a laptop goes off-VPN. The control that holds lives at identity. Enforce SSO, then claim your domain, and know that the claim is a one-way door.
Claude Code behind a TLS-inspecting proxy: configure the tool, not the proxy
Locked-down shops reach for a proxy exception to make Claude Code connect. Wrong move, and it fails anyway. Claude Code does not pin certificates, so it works through full TLS inspection once you teach it to trust your corporate root CA. The fix is a couple of environment variables and an egress allowlist, not a hole in the proxy.
You are at phase zero, and the deck you were sold starts at phase three
Every enterprise AI maturity model starts a rung above where most companies stand and skips the one that holds the rest up: getting the tool safely into people hands. Your team already has Claude. If IT cannot produce the tenant policy, the egress allowlist, the tool allowlist, and the audit log, you are at phase zero, whatever the deck says.
Your AI context layer is only half a brain
An AI context layer feeds every model one governed source of company truth, and DataHub and Atlan will sell you that read half today. The half that notices when a person did not get what they wanted, the re-ask nobody logged, is what turns a knowledge store into a brain.
Should you build your agents in Copilot Studio? The demo is not the question
Low-code agent builders like Copilot Studio get you to a working demo in an afternoon. That is real, and it is also the trap. The question is not whether it demos well. It is what you give up the day you need control, and whether you will need control.
Stop building "the ERP agent." The value is in skills that cross functions
Companies build AI agents shaped like their org chart: an ERP agent, an HR agent, a finance agent. Each one is a silo with a chat box. The real payoff shows up when skills compose across functions, because data exists to tell a story or trigger an action, not to sit in one department.
The hard part of analytics AI is not the answer, it is figuring out the question
Everyone obsesses over whether the model reasons well. The real failure in AI over business data happens earlier, at the moment the agent decides what you meant. A confident answer to the wrong question is worse than no answer at all.
Your AI has no whoami
Every enterprise AI platform resolves what you can access through SSO and SCIM. None of them load your team instructions from who you are. Claude gives admins one 3,000-character field for everyone. Microsoft Copilot reads your permissions but not your team playbook. Here is the gap and what works today.
CLAUDE.md hierarchy: lock at two levels, split the libraries, audit the rest
CLAUDE.md hierarchy looks tidy in a personal repo. Push it across departments and it splits into a tree most users cannot reason about. Lock at two levels. Split read-only governance from read-write working content. Run a seven-check audit on every new file. Anything deeper is a vanity hierarchy that breaks in weeks.
Ask Your Org, and the case for scoping Claude yourself
Claude Ask Your Org connects Claude to Slack, Microsoft 365, and Drive in one project. Its security model is sound, permission-aware and not indexed. The question it makes easy to skip is scope. Here is when to use the broad tool and when to scope Claude yourself with a filesystem MCP server.
Claude Code enterprise security is a design problem
Most guides to running Claude Code in an enterprise stop at the install. That is the easy ten percent. The real work is the security design around an agentic tool that runs commands and reads files: the audit trail, prompt injection, permission modes, and a managed policy file.
How to make a single root CLAUDE.md load across your whole organization
Drop a CLAUDE.md at the root of a SharePoint site and nothing propagates. Each Claude product reads CLAUDE.md a different way. Four parallel loaders, all pulling from one canonical file, are what makes a single source of truth actually land in every session across Claude Code, Desktop, web, and Cowork.
How to run Claude in compliance-heavy environments
Running Claude on regulated data is a solved problem in 2026 if you pick the right deployment surface and match it with the right contractual paper. Three architecture patterns cover HIPAA, SOC 2, GDPR, FINRA, FedRAMP, and ITAR. Most compliance objections are fixable, and the real leak paths are almost never the model.
SharePoint vs OneDrive for AI - where your files live decides what AI can see
When AI indexes your files, SharePoint and OneDrive expose data very differently. Here is how permission models, governance gaps, and the oversharing problem change everything about where you store documents for AI workflows.
What Claude office agents actually do and why you should care
Claude office agents let Claude share context across Excel and PowerPoint through a single toggle. Here is what the feature actually does, what the Skills framework changes, and the security gaps you need to know about before enabling it.
Your employees are generating AI code nobody governs - here is what to build
45% of AI-generated code contains security flaws. Most of it lives on employee laptops with zero scanning, logging, or continuity planning. Here is a three-pillar blueprint that costs a fraction of the reactive support it replaces.
Plugins, connectors, and skills in Claude - what each one does
Claude offers three distinct extension mechanisms - connectors for data access, skills for custom instructions, and plugins for team-wide bundles. Each carries different security implications and admin controls that Anthropic does not make obvious upfront.
Why organizing your files comes well before doing any sort of AI
A Seagate study of 1,500 enterprise leaders found 68% of business data went unused in 2020. AI amplifies whatever state your files are in. If SharePoint is a graveyard of duplicate presentations and orphaned project sites, AI just indexes the mess faster. File organization is not a nice-to-have before AI adoption. It is a prerequisite.
Claude inside Copilot: what your company is actually buying
Claude models now run inside GitHub Copilot at no extra cost. That does not mean Copilot replaces a direct Claude subscription. The context window shrinks on some clients, and you still lose a few Claude features. Most mid-size teams end up needing both. Here is what to buy and why.
How to standardize on one AI vendor without your team going around you
Harmonic Security analysed 22.4 million AI prompts across enterprises and found 665 distinct tools in use. ChatGPT alone caused 71.2% of data exposures. Standardizing on one vendor is not about picking favorites. It is about making the approved option so good that nobody bothers looking elsewhere.
Your team is producing 500 documents a week with Claude and none of them look like yours
Claude Projects carry no published character limit on instructions. You can paste an entire 80-page brand guide. But most companies have not done this, so every AI-generated document goes out with default formatting and generic voice. The five-layer brand enforcement stack fixes this systematically without slowing anyone down.
How to build an AI champions network that actually drives adoption
AI4SP research across 115,000 organizations and individuals found 80% satisfaction with off-the-shelf AI tools but under 40% for enterprise-sanctioned deployments. The companies getting adoption right build three-tier champion networks where trusted peers test, validate, and spread use cases from the middle of the organization outward.