> For the complete documentation index, see [llms.txt](https://docs.fenixpyre.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fenixpyre.com/faqs-trouble-shooting/how-to-update-sharepoint-client-secret.md).

# How to update SharePoint Client Secret

Follow the steps below to update the client secret for the **FenixPyre** application in **Microsoft Azure**:

#### **Step 1: Access Azure Portal**

1. Open your web browser and navigate to [Azure Portal](https://portal.azure.com/).
2. Sign in using your **Azure administrator credentials**.<br>
3. Once logged in, click on **Azure Active Directory** from the left-hand menu.

   <figure><img src="https://3947089720-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOuMyGdeUQs2m5OYPFuwT%2Fuploads%2Fs5pEyJOhrFFgYhYObQ5n%2FSP.png?alt=media&amp;token=5f3f31a2-80b6-4d54-8d5a-a389300b7bd9" alt=""><figcaption></figcaption></figure>

#### **Step 2: Access App Registrations**

1. In the **Azure Active Directory** menu, click on **App Registrations**.

<figure><img src="https://3947089720-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOuMyGdeUQs2m5OYPFuwT%2Fuploads%2FS4WLlngvHj4FZPDvfjKj%2FSP1.png?alt=media&amp;token=f98d3984-339a-4c41-8dfb-29c1387d3dc0" alt=""><figcaption></figcaption></figure>

#### **Step 4: Locate the FenixPyre App**

1. In the list of registered applications, locate **FenixPyre(**&#x43;heck for the **Datanchor** app if you have not migrated to FenixPyr&#x65;**)**
2. **Verify the App ID** to ensure you are updating the correct application.

#### **Step 5: Check Certificate Expiry**

1. Under the **Certificates & secrets** section, check if the **current client secret has expired**.

<figure><img src="https://3947089720-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOuMyGdeUQs2m5OYPFuwT%2Fuploads%2FyUmZqUslEWvY4EjvzYmy%2FExpired.png?alt=media&amp;token=28c9a68c-778c-44bf-8277-83a70d8d37d9" alt=""><figcaption></figcaption></figure>

#### **Step 6: Create a New Client Secret**

1. Click on **+ New Client Secret**.
2. Enter a **description** (e.g., "FenixPyre Client Secret").
3. Select the desired **expiration period** (e.g., 6 months, 1 year, or 2 years).
4. Click **Add.**<br>

   <figure><img src="https://3947089720-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOuMyGdeUQs2m5OYPFuwT%2Fuploads%2F953s46mBFkZ9IHQjqlES%2Fnew_clientSecret.png?alt=media&amp;token=0d958c6a-c4ab-495a-b1d4-050cc1d7468d" alt=""><figcaption></figcaption></figure>

#### **Step 7: Copy and Store the Client Secret**

1. Once created, **copy the new client secret value immediately**.

   * **Important:** You will not be able to retrieve it later.

   <figure><img src="https://3947089720-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOuMyGdeUQs2m5OYPFuwT%2Fuploads%2F4QapNB79EtAgeu4FtS1Y%2Fnew_created.png?alt=media&amp;token=8bc9f141-e18a-452e-9fde-89fbeb8b2f45" alt=""><figcaption></figcaption></figure>
2. Store it securely in a **password manager** or a **secure vault**.

#### **Step 8: Update FenixPyre Configuration in Dashboard**

1. Navigate to the FenixPyre (Anchor) dashboard
   * Navigate to <https://admin.anchormydata.com/> or admin.fenixpyre.com if you have migrated to FenixPyre
   * Navigate to \<orgId>.[dashboard.datanchor.io](http://dashboard.datanchor.io/) if you have not migrated to FenixPyre
2. Click on edit and update the client secret ID<br>

   <figure><img src="https://3947089720-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOuMyGdeUQs2m5OYPFuwT%2Fuploads%2Fd3b4Z1O2czmBRpVnLsc9%2FScreenshot%202025-02-13%20at%204.05.26%E2%80%AFPM.png?alt=media&amp;token=1242f8f5-5f82-4db3-82e1-a05427d51a6d" alt=""><figcaption></figcaption></figure>

* **Application (Client) ID**: Locate this on the app’s overview page in Azure.
* **Directory (Tenant) ID**: This is also available on the app’s overview page in Azure.

<figure><img src="https://3947089720-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOuMyGdeUQs2m5OYPFuwT%2Fuploads%2FQxasNnxbuEkhFwxDNI7j%2Fimage.png?alt=media&amp;token=91c7dbc7-449b-4ed2-ad58-09202749653b" alt=""><figcaption></figcaption></figure>


---

# 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://docs.fenixpyre.com/faqs-trouble-shooting/how-to-update-sharepoint-client-secret.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.
