Skip to content

Commit e7c0da5

Browse files
author
Simonx Xu
committed
Add 2 articles
1 parent 3ec823f commit e7c0da5

3 files changed

Lines changed: 96 additions & 0 deletions

File tree

Lines changed: 42 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,42 @@
1+
---
2+
title: Troubleshoot Issues with Provisioning Channels
3+
description: Solves an issue where the Omnichannel Admin Center appears in read-only view and you can't manage or provision channels.
4+
author: Yerragovula
5+
ms.author: srreddy
6+
ai-usage: ai-assisted
7+
ms.date: 03/27/2025
8+
ms.reviewer: bavasude, srubinstein
9+
ms.custom: sap:Licensing, provisioning, and installation, DFM
10+
---
11+
# Provisioning channels in Omnichannel Admin Center
12+
13+
This article provides guidance for resolving provisioning issues when the Omnichannel Admin Center application appears in read-only view.
14+
15+
## Symptoms
16+
17+
When you try to provision a channel in the Omnichannel Admin Center, you encounter the following issues:
18+
19+
- The Omnichannel Admin Center appears in read-only view.
20+
- You can't manage or provision channels through the Omnichannel Admin center.
21+
22+
## Cause
23+
24+
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).
25+
26+
## Resolution
27+
28+
To successfully provision the chat (or other) channels, follow these steps:
29+
30+
1. Navigate to your environment.
31+
32+
2. Open the **Customer Service Admin Center** application.
33+
34+
3. Go to **Channels** under **Customer Support**.
35+
36+
4. Select **Manage** to configure the channels.
37+
38+
5. Check the appropriate boxes to provision the channels that you want to use.
39+
40+
6. Select **Save**.
41+
42+
For more information, see [Provision channels in Dynamics 365 Contact Center](/dynamics365/contact-center/implement/provision-channels).
Lines changed: 50 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,50 @@
1+
---
2+
title: Contact Center Workspace not Visible
3+
description: Solves an issue where users are unable to see or access the Dynamics 365 Contact Center workspace.
4+
author: Yerragovula
5+
ms.author: srreddy
6+
ai-usage: ai-assisted
7+
ms.date: 03/27/2025
8+
ms.reviewer: bavasude, srubinstein
9+
ms.custom: sap:Licensing, provisioning, and installation, DFM
10+
---
11+
# Contact center workspace not visible
12+
13+
Users may encounter an issue where they are 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.
14+
15+
## Symptoms
16+
17+
- Users with Dynamics 365 Contact Center licenses are unable to locate or access the Dynamics 365 Contact Center workspace within the system.
18+
- The workspace does not appear in the Dynamics 365 environment, despite license and role assignment.
19+
20+
## Cause
21+
22+
The Dynamics 365 Contact Center workspace and the Customer Service workspace cannot 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.
23+
24+
## Resolution
25+
26+
To enable the Dynamics 365 Contact Center workspace, follow these steps:
27+
28+
1. Create a new environment:
29+
30+
- Navigate to the [Power Platform Admin Center](https://admin.powerplatform.microsoft.com/).
31+
- Select **Environments** from the left-hand menu.
32+
- Click **+ New** to create a new environment.
33+
34+
2. Deploy the Contact Center app:
35+
36+
- During the provisioning of the new environment, ensure that you select the **Contact Center** app for deployment.
37+
- Complete the setup process as prompted.
38+
39+
3. Switch to the new environment:
40+
41+
- Users who need access to the Dynamics 365 Contact Center workspace should switch to the newly created environment.
42+
- Ensure that appropriate licenses and roles are assigned within this new environment.
43+
44+
> [!NOTE]
45+
> Existing organizations using the Customer Service workspace cannot simultaneously display the Contact Center workspace. A separate environment is required to use the Contact Center workspace.
46+
47+
## More Information
48+
49+
- [Overview of Contact Center workspace](/dynamics365/contact-center/use/ccw-overview)
50+
- [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/toc.yml

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -172,10 +172,14 @@
172172
href: omnichannel-for-customer-service/agent-capacity-issue-in-customer-support-assignment.md
173173
- name: Chat channel provisioning fails due to license issue
174174
href: omnichannel-for-customer-service/chat-channel-provisioning-fails-in-due-to-license-issue.md
175+
- name: Contact center workspace not visible
176+
href: omnichannel-for-customer-service/contact-center-workspace-not-visible.md
175177
- name: Instance unavailable to select on the provisioning app
176178
href: omnichannel-for-customer-service/instance-unavailable-provision-omnichannel.md
177179
- name: Omnichannel provisioning fails with an error
178180
href: omnichannel-for-customer-service/omnichannel-provision-fail-errors.md
181+
- name: Troubleshoot issues with provisioning channels
182+
href: omnichannel-for-customer-service/channel-provisioning-in-omnichannel-admin-center.md
179183
- name: Messaging capabilities
180184
items:
181185
- name: '"This number cannot be upgraded, Calling and SMS capabilities maxed out" error'

0 commit comments

Comments
 (0)