Kevin Duong

In an environment of type "Microsoft Teams", auditing should be enabled to enhance security without the need to upgrade to Dataverse database.

When using the API call to "/api/data/v9.0/organizations", the value for "auditretentionperiod" does not reflect the audit retention period setting in admin center. However, the value is updated correctly for "auditretentionperiodv2", which can cause confusion to customers. The "auditretentionperiod" attribute should be removed to avoid confusion.

When users design a journey, if it is complex enough, there will be an error when publishing it: "Journey could not be published due to too many actions being present exceeding '500'". It's frustrating as a user to build a journey and have the system say it’s too complex.

It would be great if the limit can be increased, or the journey can be optimized so that it generates less actions.

Currently, there is no way for agents to directly take over bot conversations. They have to configure a topic with Copilot so that it can help transfer case from bot to agents, but this is a workaround.

It would be great if this feature is implemented to help with customer's operations.

Currently, when a topic/purpose checkbox is unchecked, it will be taken into account by default when submitting the form. It would be nice to have an additional option to set the desired behavior when a checkbox is unchecked, so that customers can make the form ignores the unchecked checkbox for example.

Currently, it is possible for personalization, journey, and segment. However, this is not applicable for trig yet.

It would be helpful for users if this can be applied to trig as well.

Currently, FLS override is possible for personalization, journey, and segment. However, this is not applicable for triggers yet.

It would be helpful for users if this can be applied to triggers as well.