Mansi Pednekar

Current behavior: When an environment is created in Power Platform Admin Center, the environment is created with URL consisting crm. For eg. https://domainname.crm.dynamis.com

Ask: When an environment is created in Power Platform Admin Center, the URL of the created environment should not consists of crm as it creates a confusion for end users.

Current behavior:

-Additional storage is required for each language you use. Not using a specific language doesn't uninstall the language or reduce the storage requirement. 

-Storage capacity is purchased by customer for storing data and records in CRM however due to this language packs installation, the storage is occupied by language packs which is provided by Microsoft for providing CRM users to use CRM environment in different languages.

-Therefore, the more language pack customer will install, the more storage capacity it would consumed leading to which customer has to purchase more storage capacity which is not convenient.

-There is an option to disable/remove language packs which are not required however it is not feasible solution for customers who have users across globe and therefore need different language packs to be installed.

Expect behavior:

Installation of language packs should not contribute to storage capacity which will help the customer to utilize the purchased storage capacity to store their records and data in CRM environment (not for something like language packs which is provided by Microsoft to improve utilization of CRM)

Actual Behavior: As per the current product design, Microsoft Entra group membership maintenance done on the team member in Microsoft Entra ID will not be reflected until the next time the team member logs in or when the system refreshes the cache (after 8 hours of continuous log-in).

Expected behavior:  Microsoft Entra group membership maintenance done on the team member in Microsoft Entra ID should be reflected immediately without the need for the team member to log in to environment or wait for the system to refresh the cache.

Actual Behavior: As per the current design/product behavior, it is not possible to throw the exceptions/errors for CRUD operations triggering the MS Odata plugins.

Expected Behavior: Need to change the product behavior to get exceptions/errors for CRUD operations triggering the MS Odata plugins.

Current behavior: It is possible to disable/enable co-pilot feature at the form level and app level.

Expected behavior: It should be possible and allowed to disable/enable co-pilot feature at the environment level.