Lab 04 - Use Your Own Data - Deployment Failure

[SkillableKA]

Lab 04 - Create a custom copilot that uses your own data
Task - Deploy the flow
Step 2 - Create a deployment with the following settings:

We have users reporting being unable to deploy the flow as instructed. I have been able to reproduce this issue multiple times and have been unable to determine the root cause or find a successful work around. Every step works as instructed until you attempt to deploy the flow. I have attempted to change the VMsize to a few different available SKUs with no success.

[afelix-95]

I wasn't able to reproduce the error. However, I was not able to deploy the prompt flow in VM environment either. The creation process concludes without any error notifications but the endpoint and deployment don't show up in the deployments page even after 30-40min waiting. Outside of VM environment the deployment succeeds without any issues in 5-10min.

[ivorb]

Thanks @afelix-95. @SkillableKA what would be limiting the VM but not the same outside - are you changing anything from the instructions as is in this repo?

[SkillableKA]

@ivorb Thank you for the quick response. We are not changing anything on our platform, and pulling directly from the repo. We will continue looking into the issue on our side.

[SDSTony]

FYI, it also gave me an error when I tried it on outside of the VM environment, on my own tenant. However, I was able to troubleshoot it by deleting the endpoint and then deploying the prompt flow again.

[ivorb]

@afelix-95 will you run this again when you have time, now that updates from Ignite have settled down?

[afelix-95]

@ivorb I've tested it once more both with my own tenant and in the VM environment. Again, with my own tenant I could deploy the prompt flow without issue, only needed to change the instance count from 3 to 2 due to quota limitations. In the VM environment I couldn't create the endpoint, receiving the following error:

Since there is no information on which resource provider is not registered, I couldn't manually fix it.