Can Microsoft Copilot Connect to LinkedIn?

This question comes up more often than any other version of it, and for a good reason. Microsoft bought LinkedIn in 2016. Microsoft builds Copilot. It feels obvious that the two should talk to each other, and that Copilot ought to be able to write and publish your LinkedIn posts without any of the setup other assistants need.

It does not work that way, and the reason is worth understanding, because it explains how every AI-to-LinkedIn connection works.

Does Microsoft owning LinkedIn mean Copilot can post for me?

No. Owning the company that runs a service is a business fact. It is not a permission your account has granted.

When any application publishes a post as you — whoever built it — it has to hold an access token issued for your specific member account through LinkedIn’s own OAuth flow. OAuth is the open sign-in standard behind every “Continue with LinkedIn” button: you approve on LinkedIn’s own page, and the app receives a limited, revocable key instead of your login details. That key carries named permissions, called scopes. The one that allows publishing on your behalf is w_member_social.

That requirement is about consent, not about corporate structure. LinkedIn cannot hand your posting rights to a sister product any more than it can hand them to a stranger, because the thing being protected is your account, and only you can grant access to it. If a Microsoft product ever does publish to LinkedIn for you, you will still see a LinkedIn permission screen, and the grant will still appear in your LinkedIn settings where you can revoke it.

So the useful question is not “does Microsoft own LinkedIn”. It is “does the specific Copilot product I use support connecting to an outside tool, and has that tool been granted LinkedIn posting permission by me”.

Which Copilot do you actually mean?

Half the confusion here is that “Copilot” is not one product. Microsoft has used the name across several very different things, and what one of them can do tells you nothing about the others.

These sit on different plans, with different admin controls and different ways of adding outside tools. A feature announced for one is not automatically present in another, and on a work account an administrator can switch parts of it off no matter what the documentation says is possible.

So can Copilot connect to an outside tool at all?

Honestly: we are not certain what is available in your version today, and saying so is the correct answer rather than a dodge.

Microsoft has been building extensibility into its Copilot products for a while — the general idea being that an assistant can call out to another system instead of only answering from what it already knows. The industry standard for that kind of link is MCP, the Model Context Protocol, an open specification for connecting AI assistants to outside tools. But which Copilot product supports which connection method, on which plan, behind which admin toggle, is exactly the sort of detail that shifts between releases. Anything specific written here would be stale before you read it.

What does not change is the list of questions to ask, even when the menus move:

• Does your Copilot product support adding external tools, agents, plugins or connectors at all? If it does not, nothing else matters — the answer for you is no, today.
• Is that feature on your plan? Extension features are usually paid or business-tier, not free-tier.
• Has your organisation allowed it? On a work account an administrator decides which external tools are permitted. This stops more people than any technical limit does.
• Does it support remote MCP servers specifically? Some extension systems only accept tools built to that vendor’s own format, which is a different thing from supporting the open standard.
• When you connect a LinkedIn tool, does LinkedIn itself show you a permission screen? If it never does, the tool is not using LinkedIn’s official API, and you should find out what it is doing instead.

Microsoft’s documentation answers the first four. The fifth you can see with your own eyes during setup.

What does any assistant need in order to post to LinkedIn?

Whichever assistant you end up using, the LinkedIn side of the job is identical. It is worth knowing, because it lets you judge any tool that claims to do this.

• Identity. Sign In with LinkedIn using OpenID Connect, so the tool knows which member it is acting for.
• Posting permission. The Share on LinkedIn product, which grants the w_member_social scope. Both of these are free, self-serve LinkedIn products — no partner status needed.
• A real publishing endpoint. Posts go through POST /v2/ugcPosts, or LinkedIn’s newer versioned /rest/posts interface for multi-image and document posts.
• Somewhere safe to keep the token. LinkedIn member tokens last around 60 days and, for self-serve apps, come with no refresh token, so you reconnect periodically. The token should stay encrypted on the tool’s backend and never be handed to the AI model itself.

Notice what is not on that list: any special relationship with Microsoft. A tool built by one developer and a tool built by Microsoft go through the same door.

What is confirmed to work right now?

Kalovio is a free, hosted MCP server for LinkedIn. Here is exactly where it has been tested:

• Claude — confirmed working. You add it as a custom connector, and it works on Claude’s free plan.
• ChatGPT — confirmed working. It needs Developer Mode, which is on the paid plans, is web only, and the connector has to be switched on per conversation from the tools menu.
• Microsoft Copilot — untested. We have not tried it, so we are not claiming it works and we are not writing steps for it.
• Codex — not supported. Connecting in ChatGPT does not carry over; each app connects on its own.

Underneath it uses exactly the components listed above: LinkedIn OAuth, the w_member_social scope, the official publishing endpoints, and tokens encrypted with AES-256-GCM that never leave the backend. Nothing is scraped — no cookies, no borrowed browser session. Before anything publishes, a two-step confirm gate shows you a preview plus a signed token covering the exact content, and nothing is sent until you approve that exact text. That gate is there to stop hidden instructions in something the model read from posting on your behalf.

It has real limits too. It cannot read posts it did not create, because the permission for that is closed to self-serve apps. It gives you link-click tracking but no engagement analytics, which needs a partner-gated LinkedIn API. Document and PDF posts publish immediately and cannot be scheduled yet. Multi-image and document posts use LinkedIn’s newer versioned interface, which may not be switched on for every self-serve app — a refusal is reported clearly, so try it on your own account. It cannot send messages, send connection requests, or collect leads. It is in free public beta with no card required, and pricing may change later.

Is publishing through an AI assistant allowed by LinkedIn?

The route that gets accounts into trouble is a different one: tools that ask you to paste a session cookie and then drive your logged-in browser. The most popular open-source LinkedIn MCP server warns in its own README that accounts “can be restricted or banned”, and also states it “does not publish or create posts on your behalf” — it reads data, it does not write.

What should I do if I am on Copilot?

Start with Microsoft’s current documentation for your specific Copilot product, and find out whether external tools or MCP servers can be added on your plan, and whether your administrator permits it. If they can, the LinkedIn tool still has to hold its own OAuth grant from you — Copilot being a Microsoft product changes nothing about that requirement.

If your Copilot cannot add outside tools today, the confirmed path is a different assistant. Claude on its free plan is the lowest-friction option we have tested, and ChatGPT works on a paid plan in Developer Mode. Neither is Microsoft, but both are proven, and either way your LinkedIn account stays under your control through a consent screen you can revoke.