> For the complete documentation index, see [llms.txt](https://university.gonexa.fr/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://university.gonexa.fr/connect/en/getting-started/configure-connect-sharepoint/configure-azure-and-sharepoint.md).

# Set up Azure and SharePoint for Gonexa Connect

These steps require access to your SharePoint by an administrator.

{% hint style="warning" %}
These steps require access to your SharePoint by an administrator.
{% endhint %}

## Creating an application

Access your SharePoint from the Azure portal ([portal.azure.com](https://portal.azure.com))

* Go to the "Azure Active Directory" service
* Go to "App registrations"
* Click "New registration"
* Enter a Name (e.g. Gonexa).
* Leave the default settings for now
* Click Register

## Adding the 3 application permissions

{% tabs %}
{% tab title="Permission 1: Microsoft Graph" %}

* Go to the "API permissions" tab
* Click "Add a permission"
* Select Microsoft Graph, then Application permissions
* Select the following permissions:
  * Site > Site.ReadWrite.All (Application)
  * Site > Site.Selected\* (Application)
  * Files > Files.ReadWrite.All (Application)
    {% endtab %}

{% tab title="Permission 2: SharePoint" %}

* Click "Add a permission"
* Go to the SharePoint tab
* Click Application permissions
* Select the following permissions:
  * Sites > Sites.ReadWrite.All (Application)
  * Sites > Sites.Selected\* (Application)
  * User > User.Read.All (Application)
    {% endtab %}
    {% endtabs %}

{% hint style="info" %}
**\*There are additional steps to be done by the SharePoint admin if this option is chosen instead of Sites.ReadWrite.All (**[**How to use**](https://devblogs.microsoft.com/microsoft365dev/controlling-app-access-on-specific-sharepoint-site-collections/)**).**
{% endhint %}

Then click Grant admin consent for {Your company name}

{% hint style="warning" %}
This step requires "SharePoint Super Admin" rights. If the button is disabled, contact an administrator with the required rights.
{% endhint %}

## Generate a client secret

Go to the Certificates & secrets tab, in the Client secrets tab\
Click "New client secret".

* Description: Gonexa Connect
* Expiry date: (*your choice*)\
  E.g. 730 days (24 months)

{% hint style="info" %}
Remember to update these items before the expiry date.
{% endhint %}

Click Add

## Retrieve the codes

Go to Certificates & secrets, in the Client secrets tab.\
Retrieve the following items:

* **Value:** this is the secret

{% hint style="warning" %}
This value can only be retrieved when the key is created. If it is no longer displayed, you will need to create another key.
{% endhint %}

From the Overview tab:

* **Application (client) ID**: this is the consumer ID
* **Directory (tenant) ID**: this is the tenant ID

## Creating a site from SharePoint

If you don't have a site set up in SharePoint yet, please create one.

{% hint style="info" %}
You can create a test site to install the Gonexa Connect package in a Sandbox.
{% endhint %}

* From SharePoint, go to My sites
* Click "Create site"
* Select "Team site"
* Site name: {your choice} e.g. Salesforce
* Click Next, then Finish


---

# 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://university.gonexa.fr/connect/en/getting-started/configure-connect-sharepoint/configure-azure-and-sharepoint.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.
