Teodor Raychev

In our experience there were multiple Features (marked as non-mandatory) enabled automatically after an Environment (Microsoft) Update. After further investigation and support from Microsoft, we were advised that these Features were enabled automatically in relation to Copilot. In other words, in order for Copilot to work as expected, these Features needed to be enabled.

As end-customer had not given their consent, nor were features marked as Mandatory - we were all very surprised how this happened. What we understood from Microsoft Support was that the Product Group manages how the Features for Copilot are enabled and it's not decided by end-customer.

In our experience the Features were enabled after a Proactive Quality Update, they did not cause any issues (at least to our knowledge). However in the same period we had a huge Performance degradation, probably not related to enabled Features, however we were non the less very surprised and at the time we looked at this as a root cause for the performance issues.

Our concern is that by this logic, we can get a lot of features enabled by default after an Update, without them being marked as Mandatory and we believe that this will cause a lot of confusion, the least.

Since (in our case) the features were linked and are required for Copilot - would it be possible to mark these Features as "Mandatory for Copilot" for example, or mandatory for anything else that requires the feature as a prerequisite.

Or, at least add these details in the Update release notes - this way, it's clear and customers are notified of this.