Claude for Manufacturing: Setup and the Microsoft 365 Connector

What Claude for Manufacturing is

Claude for Manufacturing is a plugin, not a separate app or a new model. A plugin bundles skills (written instructions for specific tasks) and connectors (links to business systems) so Claude can carry out a workflow inside the Claude apps your users already have.

Anthropic describes the scope as everything "from pricing a new job to diagnosing a stopped machine."

The 17 skills span sales, quality, operations, supply chain, design and setup. Some do one task; others chain several steps and stop when a person needs to review.

Anthropic's announcement and product page describe these workflows:

• Quoting a new job - Reads the customer's request, flags missing information and drawing gaps, compares costs on similar past jobs and drafts the quote. The estimator releases the quote.
• Failed inspection to 8D - Documents the failure, searches earlier nonconformance reports (NCRs) for the same issue, ranks likely causes and drafts the corrective action report (8D). The quality engineer verifies the fix.
• Machine down - Reviews sensor exports, repair notes, photos and the OEM manual and ranks probable causes. The technician decides what to check.
• Sourcing from another supplier - Prepares the request for quotes and compares the bids that come back. The buyer.
• Comparing designs in Autodesk Fusion - Creates variations of an existing model, scores them against the engineer's targets and drafts a decision memo. The engineer.
• Morning production report - Combines output versus target, downtime and the cost of downtime and missed output into one report. The plant manager.

The full list of 17 skill names is not published on the announcement, the product page or the Manufacturing Dive report we read. The plugin's directory listing on claude.ai requires a Claude sign-in, so we could not check it.

Anthropic says the skills are starting templates that you can customize to your own forms, and that it will add more skills over time.

The four connectors do different jobs:

• Autodesk Fusion: generates design variations so engineers can evaluate more options.
• Infor: lets buyers and planners look up purchase orders and stock. This connector only reads records. Infor is releasing its own "Infor in Claude" plugin that can also make changes in Infor after a person approves, and Anthropic says "Claude's access follows the buyer's Infor permissions."
• Microsoft 365: finds procedures, supplier emails and exported reports in shared folders and inboxes.
• Oracle NetSuite: pulls orders, inventory, production steps and job costs for quote pricing.

For systems without a connector (an older ERP, a quality system or an MES), Anthropic's answer is simple: save regular exports from those systems to Microsoft 365, and Claude works from the files.

That makes the Microsoft 365 connector the center of most small-plant deployments, and it is why the IT side of this rollout is mostly a Microsoft 365 project.

Who it is for and availability

Anthropic's product page is direct about fit. The plugin "fits best where each job gets its own quote, drawing, and routing," with quality issues handled through NCRs and 8Ds, which describes a typical job shop or contract manufacturer.

Asked whether it suits process manufacturers, Anthropic answers "Partly, today": food, consumer packaged goods, chemicals and steel producers can use the morning report, breakdown diagnosis and supplier skills right away, and can adapt the quoting and quality skills to batch records.

• Launch date: November 12, 2026
• Plans: Claude Team or Enterprise (the product page FAQ says paid plans, including Enterprise bought through AWS Marketplace)
• Price: No separate price published; the product page links only to general Claude pricing
• Named customers: None named in the announcement
• Roles it targets: Estimators, quality engineers, technicians, buyers, planners, engineers and plant managers
• Webinar: Technical webinar on November 17, 2026, at 11:00 a.m. ET

Anthropic's case for the product rests on one statistic it cites: in a 2025 Manufacturing Leadership Council survey, 79% of manufacturers said they enter data manually.

Lauren Collett, Anthropic's enterprise go-to-market leader, told Manufacturing Dive the goal is to cut the "internal toil" of gathering information from different systems, while "making sure a person is signing off on every draft."

Requirements

Before you start, confirm these on both the Claude side and the Microsoft side:

• A Claude Team or Enterprise plan, and an Owner or Primary Owner who can change organization settings. On Enterprise, a custom role that can manage the organization's libraries can also manage plugins. Anthropic's help center notes that the role labeled Admin in the members list does not include the plugins page.
• Cowork and Skills turned on for the organization. Anthropic's plugin management article says both must be enabled before you can use plugin marketplaces.
• A Microsoft Entra Global Administrator for the one-time tenant-wide consent of the Microsoft 365 connector. Users need work or school accounts in an Entra tenant with an active Microsoft 365 license.
• Accounts for the other systems you plan to connect: Oracle NetSuite, Infor or Autodesk Fusion, with the permissions each user should have. Anthropic says connectors typically respect each user's existing permissions.
• A decision on where exports will live in SharePoint or OneDrive if you have systems without a connector (see the Microsoft 365 section below).

How to set up Claude for Manufacturing, step by step

Anthropic's announcement gives three steps, and its plugin and connector help articles fill in the admin side. Steps below come from those pages; menu names are quoted as Anthropic writes them.

1. Make the plugin available to your users (Claude owner)

   Confirm Cowork and Skills are enabled for the organization. Install the plugin from Anthropic's plugin directory. The announcement's "Install the plugin" link opens the Claude for Manufacturing page in the directory, and the product page FAQ says admins install it from there.

   Choose who gets it in Organization settings > Plugins & skills. On the Inventory tab, open the plugin's row menu, choose Default access and pick an install preference: "Installed by default", "Available to install", "Required" or "Not available". Changes take effect on each member's next session or plugin refresh.

   On Enterprise, you can target a group instead: row menu > Group access… > Add groups next to Install targeting. Groups can be created manually or synced from your identity provider through SCIM. If a person is in several groups, the most permissive setting wins, so Anthropic's advice for a limited pilot is to set the organization-wide preference to "Not available" and grant access only to the pilot group.

   Members who were given "Available to install" find the plugin on the Discover tab in Customize > Plugins.

2. Add the connectors (Claude owner and Entra admin)

   For the Microsoft 365 connector on Team and Enterprise, a Claude owner goes to Organization settings > Connectors, clicks + Add, then All available, finds Microsoft 365 and clicks Add to your team. A Global Administrator then grants the tenant-wide consent described in the next section.

   The other three connectors are added and authorized for their own systems; Anthropic's manufacturing pages don't publish separate setup steps for them.

3. Tell Claude "Set us up"

   Any user with access opens Claude and types "Set us up." According to Anthropic, Claude then asks which systems the team uses, tests the connectors and reports which skills can't fully run yet.

   Treat that report as your gap list: it tells you which exports you still need to schedule into Microsoft 365.

4. Start with one measured process

   Anthropic's own guidance is that "one process is enough to start," with quoting or quality as the usual first choice. Pick one, record how long it takes today, and measure the same thing after a few weeks of drafts.

Preparing the Microsoft 365 connector: what IT must do

This is where most of the IT work sits. Everything below comes from Anthropic's "Set up the Microsoft 365 connector" article and its "Microsoft 365 connector security guide" unless marked as our recommendation.

Consent in Microsoft Entra ID

The connector uses delegated permissions only: it acts on behalf of the signed-in user through the OAuth 2.0 on-behalf-of flow, and app-only (service principal) access is not supported.

A Global Administrator grants a one-time consent for the tenant in one of two ways:

• Through Claude: a Global Admin with a Claude seat goes to Customize > Connectors, finds Microsoft 365, clicks Connect, chooses "Work or school account" if prompted, signs in and ticks the box to consent on behalf of the organization.

• Manually in Entra: used when the Global Admin has no Claude account, or for troubleshooting. This adds two service principals, M365 MCP Client for Claude (app ID 08ad6f98-a4f8-4635-bb8d-f1a3044760f0) and M365 MCP Server for Claude (app ID 07c030f6-5743-41b7-ba00-0a6e85f37c17), and grants admin consent for each with the documented URL:

  https://login.microsoftonline.com/{your-tenant-id}/adminconsent?client_id=<appId>

After consent, other users in the tenant connect without seeing a consent prompt.

Limit who can connect

In the Entra admin center, open the M365 MCP Server for Claude enterprise application, set Assignment required? to Yes under Properties, and add the permitted users or groups under Users and groups. Repeat for M365 MCP Client for Claude.

Anthropic says both apps must be restricted to the same people. For a pilot, use one security group for both apps and for the Claude plugin group above.

Least privilege: what the connector can read

By default the connector is read-only. The read scopes include Mail.Read, Mail.Read.Shared, Calendars.Read, Teams chat and channel read scopes, meeting transcript scopes, Files.Read.All and Sites.Read.All.

Write scopes such as Mail.Send, Files.ReadWrite.All and ChatMessage.Send are used only if you enable write tools.

Three details matter for least privilege:

• SharePoint search is tenant-wide. Anthropic says restricting search to specific sites isn't supported and site-specific .Selected scopes aren't supported. The boundary is each user's own SharePoint permissions, so anything a user can open, Claude can find for them.
• If your tenant has broad "Everyone except external users" sharing, fix that first; our Microsoft 365 Copilot oversharing readiness guide covers the same cleanup.
• You can revoke individual scopes. In Enterprise applications, open M365 MCP Server for Claude > Permissions > Admin consent tab, select a Microsoft Graph permission and choose Revoke. Revoking Mail.Read blocks Outlook, Sites.Read.All blocks SharePoint and Chat.Read blocks Teams chat. Tools that need a revoked scope fail with "Failed to call tool." Re-running admin consent restores the full default set, including write scopes, so revoke again afterwards.

Shared mailboxes are read-only, and the Online Archive is not searched. Mailbox search covers the primary mailbox and shared mailboxes the user can access, but not the separate In-Place Archive.

Write tools: keep drafts as drafts

If you enable write tools, each one can be set to Always allow, Needs approval or Blocked in Organization settings > Connectors > Microsoft 365.

For a manufacturing pilot whose whole point is "a person approves before anything goes out," our recommendation is to leave sending tools (Outlook send and forward, Teams send, post and reply, calendar changes) on Needs approval or Blocked.

Anthropic notes that sent emails carry an agent-attribution header, but file, calendar and Teams writes are not tagged, attachments are rejected, and calendar changes notify attendees automatically.

For organizations that added the connector before November 9, 2026, 11 sending and calendar tools move to Needs approval on or after December 9, 2026, unless you set them otherwise.

Where to keep the exports

Anthropic says only that teams can save regular exports to Microsoft 365. It doesn't prescribe a location. Our recommendation, based on how the connector's permissions work:

• Create a dedicated SharePoint site (for example, Plant Exports) whose members are only the people in the pilot group, rather than dropping exports into a broad team site or someone's OneDrive.
• Use file types the connector can read: Word, Excel, PowerPoint (including legacy formats), PDF, .txt, .md and .csv. OneNote and other formats can't be read.
• Name exports by system, report and date (for example, ERP_open-orders_2026-11-14.csv) and keep one folder per source system, so Claude and reviewers can trace figures back to a file.
• Apply a retention label or policy to the library so old exports don't pile up, and keep supplier pricing and customer drawings in sites with the narrowest membership.

One troubleshooting note from Anthropic: Claude adds isDoc