Merge pull request #8605 from MicrosoftDocs/main

Auto push to live 2025-03-31 02:00:02

Author: Deland-Han

support/azure/.openpublishing.redirection.azure.json

@@ -6300,6 +6300,10 @@
         "source_path": "virtual-machines/linux/linux-vm-no-boot-hyper-v-driver-issues.md",
         "redirect_url": "/troubleshoot/azure/virtual-machines/linux/troubleshoot-lis-driver-issues-on-linux-vms"
       },
+      {
+        "source_path": "azure-kubernetes/create-upgrade-delete/error-code-reservedresourcename.md",
+        "redirect_url": "/troubleshoot/azure/azure-kubernetes/create-upgrade-delete/error-code-invalidparameter"
+      },
       {
         "source_path": "azure-kubernetes/create-upgrade-delete/error-using-feature-requiring-virtual-machine-scale-set.md",
         "redirect_url": "/troubleshoot/azure/azure-kubernetes/welcome-azure-kubernetes"

support/azure/azure-kubernetes/connectivity/errors-arfter-restricting-egress-traffic.md

@@ -1,8 +1,8 @@
 ---
 title: Errors after restricting egress traffic
 description: Troubleshoot errors that occur after you restrict egress traffic from an Azure Kubernetes Service (AKS) cluster.
-ms.date: 11/12/2024
-ms.reviewer: chiragpa, nickoman, v-leedennis
+ms.date: 03/20/2025
+ms.reviewer: chiragpa, nickoman, jaewonpark, v-leedennis
 ms.service: azure-kubernetes-service
 keywords:
 #Customer intent: As an Azure Kubernetes user, I want to troubleshoot errors that occur after I restrict egress traffic so that I can access my AKS cluster successfully.
@@ -18,19 +18,21 @@ Certain commands of the [kubectl](https://kubernetes.io/docs/reference/kubectl/)
 
 ## Cause
 
-When you restrict egress traffic from an AKS cluster, your settings must comply with [required Outbound network and FQDN rules for AKS clusters](/azure/aks/outbound-rules-control-egress). If your settings are in conflict with any of these rules, the symptoms of egress traffic restriction issues occur.
+When you restrict egress traffic from an AKS cluster, your settings must comply with required Outbound network and FQDN (fully qualified domain names) rules for AKS clusters. If your settings are in conflict with any of these rules, the egress traffic restriction issues occur.
 
 ## Solution
 
-Verify that your configuration doesn't conflict with any of the [required Outbound network and FQDN rules for AKS clusters](/azure/aks/outbound-rules-control-egress) for the following items:
+Verify that your configuration doesn't conflict with any of the [required Outbound network and FQDN (fully qualified domain names) rules for AKS clusters](/azure/aks/outbound-rules-control-egress) for the following items:
 
 - Outbound ports
 - Network rules
-- Fully qualified domain names (FQDNs)
+- FQDNs
 - Application rules
 
+Check for conflicts with the rules that might occur in the NSG (network security group), firewall, or appliance that AKS traffic passes through according to the configuration.
+
 > [!NOTE]
-> The AKS outbound dependencies are almost entirely defined by using FQDNs. These FQDNs don't have static addresses behind them. The lack of static addresses means that you can't use network security groups (NSGs) to restrict outbound traffic from an AKS cluster.
+> The AKS outbound dependencies are almost entirely defined by using FQDNs. These FQDNs don't have static addresses behind them. The lack of static addresses means that you can't use NSGs to restrict outbound traffic from an AKS cluster. Additionally, scenarios that allow only IPs that are obtained from required FQDNs after all deny in NSG are not enough to restrict outbound traffic. Because the IPs are not static, issues might occur later.
 
 ## More information
 

support/azure/azure-kubernetes/create-upgrade-delete/error-code-reservedresourcename.md

@@ -33,8 +33,6 @@
       href: create-upgrade-delete/error-code-outboundconnfailvmextensionerror.md
     - name: RequestDisallowedByPolicy error
       href: create-upgrade-delete/error-code-requestdisallowedbypolicy.md
-    - name: ReservedResourceName error
-      href: create-upgrade-delete/error-code-reservedresourcename.md
     - name: ServicePrincipalValidationClientError error
       href: create-upgrade-delete/error-code-serviceprincipalvalidationclienterror.md
     - name: SubscriptionRequestsThrottled error (429)

support/azure/azure-kubernetes/toc.yml

@@ -0,0 +1,51 @@
+---
+title: Agent Capacity Issue in Customer Support Assignment
+description: Solves an issue where customer support representatives (CSRs) in Microsoft Dynamics 365 Customer Service receive fewer than the configured number of customers before their status automatically changes to Busy.
+author: Yerragovula
+ms.author: srreddy
+ai-usage: ai-assisted
+ms.date: 03/31/2025
+ms.reviewer: bavasude, srubinstein
+ms.custom: sap:Licensing, provisioning, and installation, DFM
+---
+# Agent capacity issue in customer support assignment
+
+This article addresses the issue where customer support representatives (CSRs) in Dynamics 365 Customer Service receive fewer than the configured number of customers before their status automatically changes to **Busy**.
+
+## Symptoms
+
+Customer support representatives (CSRs) are configured to handle a specific quota of customers (for example, five customers per CSR). However, their status changes to **Busy** after receiving fewer customers (for example, three customers), thereby preventing further customer assignments.
+
+## Cause
+
+This issue can occur due to the configuration of the workstream capacity units. Each customer case is assigned a specific number of capacity units, which determines how many customers an agent can handle simultaneously.
+
+For example, consider the scenario:
+
+- Each customer case is configured to consume 30 capacity units.
+- The total capacity assigned to the agent is 90 units.
+
+In this scenario, even though the agent may be configured to handle five customer cases, they can only handle three simultaneously due to the total capacity limit (3 cases × 30 units each = 90 units total.) Once this capacity is reached, the agent's status changes to **Busy**.
+
+## Resolution
+
+To resolve this issue, adjust the total capacity units assigned to the affected agents. This ensures that the agent can handle the intended number of customers simultaneously.
+
+1. Determine the required capacity:
+
+    - Identify the number of customers an agent is expected to handle (for example, five customers.)
+    - Determine the capacity units consumed by each customer case (for example, 30 units per case.)
+    - Calculate the total capacity needed for the agent: Required capacity = Number of customers × Capacity units per case. For example: For five customers, the required capacity = 5 × 30 = 150 units.
+
+2. Update the agent's capacity profile:
+
+    - Go to the Dynamics 365 Customer Service admin settings.
+    - Navigate to the capacity profiles for agents.
+    - Increase the total capacity units for the affected agents to the calculated value (for example, 150 units for five customers.)
+
+3. Save and test changes:
+
+    - Save the updated capacity profile.
+    - Test the configuration to ensure agents can now handle the desired number of customer cases without their status changing to **Busy**.
+
+For detailed instructions on managing capacity profiles, see [Create and manage capacity profiles](/dynamics365/customer-service/administer/capacity-profiles).

support/dynamics-365/customer-service/omnichannel-for-customer-service/agent-capacity-issue-in-customer-support-assignment.md

@@ -0,0 +1,37 @@
+---
+title: Troubleshoot Issues with Provisioning Channels
+description: Solves an issue where the Omnichannel Admin Center appears in read-only view and you can't manage or provision channels.
+author: Yerragovula
+ms.author: srreddy
+ai-usage: ai-assisted
+ms.date: 03/31/2025
+ms.reviewer: bavasude, srubinstein
+ms.custom: sap:Licensing, provisioning, and installation, DFM
+---
+# Can't provision channels in Omnichannel Admin Center
+
+This article provides guidance for resolving provisioning issues when the Omnichannel Admin Center application appears in read-only view.
+
+## Symptoms
+
+When you try to provision a channel in the Omnichannel Admin Center, you encounter the following issues:
+
+- The Omnichannel Admin Center appears in read-only view.
+- You can't manage or provision channels through the Omnichannel Admin center.
+
+## Cause
+
+The Omnichannel Admin center has been deprecated. All functionalities previously available in the Omnichannel Admin center have been integrated into the Customer Service admin center. For more information, see [Deprecations in Dynamics 365 Customer Service](/dynamics365/customer-service/implement/deprecations-customer-service#provisioning-of-omnichannel-for-customer-service-in-power-platform-admin-center-is-deprecated).
+
+## Resolution
+
+To successfully provision the chat (or other) channels, follow these steps:
+
+1. Navigate to your environment.
+2. Open the **Customer Service admin center** application.
+3. Go to **Channels** under **Customer Support**.
+4. Select **Manage** to configure the channels.
+5. Check the appropriate boxes to provision the channels that you want to use.
+6. Select **Save**.
+
+For more information, see [Provision channels in Dynamics 365 Contact Center](/dynamics365/contact-center/implement/provision-channels).

support/dynamics-365/customer-service/omnichannel-for-customer-service/channel-provisioning-in-omnichannel-admin-center.md

@@ -0,0 +1,35 @@
+---
+title: Chat Channel Provisioning Fails in Dynamics 365 Due To License Issue
+description: Solves an issue where the chat channel provisioning fails in Microsoft Dynamics 365 Customer Service due to a license issue.
+author: Yerragovula
+ms.author: srreddy
+ai-usage: ai-assisted
+ms.date: 03/31/2025
+ms.reviewer: bavasude, srubinstein
+ms.custom: sap:Licensing, provisioning, and installation, DFM
+---
+# Chat channel provisioning fails in Dynamics 365 due to license issue
+
+This article provides guidance to resolve the issue where the chat channel provisioning fails in Dynamics 365 Customer Service due to a license issue.
+
+## Symptoms
+
+When you try to provision a chat channel in Dynamics 365 Customer Service, the system reports that there's no license available. This occurs even though licenses have been purchased.
+
+## Cause
+
+The issue might occur if the required Microsoft Dynamics 365 Customer Service Enterprise or Dynamics 365 Customer Engagement Plan license isn't available or assigned.
+
+Licenses currently attached may be insufficient, such as basic or other messaging channel licenses, and don't include the necessary Customer Service Enterprise license required for provisioning the chat channel.
+
+## Resolution
+
+To resolve this issue, follow the steps below:
+
+1. Verify whether the Microsoft Dynamics 365 Customer Service Enterprise license or Dynamics 365 Customer Engagement Plan license is purchased and available in the tenant.
+
+2. Ensure the license is assigned to the appropriate users.
+
+3. Ensure the users have active subscription to the appropriate add-ons.
+
+To confirm the required licenses and provisioning prerequisites, see [Omnichannel for Customer Service system requirements](/dynamics365/customer-service/implement/system-requirements-omnichannel).

support/dynamics-365/customer-service/omnichannel-for-customer-service/chat-channel-provisioning-fails-in-due-to-license-issue.md

@@ -0,0 +1,49 @@
+---
+title: Contact Center Workspace not Visible
+description: Solves an issue where users are unable to see or access the Dynamics 365 Contact Center workspace.
+author: Yerragovula
+ms.author: srreddy
+ai-usage: ai-assisted
+ms.date: 03/31/2025
+ms.reviewer: bavasude, srubinstein
+ms.custom: sap:Licensing, provisioning, and installation, DFM
+---
+# Dynamics 365 Contact Center workspace isn't visible
+
+Users may encounter an issue where they're unable to see or access the Dynamics 365 Contact Center workspace, even though they have been assigned the appropriate licenses and roles. This article provides an explanation of the issue and steps to resolve it.
+
+## Symptoms
+
+Users with Dynamics 365 Contact Center licenses are unable to locate or access the Dynamics 365 Contact Center workspace within the system. And the workspace doesn't appear in the Dynamics 365 environment, despite license and role assignment.
+
+## Cause
+
+The Dynamics 365 Contact Center workspace and the Customer Service workspace can't be used simultaneously within the same Dynamics 365 organization. This limitation prevents the Contact Center workspace from being displayed if the Customer Service workspace is already in use.
+
+## Resolution
+
+> [!NOTE]
+> Existing organizations using the Customer Service workspace can't simultaneously display the Contact Center workspace. A separate environment is required to use the Contact Center workspace.
+
+To enable the Dynamics 365 Contact Center workspace, follow these steps:
+
+1. Create a new environment:
+
+    - Navigate to the [Power Platform admin center](https://admin.powerplatform.microsoft.com/).
+    - Select **Environments** on the left navigation pane.
+    - Select **+ New** to create a new environment.
+
+2. Deploy the Contact Center app:
+
+    - During the provisioning of the new environment, ensure that you select the **Contact Center** app for deployment.
+    - Complete the setup process as prompted.
+
+3. Switch to the new environment:
+
+    - Users who need access to the Dynamics 365 Contact Center workspace should switch to the newly created environment.
+    - Ensure that appropriate licenses and roles are assigned within this new environment.
+
+## More information
+
+- [Overview of Contact Center workspace](/dynamics365/contact-center/use/ccw-overview)
+- [Overview of the Customer Service workspace application for Dynamics 365 Customer Service](/dynamics365/customer-service/implement/csw-overview?tabs=customerserviceadmincenter)

support/dynamics-365/customer-service/omnichannel-for-customer-service/contact-center-workspace-not-visible.md

@@ -0,0 +1,58 @@
+---
+title: Resource Not Found Error When Configuring WhatsApp Channel
+description: Solves the Resource not found for the segment error when configuring the WhatsApp channel in Microsoft Dynamics 365 Customer Service or Dynamics 365 Contact Center.
+author: Yerragovula
+ms.author: srreddy
+ai-usage: ai-assisted
+ms.date: 03/31/2025
+ms.reviewer: parkmermel
+ms.custom: sap:WhatsApp via Twilio, DFM
+---
+# Resource not found error when configuring WhatsApp channel
+
+This article provides guidance on resolving the "A Resource not found for the segment 'msdyn\_UpdatePrivacyTerms'" error that may occur when you configure the WhatsApp channel in Dynamics 365 Customer Service or Dynamics 365 Contact Center.
+
+## Symptoms
+
+When you try to [configure the WhatsApp channel](/dynamics365/customer-service/administer/configure-whatsapp-channel) in Dynamics 365 Customer Service or Dynamics 365 Contact Center, you receive the following error message:
+
+> A Resource not found for the segment 'msdyn\_UpdatePrivacyTerms'.
+
+## Cause
+
+This issue occurs when certain required Omnichannel-related plugins are disabled.
+
+## Resolution
+
+To resolve this issue, follow these steps:
+
+### Step 1: Access the Customization Settings
+
+1. Open the **Dynamics 365 model-driven app**.
+
+2. Navigate to the following path: **Settings** > **Advanced Settings** > **Customizations** > **Customize the System**.
+
+### Step 2: Locate SDK Message Processing Steps
+
+1. Within the **Customize the System** window, expand the left-hand navigation panel.
+
+2. Select **SDK Message Processing Steps** under the **Components** section.
+
+### Step 3: Activate the Required Plugins
+
+1. In the **SDK Message Processing Steps** list, look in the **Name** column to locate the following plugins:
+
+    - **Microsoft.Dynamics.OmnichannelSharedBase.Plugins.PostOperationUpdatePrivacyTermsPlugin**: `msdyn_UpdatePrivacyTerms` of any Entity.
+    - **Microsoft.Dynamics.OmnichannelBase.Plugins.PostOperationUpdatePrivacyTermsPlugin**: `msdyn_UpdatePrivacyTerms` of any Entity.
+
+2. Verify the **Status** column for each plugin:
+
+    - If the plugin is disabled, select it by selecting the checkbox next to its name.
+
+    - Select the **Activate** button in the toolbar.
+
+### Step 4: Save and Publish Customizations
+
+1. Once the necessary plugins are activated, select **Save** in the toolbar.
+
+2. Then, select **Publish All Customizations** to apply the changes.

support/dynamics-365/customer-service/omnichannel-for-customer-service/resource-not-found-error-when-configuring-whatsapp-channel.md

@@ -165,13 +165,21 @@
         - name: Chat widget doesn't load on the portal
           href: omnichannel-for-customer-service/chat-widget-not-loading-portal.md     
         - name: Email field validation in a Pre-conversation survey doesn't work as expected
-          href: omnichannel-for-customer-service/email-field-validation-in-pre-conversation-survey-not-working.md           
+          href: omnichannel-for-customer-service/email-field-validation-in-pre-conversation-survey-not-working.md
     - name: Licensing, provisioning, and installation
       items:
+        - name: Agent capacity issue in customer support assignment
+          href: omnichannel-for-customer-service/agent-capacity-issue-in-customer-support-assignment.md
+        - name: Chat channel provisioning fails due to license issue
+          href: omnichannel-for-customer-service/chat-channel-provisioning-fails-in-due-to-license-issue.md
+        - name: Contact Center workspace isn't visible
+          href: omnichannel-for-customer-service/contact-center-workspace-not-visible.md
         - name: Instance unavailable to select on the provisioning app
           href: omnichannel-for-customer-service/instance-unavailable-provision-omnichannel.md
         - name: Omnichannel provisioning fails with an error
           href: omnichannel-for-customer-service/omnichannel-provision-fail-errors.md
+        - name: Troubleshoot issues with provisioning channels
+          href: omnichannel-for-customer-service/channel-provisioning-in-omnichannel-admin-center.md
     - name: Messaging capabilities
       items:
         - name: '"This number cannot be upgraded, Calling and SMS capabilities maxed out" error'    
@@ -205,4 +213,8 @@
         - name: Incoming voice calls with long greeting messages cause connection delays
           href: omnichannel-for-customer-service/greeting-message-delay-agent-connection.md
         - name: Use diagnostic messages to troubleshoot call issues
-          href: omnichannel-for-customer-service/use-diagnostic-messages-in-call-issues.md 
+          href: omnichannel-for-customer-service/use-diagnostic-messages-in-call-issues.md
+    - name: WhatsApp via Twilio
+      items:
+        - name: '"Resource not found" error when configuring WhatsApp channel'
+          href: omnichannel-for-customer-service/resource-not-found-error-when-configuring-whatsapp-channel.md