Bug Report
Lab: Application Lifecycle Management (ALM) in Copilot Studio (mcs-alm)
Use case / step number: Use Case #3: Create Power Platform Pipelines for Deployment
What happened:
I created a solution named “UserJHLUUS5Q‑Training Workshop Agents” and set it as the preferred solution (Use Case #1). I then configured the required environment variable and connection reference within that solution (Use Case #2). Finally, I described and provisioned the agent as outlined in Use Case #3. After the agent was successfully provisioned, the agent (Microsoft Surface Guide) did not appear in the preferred solution (UserJHLUUS5Q‑Training Workshop Agents). Instead, the agent was created in and is only visible within the Default solution.
What I expected:
The provisioned agent, Microsoft Surface Guide Agent should be created and associated with the preferred solution that was active at the time of agent creation.
Screenshots:
Browser / environment:
Chrome
Bug Report
Lab: Application Lifecycle Management (ALM) in Copilot Studio (
mcs-alm)Use case / step number: Use Case #3: Create Power Platform Pipelines for Deployment
What happened:
I created a solution named “UserJHLUUS5Q‑Training Workshop Agents” and set it as the preferred solution (Use Case #1). I then configured the required environment variable and connection reference within that solution (Use Case #2). Finally, I described and provisioned the agent as outlined in Use Case #3. After the agent was successfully provisioned, the agent (Microsoft Surface Guide) did not appear in the preferred solution (UserJHLUUS5Q‑Training Workshop Agents). Instead, the agent was created in and is only visible within the Default solution.
What I expected:
The provisioned agent, Microsoft Surface Guide Agent should be created and associated with the preferred solution that was active at the time of agent creation.
Screenshots:
Browser / environment:
Chrome