Declarative Copilot - "Provision" fails

[nanddeepn]

Describe the bug I have followed the article Build a declarative copilot for Copilot for Microsoft 365 to meet the prerequisites.

The Declarative Copilot provision fails with error:

Unable to execute action teamsApp/extendToM365. Error message: undefined
Failed to Execute lifecycle provision due to failed action: teamsApp/extendToM365.

To Reproduce Steps to reproduce the behavior:

1. Create Declarative Copilot
2. Click Provision.

Expected behavior The Copilot should get deployed and can be accessed from M365 Copilot chat.

Screenshots The Provision option fails with below error:

VS Code Extension Information (please complete the following information):

• OS: Windows 11
• Version v5.9.2024081502 (pre-release)

Additional context Below is the stack trace:

[2024-09-06T07:21:45.571Z] [Info] - Current VS Code locale is: en-us
[2024-09-06T07:21:45.890Z] [Info] - Teams Toolkit extension is now active!
[2024-09-06T07:22:04.641Z] [Info] - Executing provision 

Lifecycle stage: provision(4 step(s) in total). The following actions will be executed: 
(1/4) Action teamsApp/create: create Teams app.
(2/4) Action teamsApp/zipAppPackage: build Teams app package.
(3/4) Action teamsApp/update: update Teams app.
(4/4) Action teamsApp/extendToM365: acquire Microsoft 365 title with the app package

[2024-09-06T07:22:04.643Z] [Info] - Executing lifecycle provision
[2024-09-06T07:22:08.909Z] [Info] - (√)Done: Teams Package c:\New\TestCopilot\appPackage\build\appPackage.dev.zip built successfully!
[2024-09-06T07:22:11.818Z] [Error] - Unable to execute action teamsApp/extendToM365. Error message: undefined
[2024-09-06T07:22:11.823Z] [Error] - Failed to Execute lifecycle provision due to failed action: teamsApp/extendToM365. PackageServiceError:Request failed with status code 400 (tracingId: 00-a62ec9e7024e265a4a3e48728b4d1a64-7395db85a3c88fdd-00) BadRequest: No elements found in the manifest. . Env output: {"TEAMS_APP_ID":"5c816a56-87dd-41e8-a9ec-66f951c1952f","TEAMS_APP_TENANT_ID":"d0e8f2cd-23e6-4be2-9055-e321ac8b06fd","TEAMS_APP_UPDATE_TIME":"2024-09-06T07:22:10.3979966+00:00"}
[2024-09-06T07:22:11.826Z] [Info] - Execution summary:

Summary:
(×) Error: Lifecycle stage provision failed.
  (√) Done: teamsApp/create was executed successfully.
    (√) Done: Teams app 5c816a56-87dd-41e8-a9ec-66f951c1952f created successfully
  (√) Done: teamsApp/zipAppPackage was executed successfully.
  (√) Done: teamsApp/update was executed successfully.
    (√) Done: Teams app 5c816a56-87dd-41e8-a9ec-66f951c1952f updated successfully
  (×) Error: teamsApp/extendToM365 failed.
    (×) Error: Request failed with status code 400 (tracingId: 00-a62ec9e7024e265a4a3e48728b4d1a64-7395db85a3c88fdd-00) BadRequest: No elements found in the manifest. 

[2024-09-06T07:22:11.847Z] [Info] -   Created environment file (secret) at c:\New\TestCopilot\env\.env.dev.user

[huimiu]

Hi @nanddeepn, thanks for reaching out us. The Declarative Copilot is in private preview now, but it's going to be GA soon. Please stay tuned!

[VishalNagarAR]

Encountering the same issue while trying to build a declarative copilot. Followed the steps outlined in the documentation.

Lifecycle stage: provision(4 step(s) in total). The following actions will be executed: (1/4) Action teamsApp/create: create Teams app. (2/4) Action teamsApp/zipAppPackage: build Teams app package. (3/4) Action teamsApp/update: update Teams app. (4/4) Action teamsApp/extendToM365: acquire Microsoft 365 title with the app package

[2024-09-10T13:26:43.345Z] [Info] - Executing lifecycle provision [2024-09-10T13:26:48.752Z] [Info] - (√)Done: Teams Package e:\Teams\DeclarativeCopilot\EventPlanner\appPackage\build\appPackage.dev.zip built successfully! [2024-09-10T13:26:56.060Z] [Error] - Unable to execute action teamsApp/extendToM365. Error message: undefined [2024-09-10T13:26:56.066Z] [Error] - Failed to Execute lifecycle provision due to failed action: teamsApp/extendToM365. PackageServiceError:Request failed with status code 400 (tracingId: 00-da8f6ca79084cab1e27cb3e00c1e7518-202cccfe767fcab4-00) BadRequest: No elements found in the manifest.

Any insights or solutions would be greatly appreciated!

[huimiu]

Hi @VishalNagarAR, thank you for reaching out. The error is due to the fact that DC is still in private preview. Please wait until it goes GA, which will happen soon, and try again then.

[huimiu]

Hi @nanddeepn, @VishalNagarAR, declarative agents for Microsoft 365 are currently generally available, feel free to give it another try!