Forum Discussion

NickKearns's avatar
NickKearns
Tin Contributor
Aug 27, 2026

New Copilot Studio experience - MS365 Copilot and Teams - Channel About Info

We have imported a managed Solution into our Production Environment and all Objects successfully migrated, with the exception of the Channel 'About Info'. We find we can now update these About Info details, but they do not carry through into the App Manifest Download or the Submit to Org Catalogue. Unlike the Classic experience, there is also nowhere to update the Icon in the Channel Details, so only the default icon comes through in the Manifest and Org Catalogue workflow. HELP!

1 Reply

  • Hello,

    I agree. In the new Copilot Studio experience, some behaviors may differ from the classic experience, and inconsistencies or bugs may still be encountered in certain scenarios...

    I can't find any information stating that the channel's "About Info" settings are supported as part of the ALM lifecycle for managed solutions in the new Copilot Studio experience.

    I would suggest the following checks:

    • Open the "Teams and Microsoft 365 Copilot" channel in the production environment and use "Edit details" to re-enter the name, descriptions, and metadata before republishing the agent.
    • Republish the agent after each change.  The publishing information populates the Teams and Microsoft 365 catalog entries.
    • Allow up to 24 hours after publishing to validate icon and branding changes, as Microsoft documents a propagation delay of up to 24 hours.
    • Download the generated ZIP package and verify the manifest contents as well as the color.png and outline.png files. 
    • If the generated icon remains the default icon, try updating the icon in the agent details and then republish.
    • As a last resort, manually modify the manifest and icon files within the ZIP package before submitting it to the organizational catalog.

    If the "About Info" fields and icon are still not reflected in the exported manifest after these steps, I would consider this an undocumented behavior and recommend opening a Microsoft Support ticket with :

    • The environment ID
    • The solution ID
    • A comparison between the source and production environments
    • The exported manifest before and after the import process.

    Hope this helps. Let me know if you find a solution.