Microsoft Patents a Share Button That Pushes App Content Straight Into a Teams Meeting
Instead of screen-sharing your whole monitor, imagine clicking a single button inside a third-party app and having just that app's content appear inside a Teams meeting. That's the specific problem Microsoft is patenting a fix for.
What Microsoft's in-app meeting share button actually does
Picture this: you're inside a project management app, looking at a chart you want to share with your team on a call. Right now, you'd probably alt-tab to Teams, fumble with screen sharing, and hope the right window shows up. Microsoft's patent describes a different approach: a share button built directly into the app itself.
When you click that button, it sends a signal to Teams telling it exactly what content to pull and how to display it. The developer of that third-party app gets to decide the format, whether that's a full-screen view, a side panel, or something else Teams supports.
The key idea is that sharing can happen from outside the meeting window, without you needing to be in the meeting stage at all. You hit share, and Teams handles the rest.
How the API call picks a sharing format for Teams
The patent describes a system where a third-party application (think a Jira board, a Figma file, or a sales dashboard) can embed a share control directly in its own interface.
When a user activates that control, it triggers an API call (a structured request sent from one piece of software to another) to Microsoft's collaboration platform. That API call carries two things:
- The specific content to share (a page, a document, a data view)
- A sharing protocol, which tells Teams which of its available display formats to use when presenting that content to meeting attendees
The platform then retrieves the content and pushes it into the active online collaboration using the format the developer specified. Crucially, this all happens from outside the meeting stage, meaning the user doesn't have to switch into the meeting window to initiate sharing.
Developers extend their app's manifest (a configuration file that tells Teams what an app can do) to register these share entry points and protocols, giving them fine-grained control over how their content lands in meetings.
What this means for Teams app developers and meeting hosts
For people who live in Teams all day, this is a meaningful workflow fix. Right now, sharing content from a third-party app into a meeting involves manual steps and often results in a clunky full-screen share. A native share button that respects Teams' own display formats could make co-presenting from external tools feel much less awkward.
For developers building Teams-integrated apps, the bigger deal is control. The patent gives app makers the ability to choose how their content is displayed in a meeting, not just whether it appears. That's a meaningful hook for ISVs (independent software vendors) building on the Teams ecosystem, and it fits Microsoft's broader push to make Teams a platform rather than just a video call tool.
This is unglamorous plumbing work, but the kind that actually changes day-to-day behavior. If Microsoft ships this as described, it addresses a real friction point in hybrid meetings without requiring users to learn anything new. The developer-side API control is the more interesting piece, since it gives Microsoft leverage to attract richer app integrations.
Which company should we read for you?
We track 17 companies here. Pro is the same weekly breakdown for any company you choose, delivered privately. Type a name and we'll scope it and send you a quote.
Get one Big Tech patent every Sunday
Plain English, intelligent commentary, no hype. Free.
Editorial commentary on a publicly published patent application. Not legal advice.