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.
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
Sign in with your tenant administrator account.
Step 2 — Create the billing policy
In the left-hand menu, navigate to Copilot → Billing & Usage.
Select the Billing policies tab and click + Add a billing policy.
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
Review the information and click Create policy.
Step 3 — Confirm activation
Still under Billing & Usage, select the Pay-as-you-go tab.
Locate the Microsoft 365 Copilot Retrieval API item.
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
Click + New → Agent.
Fill in:
Agent name
Agent objective
Add the data sources (specific files or the entire site content).
Define the agent's behavior instructions.
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:
Part 3 — Configure the Connector in Power Omni
Step 1 — Create the connector
Go to Settings → Artifacts → Connectors.
Click Create.
Select the SharePoint connector.
Fill in:
Connector name
Description
Associated Power Omni project
Step 2 — Create the connection
Click Create new connection.
Fill in:
Connection name (can be the same as the connector name)
SharePoint site URL:
https://<company>.sharepoint.com/sites/<site_name>
Click Save.
Step 3 — Link the connector to the agent
Go to Artifacts → Agents.
Select the desired agent and open the Relationships tab.
Add the connector you just created.
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
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
Last updated