teamsApp/extendToM365 failed. Request failed with status code 404 when Provision a Declarative Agent template

[therealjohn]

Describe the bug

To Reproduce
Steps to reproduce the behavior:

1. Create a Declarative Agent in VS Code
2. Select Provision

Expected behavior
It should run all the steps OK.

Screenshots
It does not. See screenshot above. It errors on teamsApp/extendToM365

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

• OS: Windows
• Version 5.10

Additional context
CLI 3.0.4 works OK for the same project.

[nicodecleyre]

Same issue here, occurs suddenly.. Couple of days ago it still worked. removed the values in .env.dev & removed the file .env.dev.user & removed everything in appPackage\build

[MrKSchmitz]

Yeah, can no longer debug local builds using the Teams toolkit.
Last update for the toolkit was 2 weeks ago (5.10.0), and I've tried multiple tenants. Likely something is busted service-side.
Was working fine yesterday.

[BobGerman]

Thanks @MrKSchmitz - it worked earlier today for me and then at around 10 or 11am Eastern it stopped working on all my projects. It has to be in the services somewhere because I did not change the TTK VSC extension between it working and not working.

Trying to lock the Ignite labs so we can teach attendees how to build DA's with TTK - Thanks!

[MrKSchmitz]

There's an older post here with the same/similar issue:
#11904

If you don't need the app in the Outlook or Microsoft 365 app you can comment out the "teamsApp/extendToM365" step in the yaml file for a quick temp fix.

[huimiu]

Hi all, we're looking into the cause of this error. Could you please let me know if it's still an issue? Or is it now successfully provisioned?

[huimiu]

There's an older post here with the same/similar issue: #11904

If you don't need the app in the Outlook or Microsoft 365 app you can comment out the "teamsApp/extendToM365" step in the yaml file for a quick temp fix.

The "teamsApp/extendToM365" step is a necessary step for sideloading your declarative agent.

[MrKSchmitz]

Hi all, we're looking into the cause of this error. Could you please let me know if it's still an issue? Or is it now successfully provisioned?

Looks like it working now, I did have to log out & then in again, but seems to be working as expected

[MrKSchmitz]

broken again

[huimiu]

Thanks for your feedback. We've already raised the priority of this issue, and I'll keep you updated with any progress

[nixon-ui]

@huimiu Please do as soon as possible. 😢

[swatiarora11]

@huimiu please confirm once done, waiting for your update

[huimiu]

The issue has been identified, the service-side fix is complete, and it's currently being deployed. I'm confirming when the deployment will be finished

[huimiu]

Update: Although this error occurred, your agent has actually been provisioned successfully. You can go ahead and test it. The server-side fix will be fully deployed tomorrow morning PST.

[BobGerman]

Still happening for me - blocked in preparing and testing labs for Ignite which is <2 weeks away!

[BobGerman]

Can this stay open until it is fixed for people outside the engineering team? Thanks! @therealjohn @MrKSchmitz

[doaaeltahan15]

Hello, still facing the same error. it seems the agent was deployed but not acting as expected.

[Billbrockbank]

I did a test on a computer before updating to Teams Toolkit in VS Code.
The deployment was completed with the error but after the update to Teams Toolkit v5.10.0, the error started to appear on deployment.

[premkaretimsft]

I'm facing the same issue and I can't disable this step in the yaml as the app won't sideload into the Teams client without this step.

[therealjohn]

The service issue has been resolved and rolled out. You should be able to successfully run these steps now.

[nicodecleyre]

The service issue has been resolved and rolled out. You should be able to successfully run these steps now.

Can confirm, app provisions without errors now. Thank you everyone 🙏