Declarative copilot provisioning fails with 404

[benedikt-udg]

Describe the bug
When creating a new declarative agent with the Teams Toolkit and then running "Provision", the provisioning fails with the following error message:

[2024-11-05T12:19:18.082Z] [Error] - Unable to execute action teamsApp/extendToM365. Error message: undefined
[2024-11-05T12:19:18.084Z] [Error] - Failed to Execute lifecycle provision due to failed action: teamsApp/extendToM365. iwt:Request failed with status code 404 (tracingId: 00-08e4e96afafd96e1bb5b84052ff56f46-0561270c4169cbaf-01) : . Env output: {"TEAMS_APP_ID":"5f3e7e2a-7e08-44e5-88f7-c8e45e40cd00","TEAMS_APP_TENANT_ID":"6ffe90e7-2d89-47e6-97bf-c03294cf3e63","TEAMS_APP_UPDATE_TIME":"2024-11-05T12:19:15.3648297+00:00"}

To Reproduce
Steps to reproduce the behavior:
Create a new declarative agent according to the documentation here https://learn.microsoft.com/en-us/microsoft-365-copilot/extensibility/build-declarative-agents?tabs=ttk&tutorial-step=1

1. Go to 'Teams Toolkit' in Visual Studio Code
2. Click on 'Provision'
3. See the error above in the output

Expected behavior
The provisioning should run and the declarative agent should be accessible in https://www.office.com/chat?auth=2

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

• OS: Windows 10
• Version Teams Toolkit: v5.10.0

Additional context
Please see the complete provisioning output here:

[2024-11-05T12:11:58.920Z] [Info] - Current VS Code locale is: en-us
[2024-11-05T12:11:59.209Z] [Info] - Teams Toolkit extension is now active!
[2024-11-05T12:12:03.962Z] [Info] - Executing provision 

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

[2024-11-05T12:12:03.963Z] [Info] - Executing lifecycle provision
[2024-11-05T12:12:04.782Z] [Info] - (√)Done: Teams Package c:\Users\benedikt.eger\OneDrive - UDG United Digital Group\Documents\Projects\Bruker\Code\declarative-agent\appPackage\build\appPackage.dev.zip built successfully!
[2024-11-05T12:12:05.151Z] [Info] - 
Teams Toolkit has checked against all validation rules:

Summary:
51 passed.



A complete log of validations can be found in c:\Users\benedikt.eger\AppData\Roaming\Code\logs\20241105T131153\window1\exthost\TeamsDevApp.ms-teams-vscode-extension\20241105T121158.log
[2024-11-05T12:12:12.619Z] [Error] - Unable to execute action teamsApp/extendToM365. Error message: undefined
[2024-11-05T12:12:12.623Z] [Error] - Failed to Execute lifecycle provision due to failed action: teamsApp/extendToM365. iwt:Request failed with status code 404 (tracingId: 00-2d0852a5d0ef94cb0d75e90f3588bb8e-d7ed1145dcd3a21d-00) :  . Env output: {"TEAMS_APP_ID":"1afe74a9-ad74-451c-8cbe-86a74c1eee71","TEAMS_APP_TENANT_ID":"6ffe90e7-2d89-47e6-97bf-c03294cf3e63","TEAMS_APP_UPDATE_TIME":"2024-11-05T12:12:08.6818283+00:00"}
[2024-11-05T12:12:12.626Z] [Info] - Execution summary:

Summary:
(×) Error: Lifecycle stage provision failed.
  (√) Done: teamsApp/create was executed successfully.
    (√) Done: Teams app with id 1afe74a9-ad74-451c-8cbe-86a74c1eee71 already exists, skipped creating a new Teams app.
  (√) Done: teamsApp/zipAppPackage was executed successfully.
  (√) Done: teamsApp/validateAppPackage was executed successfully.
  (√) Done: teamsApp/update was executed successfully.
    (√) Done: Teams app 1afe74a9-ad74-451c-8cbe-86a74c1eee71 updated successfully
  (×) Error: teamsApp/extendToM365 failed.
    (×) Error: Request failed with status code 404 (tracingId: 00-2d0852a5d0ef94cb0d75e90f3588bb8e-d7ed1145dcd3a21d-00) :  

[microsoft-github-policy-service]

Thank you for contacting us! Any issue or feedback from you is quite important to us. We will do our best to fully respond to your issue as soon as possible. Sometimes additional investigations may be needed, we will usually get back to you within 2 days by adding comments to this issue. Please stay tuned.

[benedikt-udg]

As a side note: I hat this setup working yesterday without problems - and on my side nothing has changed between yesterday and today.

[benedikt-udg]

Sorry - I just saw the issue is already being discussed in #12652

[swatiarora11]

@benedikt-udg is it resolved?
Has anyone checked

[benedikt-udg]

@swatiarora11 In part: the error message still appears and apparently there is still work to be done on MS side, but the provisioning works despite the error message.

[swatiarora11]

How is provisioning works for you?, Suggest if you have workaround, for me it's still broken on local

[benedikt-udg]

I'm not doing anything special: just clicking the "Provision" button. It still shows the error message, but my agent gets updated anyway.