The Copilot Service admin center

What it does

It's the model-driven app where you configure Customer Service. It replaced two older admin surfaces — the Omnichannel admin center and the service management area inside Customer Service Hub — and it now carries the name Copilot Service admin center in the docs and in the app list.

Key facts

Shipped GA in April 2022 as Customer Service admin center; the rename to Copilot Service admin center came later, and older Learn pages and consultants both still say "CS admin centre". Same app.
It is installed automatically in every Customer Service organisation. There is nothing to deploy.
No data migration was ever needed when moving off the old apps — the settings write to the same tables, only the shell changed.
The site map has three areas: Customer support (users, channels, queues, routing, workstreams, case settings, customer settings), Support experience (workspaces, productivity, knowledge) and Operations (insights, calendar, service terms, service scheduling, miscellaneous).
The site map is adaptive: areas for capabilities you haven't provisioned simply don't render, which is why two environments can show different menus.
Full access needs System Administrator or System Customizer. Partial access is possible with CSR Manager (queues, email, record creation rules, workstreams), Omnichannel administrator plus Basic User, or App Profile Manager Administrator plus Basic User.
The Omnichannel admin center app is deprecated and hidden by default, but it still exists and is still visible from Power Apps.
There's a "Create your contact center" wizard that stands up chat, voice, a default agent experience profile and some AI features in one pass — new organisations only.
Admin settings search works across the site map, which is the fastest way to find a setting whose page has moved between waves.
The site map is customisable with the app designer, including adding your own tables.

When to use / skip

There is no choice to make here — this is the admin app, and anything you configure elsewhere is either legacy or headed there. The real decision is what you tell a client who has been running on Omnichannel admin center or the Hub settings area for years and has runbooks, screenshots and training decks pointing at them. Move them. The old apps get no new settings, so every feature added since 2022 is only reachable from here, and you will eventually hit a support case where Microsoft asks for a screen you can't produce.

Where it genuinely doesn't help: tenant and environment concerns. Licence assignment, environment copy, storage capacity, auditing configuration and DLP all live in the Microsoft 365 and Power Platform admin centres. Expect to have both open.

Configuration decisions

Which admin app your client's team is allowed to use, and whether you hide the deprecated Omnichannel admin center outright to stop people drifting back.
How admin access is split: blanket System Administrator, or CSR Manager and Omnichannel administrator for the people who only manage queues, workstreams and agents day to day.
Whether admin roles are scoped to a business unit — relevant if a shared service platform has more than one service desk configuring its own queues.
Whether you extend the site map with the client's own configuration tables so support managers have one place to go rather than a second app.
Whether to run the contact centre wizard on a fresh environment or configure channels by hand — the wizard is quick but makes choices you'll have to unpick.
Which column security profiles admins need, since some settings pages write to secure columns (authentication settings, SMS settings, payment profiles) and fail quietly without them.

Gotchas

Customisations made to the old Omnichannel admin center site map do not come across. You have to rebuild them in the app designer, and Microsoft's own advice is to add new sub-areas rather than edit the shipped ones, or your changes get overwritten on the next update.
Omnichannel administrator on its own isn't enough for a lot of tasks. It needs Basic User alongside it, and several operations still want System Administrator.
Some links in the admin centre still drop you into the legacy settings dialogs or the Power Platform admin center. That's expected, not a broken environment.
Because the site map is capability-driven, a setting missing in UAT but present in dev usually means a capability wasn't provisioned in UAT, not that the solution failed to import.
Creating a shared mailbox from within the admin centre needs Microsoft 365 tenant admin rights, which the Dynamics admin frequently doesn't have. Plan that handover early.
Deep links you put in documentation are not stable across release waves. Reference the setting name and the area, not the URL.

Consultant notes

Demo the admin settings search early. It's the single thing that stops a new admin team giving up when a setting has moved.
Agree an admin RACI at design stage. "Everyone gets System Administrator" is the default outcome if you don't, and it makes every later security conversation harder.
Push back on requests to keep using the Hub settings area for familiarity. You are only deferring the migration and adding a second place for configuration drift.
Before go-live, check the client's admin users can actually open every area they own with their assigned roles, in the target environment, not in dev where everyone is a System Administrator.
Screenshot-based training material for this app ages fast. Write task-based documentation instead, or expect to redo it every wave.

Worth another look after each release wave — the site map areas and the app's own name have both moved before.