Merge pull request #8807 from MicrosoftDocs/main

Auto push to live 2025-04-25 18:06:56

Author: Deland-Han

support/azure/azure-storage/files/file-sync/file-sync-troubleshoot-cloud-tiering.md

@@ -151,6 +151,7 @@ If content doesn't exist for the error code, follow the general troubleshooting
 | 0x8002802b | -2147319765 | TYPE_E_ELEMENTNOTFOUND | An unexpected error occurred. | No action required. This error should automatically resolve. If the error persists for several days, create a support request. |
 | 0x80072f00 | -2147012864 | WININET_E_FORCE_RETRY | A connection with the service could not be established. | No action required. This error should automatically resolve. If the error persists for several days, create a support request. |
 | 0x80C86093 | -2134351785 | ECS_E_STABLEVERSION_SVID_CHECK_<br/>FAILED | The file can't be tiered due to a known issue. | No action required. Ignore the error and it will no longer appear once a fix is released. |
+| 0x80c83099 | -2134364007 | ECS_E_PRIVATE_ENDPOINT_ACCESS_<br/>BLOCKED | Private endpoint configuration access blocked. | Check the private endpoint configuration and allow access to the Azure File Sync service. [Learn more](/azure/storage/file-sync/file-sync-firewall-and-proxy#test-network-connectivity-to-service-endpoints). |
 
 ## How to troubleshoot files that fail to be recalled
 

support/dynamics-365/customer-service/core-service-scheduling/book-button-not-available-for-service-activity.md

@@ -0,0 +1,42 @@
+---
+title: Service Activity Not Visible and Missing Book Button
+description: Solves an issue where the Book button isn't available for service activities and service activities don't appear under Unscheduled Service Activities in Microsoft Dynamics 365 Customer Service.
+ms.reviewer: ghoshsoham
+author: Yerragovula
+ms.author: srreddy
+ai-usage: ai-assisted
+ms.date: 04/24/2025
+ms.custom: sap:Core Service Scheduling, DFM
+---
+# Book button isn't available for service activity and Unscheduled Service Activities doesn't show service activities
+
+This article provides guidance on resolving the issue where the **Book** button isn't available for service activities, and service activities don't appear under the **Unscheduled Service Activities** view in the schedule board in Dynamics 365 Customer Service.
+
+## Symptoms
+
+You might encounter the following issues in Dynamics 365 Customer Service:
+
+- The **Book** button is missing for [service activities](/dynamics365/customer-service/use/schedule-service-activity-csh).
+- Service activities aren't visible under the **Unscheduled Service Activities** view in the [schedule board](/dynamics365/customer-service/use/use-schedule-board-configure-service-activity).
+
+## Cause
+
+This issue might occur due to one of the following reasons:
+
+- The entity isn't enabled in the **Resource Scheduling** settings.
+- Post-import code fails to execute properly for service scheduling upon import. This code is essential for scheduling and establishing relationships.
+
+## Resolution
+
+To resolve the issue:
+
+1. Open the **Resource Scheduling** app in Dynamics 365.
+2. Select **Settings** in the navigation area.
+3. Select **Administration** from the site map.
+4. Select **Enable Resource Scheduling for Entities**.
+5. Verify if the relevant [entity](/dynamics365/customer-service/administer/scheduling.entities#understand-scheduling-entities) is enabled. If it isn't enabled, enable the entity and publish the changes.
+
+The issue might persist because post-import code fails to execute properly. To solve this issue:
+
+1. Check for available updates for the Dynamics 365 Service Scheduling solution.
+2. Apply the updates as per the instructions provided. For more information, see [Manage Dynamics 365 apps that run on Microsoft Dataverse](/power-platform/admin/manage-apps).

support/dynamics-365/customer-service/customer-service-admin-center/cant-install-dynamics-365-customer-service-apps-in-existing-environment.md

@@ -0,0 +1,69 @@
+---
+title: Can't Install Customer Service Apps in Existing Environment
+description: Solves an issue where users can't install Dynamics 365 Customer Service applications in an existing Power Platform environment.
+ms.reviewer: ghoshsoham
+author: Yerragovula
+ms.author: srreddy
+ai-usage: ai-assisted
+ms.date: 04/24/2025
+ms.custom: sap:Core Service Scheduling, DFM
+---
+# Can't install Dynamics 365 Customer Service applications in an existing Power Platform environment
+
+This article provides guidance for users who encounter issues when trying to install Dynamics 365 Customer Service applications, such as the Customer Service workspace and Customer Service admin center model-driven apps, in an existing Power Platform environment.
+
+## Symptoms
+
+Users can't install Dynamics 365 Customer Service applications in an existing Power Platform environment, such as the [Customer Service workspace](/dynamics365/customer-service/implement/csw-overview?tabs=customerserviceadmincenter) and the [Copilot Service admin center (previously known as Customer Service admin center)](/dynamics365/customer-service/implement/cs-admin-center) model-driven applications.
+
+This issue occurs due to one or more of the following reasons:
+
+## Cause 1: The environment is Dataverse-only
+
+- The environment is created as a Dataverse-only environment without enabling Dynamics 365 apps.
+- Dynamics 365 applications, such as Customer Service workspace, require the environment to be created with the **Enable Dynamics 365 apps** option selected during the environment setup.
+- The **Enable Dynamics 365 apps** option allows the environment to host first-party applications such as Dynamics 365 Sales, Dynamics 365 Customer Service, and Dynamics 365 Marketing.
+
+### Resolution
+
+1. Navigate to the [Power Platform admin center](https://admin.powerplatform.microsoft.com/).
+
+2. Select the environment where you are trying to install the applications.
+
+3. Go to **Settings** > **Overview**, and verify whether the environment is listed as **Dataverse-only** or if Dynamics 365 apps are enabled.
+
+4. If the **Enable Dynamics 365 apps** option isn't enabled, it means that the database is provisioned as **Dataverse-only** and you can't install Dynamics 365 apps in this environment.
+
+5. In this case, follow these steps to create a new environment with Dynamics 365 apps enabled:
+
+   1. Navigate to the [Power Platform admin center](https://admin.powerplatform.microsoft.com/).
+   2. Select **+ New environment**.
+   3. Provide a name and select a region for the new environment.
+   4. Under **Type**, select **Production** or **Sandbox** as required.
+   5. Enable Dataverse by selecting the appropriate box.
+   6. Enable Dynamics 365 apps by selecting the **Enable Dynamics 365 apps** checkbox.
+   7. Select **Save** and wait for the provisioning process to complete.
+
+Once the environment is successfully set up, the [Customer Service Hub](/dynamics365/customer-service/implement/customer-service-hub-user-guide-basics) and Copilot Service admin center applications are available in the app list for users with the appropriate licenses.
+
+## Cause 2: Missing or incorrect licensing
+
+Users trying to install or access Dynamics 365 applications must have the [appropriate license](https://www.microsoft.com/dynamics-365/products/customer-service/pricing) assigned.
+
+### Resolution
+
+1. Go to the [Microsoft 365 admin center](https://admin.microsoft.com/).
+2. Select **Users** > **Active users**.
+3. Locate and select the user who needs access to the Customer Service applications.
+
+4. Select **Licenses and apps**, and ensure the user has one of the following licenses assigned:
+
+    - Customer Service Professional
+    - Customer Service Enterprise
+    - Customer Service Premium
+
+5. Save the changes.
+
+## More information
+
+For more detailed guidance on creating and managing environments, see [Create and manage environments in the Power Platform admin center](/power-platform/admin/create-environment).

support/dynamics-365/customer-service/omnichannel-for-customer-service/agents-dont-receive-desktop-notifications-for-new-messages.md

@@ -0,0 +1,40 @@
+---
+title: Agents Don't Receive Desktop Notifications for New Messages
+description: Solves an issue where agents don't receive desktop notifications for new session messages when the browser isn't active in Microsoft Dynamics 365 Contact Center and Dynamics 365 Customer Service.
+author: Yerragovula
+ms.author: srreddy
+ms.reviewer: courtser
+ai-usage: ai-assisted
+ms.date: 04/24/2025
+ms.custom: sap:Live chat Widget (LCW), DFM
+---
+# Agents don't receive desktop notifications for new session messages when the browser isn't active
+
+This article addresses an issue where agents don't receive notifications for newly assigned session messages when their browser page isn't actively viewed in Dynamics 365 Contact Center and Dynamics 365 Customer Service.
+
+## Symptoms
+
+Agents don't receive [notifications](/dynamics365/customer-service/administer/notification-templates#desktop-notifications) for new session messages when the browser is running in the background.
+
+## Cause
+
+This is the expected behavior when the system is configured to use default notification templates, which don't support desktop notifications when the application isn't actively in use.
+
+## Resolution
+
+To enable desktop notifications for agents when the browser isn't active, follow these steps:
+
+1. Create a new notification template:
+
+    - Navigate to the [notification settings](/dynamics365/customer-service/administer/notification-templates#create-a-notification-template) in the Dynamics 365 environment.
+    - Create a notification template named "When app is in the background."
+    - Enable the **Show Desktop Notification** setting for this template.
+
+    For more information, see [Use notifications in Dynamics 365 Customer Service](/dynamics365/customer-service/use/oc-notifications).
+
+2. Associate the newly created notification template with the appropriate workstream:
+
+    - Identify the workstream(s) that require the new notification template.
+    - Associate the "When app is in the background" notification template with the relevant workstream(s).
+
+    For step-by-step guidance, see [Associate notification templates with workstreams](/dynamics365/customer-service/administer/associate-templates).

support/dynamics-365/customer-service/queues/queue-email-address-not-resolving-correctly.md

@@ -0,0 +1,51 @@
+---
+title: Queue Email Address Is Unresolved or Unrecognized in the To Field
+description: Solves an issue where emails sent to a queue show the queue email address as unresolved or unrecognized in the To field in Microsoft Dynamics 365.
+author: Yerragovula
+ms.author: srreddy
+ms.reviewer: courtser
+ai-usage: ai-assisted
+ms.date: 04/24/2025
+ms.custom: sap:Queues, DFM
+---
+# Queue email address isn't resolved correctly in Dynamics 365
+
+This article addresses an issue in Dynamics 365 where emails sent to a queue show the queue email address as unresolved or unrecognized in the **To** field.
+
+## Symptoms
+
+When emails are sent to a [queue](/dynamics365/customer-service/administer/set-up-queues-manage-activities-cases) in Dynamics 365, the queue email address appears as unresolved or unrecognized in the **To** field. However, the system still processes the email and generates cases as expected.
+
+## Cause
+
+This issue occurs when multiple records within Dynamics 365 share the same email address. The system identifies multiple matches and might randomly resolve one of them. As a result, the email address appears as unresolved or unrecognized.
+
+## Resolution
+
+To resolve this issue, follow these steps:
+
+1. Use the following [Open Data Protocol (OData) query](/power-apps/developer/data-platform/webapi/query/overview) to find duplicate email addresses in the system. This query returns all records (queues, accounts, contacts, leads, or custom records) that share the same email address.
+
+    `https://contoso.api.crm.dynamics.com/api/data/v9.1/emailsearches?$filter=emailaddress eq 'email@example.com'`
+
+   > [!NOTE]
+   > Replace the organization URL and email address in the query to fit your environment.
+
+2. Remove or update duplicate email addresses:
+
+   1. Change the email addresses on duplicate records to ensure each email address is unique across all records.
+
+   2. After updating the email addresses, re-run the query and verify that duplicates no longer appear in the query result.
+
+      If duplicates persist in the query results, there might be a delay in the email search table refresh. Currently, there's no method to force an immediate refresh of the email search table.
+
+3. Adjust Dynamics 365 system settings:
+
+   1. Navigate to **Advanced Settings** > **Settings** > **Administration** > **Email** in Dynamics 365.
+
+   2. Locate the **Set To, cc, bcc fields as unresolved values if multiple matches are found in Incoming Emails** setting.
+
+   3. Set the setting to **No** to ensure the system correctly resolves email addresses when there's only one matching record.
+
+   > [!IMPORTANT]
+   > If the setting is set to **Yes**, the system doesn't resolve email addresses that have multiple matches. These email addresses appear marked in red, requiring you to manually resolve them to a specific record.

support/dynamics-365/customer-service/toc.yml

@@ -26,6 +26,14 @@
   items:
     - name: Troubleshoot issues using Solution Health Hub
       href: customer-service-insights/troubleshoot-cs-oc-solution-health.md 
+- name: Core Service Scheduling
+  items:
+    - name: Service activity not visible and missing the Book button
+      href: core-service-scheduling/book-button-not-available-for-service-activity.md
+- name: Customer Service Admin Center (CSAC)
+  items:
+    - name: Can't install applications in an existing environment
+      href: customer-service-admin-center/cant-install-dynamics-365-customer-service-apps-in-existing-environment.md
 - name: Email
   items: 
     - name: '"Case is missing customer" error'
@@ -59,7 +67,9 @@
 - name: Queues
   items:  
     - name: Personal view queue filters aren't working properly
-      href: queues/queue-filter-error.md                  
+      href: queues/queue-filter-error.md 
+    - name: Queue email address isn't resolved correctly
+      href: queues/queue-email-address-not-resolving-correctly.md               
 - name: Service Level Agreements (SLAs)
   items:
     - name: Import, export, or upgrade SLA
@@ -190,6 +200,8 @@
           href: omnichannel-for-customer-service/error-create-chat-widget-social-channel.md
     - name: Live Chat Widget (LCW)
       items:
+        - name: Agents don't receive desktop notifications for new session messages
+          href: omnichannel-for-customer-service/agents-dont-receive-desktop-notifications-for-new-messages.md
         - name: Chat widget icon doesn't load on portal
           href: omnichannel-for-customer-service/chat-widget-icon-does-not-load-portal.md
         - name: Chat widget doesn't load on the portal

support/power-platform/dataverse/tables-fields-and-relationships/string-or-binary-data-would-be-truncated-error.md

@@ -0,0 +1,43 @@
+---
+title: String or Binary Data Would Be Truncated Error
+description: Solves an issue where you can't delete records from a custom table in Microsoft Dynamics 365 Customer Service.
+author: Yerragovula
+ms.author: srreddy
+ms.reviewer: courtser
+ai-usage: ai-assisted
+ms.date: 04/24/2025
+ms.custom: sap:Tables, Fields and Relationships, DFM
+---
+# "String or binary data would be truncated" error when deleting records from a custom table
+
+This article provides guidance on resolving an error that occurs when you try to delete records from a custom table in Dynamics 365 Customer Service.
+
+## Symptoms
+
+When you try to delete records from a [custom table](/power-apps/maker/data-platform/create-custom-entity), you receive the following error message:
+
+> String or binary data would be truncated.
+
+The error message usually specifies the table and [column](/power-apps/maker/data-platform/types-of-fields) that cause the truncation error.
+
+## Cause
+
+The issue occurs because the data in one or more columns exceeds the maximum allowed character limit for those columns. Specifically, the data length in the affected column(s) is larger than the defined maximum character count.
+
+## Resolution
+
+To resolve this issue, follow these steps:
+
+1. [Select your environment in Power Apps](/power-apps/maker/canvas-apps/sign-in-to-power-apps#choose-an-environment).
+2. In the left navigation, select **Tables**, and then select the table where the error occurs.
+3. Select **Columns**, and locate the problematic column.
+4. Expand **Advanced options** for the selected column.
+
+   > [!TIP]
+   > You can also find the **Advanced options** in the [table designer](/power-apps/maker/data-platform/create-edit-entities-portal?tabs=excel#table-designer).
+
+5. Increase the **Maximum character count** to accommodate the data length.
+6. Save and publish the changes.
+7. After updating the maximum character count, proceed to delete the records again.
+
+If increasing the maximum character count doesn't solve the issue, you can try truncating the data in the column before deleting the records.

support/power-platform/dataverse/toc.yml

@@ -180,6 +180,10 @@
   items:
     - name: Dataverse plug-ins
       href: plug-in-execution/dataverse-plug-ins-errors.md
+- name: Tables, Fields and Relationships
+  items:
+    - name: '"String or binary data would be truncated" error'
+      href: tables-fields-and-relationships/string-or-binary-data-would-be-truncated-error.md
 - name: User permissions
   items:
     - name: Clean up inherited access