microsoft / microsoft/CopilotStudioSamples

Request: Unmanaged version of MCSResponsesAnalyzer solution

Open
#437 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
797
Forks
491
PR merge metrics
No merged PRs in 30d

Description

Is your feature request related to a problem? Please describe.

The FeedbackAnalyzer sample currently provides the solution package only as a managed solution:

  • MCSResponsesAnalyzer_2_0_0_2_managed.zip

Because the solution is managed, it cannot be customized, extended, or debugged in development environments. This limits our ability to adapt the sample for:

  • Real-world scenarios
  • Environment-specific changes
  • Standard ALM workflows

Describe the solution you'd like

Please provide an unmanaged version of the MCSResponsesAnalyzer solution alongside the managed package in the repository.

An unmanaged solution would allow developers to:

  • Inspect and customize Dataverse components
  • Modify or extend Power Automate flows
  • Debug and adapt the solution for different Copilot Studio environments
  • Follow standard ALM best practices (dev → test → prod)

Describe alternatives you've considered
  • Manually recreating the solution components in an unmanaged solution, which is time-consuming and error-prone
  • Attempting to extract components from the managed solution, which is not supported and not recommended

Neither approach is ideal compared to having an official unmanaged package.


Additional context

This repository is intended as a sample and learning resource. Providing both managed and unmanaged versions would greatly help teams who want to:

  • Learn from the solution
  • Customize it
  • Extend the Feedback Analyzer for their own Copilot Studio implementations

Thank you for maintaining and sharing these valuable Copilot Studio samples.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating MCSResponsesAnalyzer_2_0_0_2_managed.zip and the FeedbackAnalyzer solution packaging process in the repository. Add the corresponding unmanaged package alongside it, then verify that both packages are present and usable for the development and customization workflow described.

Written by the indexing model from the issue text.

Assessment

Domain
cloud, release
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.