web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Microsoft Dynamics 365 | Integration, Dataverse...
Answered

CoPilot features added without update

(1) ShareShare
ReportReport
Posted on by 4
Hi, I have updated our production environment with a custom code package however, looking at features, there have been a load of AI/Copilot features added at the same time. We have not taken a QU or PU, just a custom code package. There is nothing in LCS environment history to suggest anything has been pushed to production by MS either. I did notice our Pre-Production environment had a QU that contained these features and, that is the environment we use to deploy the production build package to and mark as release candidate. Could these features have been deployed to production as part of the code package as they existed in the pre-production environment?
I have the same question (0)
  • Anthony Blake Profile Picture
    3,158 Super User 2026 Season 1 on at
    Hi, 
     
    They were added on the  latest proactive quality update and are on by default. I don't think that you are the first person to question that decision, it has been quite contentious.
     
    I wrote about how to turn off/manage all the summary features which have been added for summaries here:
     
     
    This way you can introduce them to your users in a more controlled manner (Test/Pre-Prod/etc).
     
    I expect these will become always-on at some point, so i wouldn't just turn off the features and forget about them, but maybe introduce them in a gentler way.
     
    Anthony
     
  • Verified answer
    Anthony Blake Profile Picture
    3,158 Super User 2026 Season 1 on at
    Just a little extra on your update of production and how the PQU made it in - you cannot just update a code package in production. You select a source environment and everything comes over to production from that source (e.g. pre-prod), including Service updates and PQUs. When scheduling an update the destination version numbers after update are displayed.
     
    I expect your source environment had already had the PQU applied automatically, and then you updated production from there, bringing it up to the same version.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Meet the Microsoft Dynamics 365 Contact Center Champions

We are thrilled to have these Champions in our Community!

Congratulations to the March Top 10 Community Leaders

These are the community rock stars!

Leaderboard > Microsoft Dynamics 365 | Integration, Dataverse, and general topics

#1
11manish Profile Picture

11manish 154

#2
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 73 Super User 2026 Season 1

#3
ManoVerse Profile Picture

ManoVerse 55 Super User 2026 Season 1

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans