> For the complete documentation index, see [llms.txt](https://atlas.anywhere.now/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://atlas.anywhere.now/platform-administration/provisioning/provisioning/manage-services.md).

# Manage Services

View and manage existing OnePortal Services for Dialogue Cloud Neo customers.

Use the OnePortal **Services** view to inspect and manage the Services associated with your customers' Dialogue Cloud Neo environments.

## View Services

1. In OnePortal, select the customer from the customer list, or start typing the customer name in the **Customer** field.
2. Under **Cloud**, open **Services**.
3. Search for the Service, or select it from the displayed list.

The Service details open in a panel with operational information and available actions.

## Service details

The Service details panel contains these main areas:

| Area                | Use                                                                                                                                                          |
| ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Actions             | Provides Service-level actions such as replacing credentials, restarting the Service, changing configuration, downloading logs, or updating bundle versions. |
| Service information | Shows global configuration, license, and Service metrics for the selected Service.                                                                           |
| Requests            | Shows recent action requests and their status. Some completed requests can expose a follow-up action, such as downloading collected log files.               |
| Contact Centers     | Lists the Contact Centers on the Service and shows important configuration details. Select a Contact Center to open its Contact Center overview.             |

{% hint style="info" %}
Not all SharePoint client secret expiry dates can be retrieved. App registrations created through `AppRegNew.aspx` do not expose expiry information in the same way as current certificate-based setups. Where possible, use the current certificate-based SharePoint setup guidance.
{% endhint %}

Legacy client-secret renewal is a temporary compatibility path only. For SharePoint access, use the current App-Only certificate guidance instead of extending Azure ACS (AACS) client-secret authentication.

For SharePoint setup details, see [Configure SharePoint UCC sites](/set-up-dialogue-cloud-neo/prerequisites/configure-sharepoint-sites.md).

## Service actions

| Action   | Use                                                                                                                                                                                  |
| -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Replace  | Manage Graph Presence applications and credentials, initial SharePoint connection credentials, and the global SQL CDR database connection string.                                    |
| Restart  | Start a full Service restart, an application pool restart for web services, or a Graph Presence reset.                                                                               |
| Change   | Change deployment settings such as temporary log behavior, SBC configuration, license or authentication settings, Graph connection parameters, and Premium Insights where available. |
| Download | Download Service log files, the configuration file, or both.                                                                                                                         |
| Update   | Select an available bundle version for the customer Service.                                                                                                                         |

{% hint style="warning" %}
Service-level changes can affect all Contact Centers on the Service. Plan restart, credential, and routing changes through the current delivery or support process before applying them in production.
{% endhint %}

## Restart behavior

Restart actions can affect active calls, new call handling, Graph Presence behavior, and when configuration changes are processed. The exact effect depends on the restart option and the current Service state.

Before submitting a restart, review the selected option in OnePortal and confirm the planned impact with the current delivery or support process.

## Verification

1. Confirm that the selected Service is the intended customer Service.
2. Confirm the expected action request appears in the request overview.
3. Monitor the request until it reaches a completed or failed state.
4. For restart or configuration actions, confirm that the affected Contact Centers return to the expected operational state.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://atlas.anywhere.now/platform-administration/provisioning/provisioning/manage-services.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.