Solution with Copilot Component and Webpart with TeamsTab Enabled

[joaojmendes]

What type of issue is this?

Question

What SharePoint development model, framework, SDK or API is this about?

💥 SharePoint Framework

Target SharePoint environment

SharePoint Online

What browser(s) / client(s) have you tested

• 💥 Internet Explorer
• 💥 Microsoft Edge
• 💥 Google Chrome
• 💥 FireFox
• 💥 Safari
• mobile (iOS/iPadOS)
• mobile (Android)
• not applicable
• other (enter in the "Additional environment details" area below)

Additional environment details

• SPFx version : 1.24.0-beta-5

Issue description

I have an SPFx solution that contains both a Copilot Component and a Web Part. The Web Part has teamsTab enabled so that it can be added as a tab in Microsoft Teams.

I deployed the .sppkg package to the Tenant App Catalog and selected the option to deploy/sync the solution to Teams.

However, when I try to add the Web Part as a Teams tab, Teams tells me that I need a Copilot license and does not allow me to add the app.

I believe there is an issue with the Teams package generated during the deployment process. It appears that the generated Teams app package is created specifically for the Copilot Component, and the Web Part configuration is not correctly included or handled.

In this scenario, I believe we need separate Teams app definitions/packages:

• One for the Copilot Component
• One for the SPFx Web Part with teamsTab enabled

This is also how I was able to make the solution work.

As a workaround, I manually created a separate Teams app manifest specifically for the Web Part, generated the corresponding .zip package, and uploaded it to the Teams App Catalog. After doing this, I was able to add the Web Part as a Teams tab successfully.

I believe this process should be handled automatically.

When an .sppkg containing both a Copilot Component and a Teams-enabled Web Part is deployed to the Tenant App Catalog, the deployment process should either:

1. Automatically generate the appropriate Teams app packages/manifests for both components, or
2. Preserve the existing out-of-the-box behavior for the Web Part, where deploying/syncing the .sppkg to Teams automatically generates the Teams app required for the teamsTab-enabled Web Part.

Currently, the presence of the Copilot Component appears to override or interfere with the normal Teams app generation for the Web Part.

[m365-agent-toolkit-assistant]

👋 Hi João Mendes (@joaojmendes),

Thank you for reporting this issue. Here is an AI-generated initial response:

Classification: Bug — the reported mixed-package behavior appears inconsistent with documented SPFx support for packaging Copilot UX components alongside web parts and automatically generating Teams packages for Teams-enabled web parts.

• You observed that Teams asks for a Copilot license when adding the tab, while a separately packaged tab works. That points to package selection or generation, but does not establish the cause or which service owns it.
• Preview guidance says Copilot UX components themselves do not require a Copilot license. It does not explain why Teams presents that prompt for this app.

Upgrade check: SPFx 1.24.0-beta-5 is the latest preview listed in the release notes; no fix for this combination is documented.

What to do now:

1. Continue using the separate Teams tab package as a workaround.
2. Download the generated Teams package using the App Catalog API documented below. Compare its manifest with your working package, especially configurableTabs and the web-part component ID.
3. Share the redacted manifests and exact Teams license message to help isolate the failure.

Useful links:

• No sufficiently relevant related issue found in the searched repos.
• SPFx Copilot UX components and mixed solutions
• SPFx Teams deployment and generated-package download
• Teams app package requirements
• SPFx 1.24 preview release notes

---

Note: AI-generated guidance may be incomplete or incorrect. Please verify suggestions before applying them.