Microsoft SharePoint Site
Microsoft SharePoint Site connects Oracle Fusion AI Agent Studio to a configured SharePoint site through Microsoft Graph. It supports agentic operations for working with the site's document libraries, folders, files, lists, and pages.
Use this connector when your solution is centered on a specific SharePoint site. For agentic operations across permitted SharePoint sites, use Microsoft SharePoint.
What You Can Do
| Capability | What it supports |
|---|---|
| Access the configured site | Retrieve the configured site and list its document libraries. |
| Browse and search | List items in a library's root or child folders and search for files within a library. |
| Retrieve content | Retrieve file or folder metadata and download file content. |
| Work with lists and pages | Retrieve SharePoint list data, list site pages, and retrieve page content. |
| Manage files and folders | Create folders; upload or replace files; and rename, move, or copy items, including copying between libraries. |
| Delete items | Move a file or folder to the SharePoint recycle bin. |
| Create a basic page | Create a page with a name, title, and optional layout. This operation does not accept arbitrary page-body content. |
| Browse and link files | Use delegated-user access or configured application permissions to browse and link SharePoint files. Delegated access can also support security propagation and Fusion-to-Microsoft identity mapping. |
Authentication and Prerequisites
| Usage | Authentication |
|---|---|
| Agentic operations in AI Agent Studio | Client Credentials |
| File Store with user-specific access | Delegated OAuth |
| File Store with application access | Configured Application Permissions |
Before configuring the connector, obtain:
- SharePoint host name: Enter only the host name, such as
contoso.sharepoint.com, withouthttps://or the site path. Enter the site path separately. - SharePoint site path: For example,
sites/Financeorteams/ProjectTeam. - Microsoft Entra details: Tenant ID, client ID, and client secret for the registered application.
- Proxy details: Required only when your environment accesses Microsoft Graph through a proxy.
Microsoft Graph Permissions
Configure only the permissions required for the intended operations and obtain administrator consent when required.
| Usage | Microsoft Graph permissions |
|---|---|
| Read-only agentic operations |
Sites.Read.All
|
| Agentic operations that create or modify content |
Sites.ReadWrite.All
|
| Delegated File Store access | User.Read, Files.Read.All, and
Sites.Read.All |
For File Store access using Configured Application Permissions, the connector
requests the application permissions configured for the Microsoft Entra application
through the .default scope.
Security propagation is available only with Delegated OAuth. When it is enabled, the connector provides a default mapping that matches the Fusion user's email address with the Microsoft user's email address. Review this mapping with your identity administrator and change it only if your organization uses different identity fields.
For more information, refer:
Configure and use in AI Agent Studio
The following sections provide instructions on how to configure and use the connector in AI Agent Studio:
Create the Connector Instance
- In AI Agent Studio, go to Credentials > Connectors.
- Select Add Connector, and then choose Microsoft SharePoint Site.
- Keep the default Microsoft Graph base URL unless your environment requires a different supported endpoint.
- Enter the SharePoint host name and site path separately.
- Configure a proxy only if your environment requires one.
Enable Agentic Operations
- Enable Agentic.
- Select Client Credentials.
- Enter the tenant ID, client ID, and client secret.
- Save the connector instance.
- In AI Agent Studio, go to Resources > Tools and select Add Tool.
- Choose Connector as the tool type and select the saved connector.
- Wait for the available functions to be listed, and then select only the functions required for your agent or workflow.
Enable File Store
- Enable File Store when users need to browse and link SharePoint files.
- Choose one of the following access modes: - Delegated OAuth for access based on the signed-in user's Microsoft identity. - Configured Application Permissions for access through the configured Microsoft Entra application.
- When using Delegated OAuth, enable Security Propagation when the mapped user's SharePoint access must be applied. Review the prepopulated identity mapping before saving.
- Use the provided File Store interface to browse and link content from the configured SharePoint site.
Validate the Connection
For agentic operations, start with safe read operations:
- Retrieve the configured site with
sharepoint_get_configured_site. - List its document libraries with
sharepoint_list_site_drives. - List the root items in an approved library with
sharepoint_list_root_items. - Retrieve metadata for a known test item with
sharepoint_get_item_metadata.
For File Store, sign in or use the configured application access mode and confirm that users can browse and link the intended site content.
If validation fails, check the host name and site path, tenant and application details, Microsoft Graph permissions and administrator consent, and proxy settings.
Configure with the AI Studio Skill
If you use Codex or Claude, ask it to use the installed aistudio
skill to configure the Microsoft SharePoint Site connector.
Use a prompt such as:
Use the installed aistudio skill to configure a Microsoft SharePoint Site connector instance in this AI Studio project.
Reuse the existing Microsoft SharePoint Site connector definition. Guide me through the staged configuration, including family, product, prefix, user groups, and all required and optional connector settings. Use every valid default value provided by the connector definition instead of asking me to enter it again. For optional settings with defaults, accept the default and mark the setting as reviewed. Ask only for values that have no default or choices that require my decision, and do not display secrets after I provide them.
Create the connector instance as a local draft first. Show me the draft path and a redacted configuration summary that identifies the defaults used, and do not save it to AI Agent Studio until I explicitly approve the save.
After the connector instance is saved, verify the connection with a safe operation before selecting its functions for an agent or workflow. Keep only the capabilities required for the intended Fusion use case.
Sample Use Cases
- File Store use cases:
-
Find governed enterprise knowledge
Allow users to browse and link policies, procedures, implementation guidance, or project documents from the configured SharePoint site.
-
Provide permission-aware document access
Use Delegated OAuth with security propagation and Fusion-to-Microsoft identity mapping so users can discover SharePoint content based on their mapped Microsoft identity and existing access.
-
- Agentic workflow use cases
-
Support business approvals with current evidence
Find the latest contract, policy, checklist, or supporting document and provide the approver with relevant details and a link to the SharePoint source.
-
Publish approved project deliverables
After approval, upload reports, implementation checklists, or project documents to the appropriate document library and confirm the resulting item and link.
-
Organize enterprise project records
Create folders and—with approval—rename, move, or copy documents into the correct project or department location.
-
Prepare audit and compliance evidence
Retrieve approved documents, list items, page content, and modification details to prepare a source-linked evidence summary for audit or compliance teams.
-
Works Well With
The following examples are illustrative agentic workflow patterns. Available actions depend on the companion connector operations, permissions, and approval controls configured in AI Agent Studio.
- Microsoft Teams — Create a unified project briefing
Combine relevant documents from the configured SharePoint site with recent Microsoft Teams channel discussions to create a concise briefing of decisions, risks, progress, and outstanding actions. This helps project teams and leaders understand the latest situation without reviewing each source separately.
This workflow retrieves and summarizes Teams channel messages; it does not post messages to Teams.
- Google Docs — Create collaborative documents from governed
content
Retrieve approved content from the configured SharePoint site and—with appropriate access and approval—create or update a Google Doc for project briefs, implementation plans, audit responses, or other collaborative work. Include the SharePoint source links so users can trace the document back to its governed content.
- Jira — Turn SharePoint evidence into trackable work
Retrieve relevant SharePoint documents, check Jira for related or duplicate issues, and—with appropriate approval—create a new Jira issue or update an existing one with the supporting SharePoint context and source link. This helps teams convert audit findings, project risks, and operational evidence into traceable work.