# SharePoint

#### 1. Introduction

This section describes the process of integrating SharePoint with Power Omni via connector. By following these instructions, you will be able to configure access to SharePoint documents and sites so they can be consumed by AI agents in Power Omni.

***

#### 2. Prerequisites

Make sure all items below are met before starting the configuration.

| Requirement                   | Description                                                                   |
| ----------------------------- | ----------------------------------------------------------------------------- |
| Azure Subscription            | Access as **Owner** or **Contributor** on the subscription and resource group |
| Microsoft 365 Copilot License | At least **1 active license** throughout the entire period of use             |
| SharePoint Read Permission    | The user needs read access to the sites and documents to be queried           |
| Pay-as-you-go Retrieval API   | Best alternative to avoid purchasing Copilot licenses for end users           |

> 💡 **Recommendation:** The Pay-as-you-go model is the most cost-effective alternative for teams that don't need full Copilot licenses, paying only for effective API usage.

***

#### 3. Configuration

The configuration is divided into three parts that must be executed in the order presented.

***

**Part 1 — Enable the Pay-as-you-go Service in Microsoft 365**

> 🔐 **Who runs this:** Microsoft 365 tenant administrator.

**Step 1 — Access the Admin Center**

1. Go to <https://admin.microsoft.com>
2. Sign in with your tenant administrator account.

**Step 2 — Create the billing policy**

1. In the left-hand menu, navigate to **Copilot → Billing & Usage**.
2. Select the **Billing policies** tab and click **+ Add a billing policy**.
3. Fill in the policy settings:
   * **Policy name**
   * **Azure Subscription** and **Resource Group** for billing
   * **User scope:** all users or a specific group
   * **Budget (optional):** enable *Set a budget for this policy* and define a maximum amount, or leave unlimited
4. Review the information and click **Create policy**.

**Step 3 — Confirm activation**

1. Still under **Billing & Usage**, select the **Pay-as-you-go** tab.
2. Locate the **Microsoft 365 Copilot Retrieval API** item.
3. Confirm the status shows **Connected**.

> ⚠️ **Warning — Propagation time:** After activation, wait up to **2 hours** for the service to propagate across the entire tenant. The first API call after this period may fail — this is expected behavior. Starting from the second call, the service will work normally.

***

**Part 2 — Create the Agent in SharePoint**

> 🔐 **Who runs this:** User with an active Microsoft 365 Copilot license.

**Step 1 — Access the SharePoint site**

Navigate to the SharePoint site whose files the agent should access.

**Step 2 — Create the agent**

1. Click **+ New → Agent**.
2. Fill in:
   * **Agent name**
   * **Agent objective**
3. Add the **data sources** (specific files or the entire site content).
4. Define the agent's **behavior instructions**.
5. Click **Create agent**.

**Step 3 — Copy the site URL**

After saving, copy the site URL for use in the next part. The expected format is:

```
https://<company>.sharepoint.com/sites/<site_name>
```

***

**Part 3 — Configure the Connector in Power Omni**

**Step 1 — Create the connector**

1. Go to **Settings → Artifacts → Connectors**.
2. Click **Create**.
3. Select the **SharePoint** connector.
4. Fill in:
   * **Connector name**
   * **Description**
   * **Associated Power Omni project**

**Step 2 — Create the connection**

1. Click **Create new connection**.
2. Fill in:
   * **Connection name** (can be the same as the connector name)
   * **SharePoint site URL:** `https://<company>.sharepoint.com/sites/<site_name>`
3. Click **Save**.

**Step 3 — Link the connector to the agent**

1. Go to **Artifacts → Agents**.
2. Select the desired agent and open the **Relationships** tab.
3. Add the connector you just created.
4. Save and test the agent.

> 📌 **Limitation:** Only **1 SharePoint connection per agent** is allowed. To access multiple sites, create separate agents for each one.

***

#### 4. Permissions and Billing Model

**4.1 Access for other users**

Users without a Copilot license can use the agent as long as they are included in the Pay-as-you-go billing policy.

**4.2 Costs**

| Item                       | Value                                               |
| -------------------------- | --------------------------------------------------- |
| Pay-as-you-go service call | **$0.10 per call** (preview pricing)                |
| Consumption monitoring     | Azure Cost Management                               |
| Usage limits               | Configurable (daily and monthly) via billing policy |

***

#### 5. Conclusion

The SharePoint integration with Power Omni allows you to query data directly from SharePoint sites and documents within Power Omni agents. Follow the three configuration parts in the order presented and validate each step before moving on to the next.

If you run into issues, verify that:

* The Pay-as-you-go policy status shows **Connected**
* The 2-hour propagation window has already passed
* The SharePoint site URL was copied correctly


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.poweromni.ai/en/administration-and-configuration/artifacts/connectors/sharepoint.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.