SharePoint

​

Introduction

• Centralized Document Management: SharePoint provides a central repository for storing, organizing, and managing documents, ensuring version control, secure access, and efficient document retrieval. Document libraries offer features like check-in/check-out, version history, and metadata tagging for robust document lifecycle management.
• Collaborative Workspaces and Team Sites: SharePoint enables the creation of team sites and collaboration workspaces, providing teams with a shared platform for communication, document sharing, task management, and project collaboration.
• Customizable Lists and Libraries: SharePoint lists and libraries are highly customizable and can be tailored to meet specific business needs. Lists can track tasks, manage contacts, or hold custom data tables, while libraries organize documents and media of all types.
• Workflow Automation: SharePoint supports workflow automation through Power Automate and SharePoint workflows, allowing organizations to automate business processes, streamline approvals, and automate document-centric workflows.
• Enterprise Search Capabilities: SharePoint offers robust enterprise search capabilities, enabling users to quickly find relevant information across sites, document libraries, lists, and other content sources.

​

Toolkit’s Account Setup and Configuration in SharePoint

​

Registering an App in Azure Active Directory (Azure AD)

1. Access Azure Portal: Open your web browser and navigate to the Azure Portal and log in using an account with sufficient permissions to register applications in Azure AD.
2. Navigate to App Registrations: In the Azure portal, use the search bar at the top to search for “App registrations” and select “App registrations” from the search results under “Services”.
3. Create New Registration: On the “App registrations” page, click on ”+ New registration”.
4. Configure App Registration Details: On the “Register an application” page, provide the following information:
   • Name: Enter a meaningful and descriptive name for your application registration. For example, use “ELITEA SharePoint Integration” or “ELITEA Agent Access to SharePoint”. This name will help you identify the purpose of this app registration later.
   • Supported account types: Select the appropriate account type based on your organization’s requirements. In most cases, “Accounts in this organizational directory only ([Your Organization Name] only - Single tenant)” is the recommended option for internal organizational use. If you need to access SharePoint resources across multiple organizations, you may need to select a different option.
   • Redirect URI: If you plan to use Delegated (User OAuth) authentication, set the redirect URI here during registration:
     1. In the “Select a platform” dropdown, select “Web”.
     2. In the URI field, enter the ELITEA callback URL for your instance. The correct value depends on your deployment — refer to the info callout below.

     If you are using App-Only (Client Credentials) mode only, leave this field blank.

5. Register Application: After providing the application details, click the “Register” button at the bottom of the page to create the app registration.

​

Application Credentials

• Application (client) ID — Copy and store this value securely.
• Directory (tenant) ID — Copy and store this value securely.

​

Configure API Permissions for the Registered App

1. Navigate to API Permissions: In your registered app within the Azure portal, navigate to the left-hand menu and click on “API permissions”.
2. Add Permissions: On the “API permissions” page, click on ”+ Add a permission”.
3. Select API Type - Microsoft Graph: In the “Request API permissions” panel, select the “Microsoft Graph” API tile. Microsoft Graph provides access to various Microsoft 365 services, including SharePoint.
4. Select Permission Type - Application permissions: Choose “Application permissions” as the permission type. Application permissions are used when the application acts without a signed-in user (App-Only mode). If you are using Delegated (User OAuth) mode, you may also need to add Delegated permissions.
5. Add Microsoft Graph Scopes: In the “Application permissions” section, use the search bar to search for and select the following scopes:

   Scope	Description	When to Grant
   Sites.Read.All	Read all site collections, lists, and libraries without a signed-in user	Always — required for read access
   Sites.ReadWrite.All	Read and write all site collections, lists, and libraries without a signed-in user	Only if Agents need to create or modify SharePoint content

   
6. Add Permissions - SharePoint API: Click ”+ Add a permission” again to add SharePoint-specific permissions. This time, in the “Request API permissions” panel, select the “SharePoint” API tile (you may need to scroll down to find it).
7. Select Permission Type - Application permissions: Choose “Application permissions” as the permission type for the SharePoint API as well. If you are using Delegated (User OAuth) mode, select Delegated permissions instead.
8. Add SharePoint Scopes: In the “Application permissions” section for SharePoint API, use the search bar to search for and select the following scope:

   Scope	Description	When to Grant
   Sites.FullControl.All	Full control of all site collections without a signed-in user	Only if absolutely necessary — prefer Microsoft Graph scopes for better security

9. Add Permissions: After selecting the necessary scopes for both Microsoft Graph and SharePoint APIs, click the “Add permissions” button at the bottom of the “Request API permissions” panel to add the selected permissions to your application registration.
10. Grant Admin Consent: On the “API permissions” page, you will see the newly added permissions listed. Click the “Grant admin consent for [Your Organization Name]” button and then click “Yes” to grant admin consent for these permissions. Admin consent is required for application permissions to take effect.

​

Configure the Client Secret

1. Navigate to Certificates & secrets: In your registered app within the Azure portal, navigate to the left-hand menu and click on “Certificates & secrets”.
2. Create New Client Secret: On the “Certificates & secrets” page, click on “Client secrets” tab (if not already selected) and then click ”+ New client secret”.
3. Configure Client Secret Details: In the “Add a client secret” panel:
   • Description: Enter a descriptive name for your client secret.
   • Expiration: Choose an appropriate expiration period for the client secret from the “Expires” dropdown.
4. Add Client Secret: Click the “Add” button at the bottom of the “Add a client secret” panel to create the client secret.
5. Securely Copy and Store Client Secret Value: Immediately copy the generated Client Secret Value displayed in the “Value” column. This is the only time you will see the full Client Secret Value. Store it securely in a password manager or in ELITEA’s Secrets feature. Do not store the value in plain text. !!! warning “Important” Copy the “Value” column — not the “Secret ID” column. The Value is the actual credential used for authentication.

​

Grant App-Only Access to the SharePoint Site

1. Navigate to the SharePoint AppInv.aspx page: Open your browser and go to the following URL, replacing {your-tenant} and {site} with your values:
   https://{your-tenant}.sharepoint.com/sites/{site}/_layouts/15/appinv.aspx
   
   Example:
   https://contoso.sharepoint.com/sites/MyProjectSite/_layouts/15/appinv.aspx
   
2. Look Up the App: In the “App Id” field, enter your Application (client) ID and click “Lookup”. Verify that the Title, App Domain, and Redirect URL are populated correctly.
3. Define Permissions using XML: In the “Permission Request XML” field, enter one of the following XML blocks depending on the level of access your Agents require: !!! example “Permission Request XML Options” Full Control (read and write operations):
   <AppPermissionRequests AllowAppOnlyPolicy="true">
     <AppPermissionRequest Scope="http://sharepoint/content/sitecollection" Right="FullControl" />
   </AppPermissionRequests>
   
   Read-Only Access:
   <AppPermissionRequests AllowAppOnlyPolicy="true">
     <AppPermissionRequest Scope="http://sharepoint/content/sitecollection" Right="Read" />
   </AppPermissionRequests>
   
   !!! warning “Principle of Least Privilege” Grant only the minimum required permissions. Avoid FullControl unless your Agents need to create, modify, or delete SharePoint content.
4. Create and Trust the App: Click “Create”, then click “Trust It” on the confirmation page to grant the requested permissions to your application.

​

System Integration with ELITEA

​

Step 1: Create SharePoint Credentials

1. Navigate to Credentials Menu: Open the sidebar and select Credentials.
2. Create New Credential: Click the + Create button.
3. Select SharePoint: Choose SharePoint as the credential type.
4. Configure credential fields:

   Field	Description	Example
   Display Name	Descriptive name for this credential	SharePoint - Contoso Marketing Site
   Client ID	Application (client) ID from your Azure AD app registration	xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
   Client Secret	Client Secret Value generated in Azure AD	your-client-secret-value
   Site URL	Full URL of your SharePoint site	https://contoso.sharepoint.com/sites/MarketingTeam

5. Select the authentication tab: In the credential form, choose either “App-only” or “Delegated” depending on your access model.

​

App-Only (Client Credentials)

1. Test Connection: Click Test Connectionto verify your credentials are valid and ELITEA can connect to SharePoint.
2. Save Credential: Click Save.

​

Delegated (User OAuth)

1. Configure additional Delegated fields:

   Field	Description	Example
   OAuth Discovery Endpoint	Azure AD tenant base URL in the format https://login.microsoftonline.com/{tenant_id}. The {tenant_id} is the Directory (tenant) ID from your Azure AD App Registration Overview page	https://login.microsoftonline.com/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
   Scopes	Space-separated OAuth permission scopes the delegated token should request	Sites.ReadWrite.All Files.ReadWrite.All Notes.ReadWrite.All

2. Log in: Once the OAuth Discovery Endpoint field is filled in, a Login button appears next to the Test Connection button. Click Login to initiate the OAuth authorization flow — ELITEA calls the SharePoint check-connection endpoint, which redirects to Azure AD for user sign-in. After you authorize the application, the token is stored and the connection is verified via Microsoft Graph.

   After a successful login, the Login button changes to Logout. Click Logout at any time to clear the stored token and disconnect the credential.

3. Save Credential: Click Save.

​

Choosing an Authentication Mode

• Your workflow runs automatically, without a user actively involved (e.g., a nightly report, a scheduled file sync, or a background data processing pipeline).
• You want a single shared connection that doesn’t depend on any individual user’s account.
• You need to read from or write to public team sites where user identity doesn’t matter. !!! example An ELITEA Agent that runs every morning, reads all items from a “Project Tasks” list, and generates a summary report — App-Only is the right choice here because no user interaction is needed.

• You need to access OneNote notebooks (only available in Delegated mode).
• Your organization’s SharePoint permissions are user-based — only specific people can see certain sites or libraries.
• The workflow involves a user actively working in ELITEA and you want actions to be logged under their identity.
• You’re building a personal assistant that reads documents or lists on behalf of the signed-in user. !!! example An ELITEA Agent helping a team member search their department’s restricted SharePoint site and read OneNote meeting notes — Delegated is required because the site is access-controlled per user and OneNote needs a user token.

  	App-Only (Client Credentials)	Delegated (User OAuth)
  How it works	ELITEA connects as the application itself, with no user involved	ELITEA connects on behalf of a specific signed-in user
  Best for	Automation, background tasks, scheduled workflows	Workflows where user identity matters, or access is restricted to specific users
  Example use case	Nightly report generation, automated file archiving, batch list updates	Reading a user’s personal SharePoint files, accessing sites restricted to certain team members
  OneNote support	✘ Not supported	✔️ Supported
  Setup complexity	Simpler — App registration + AppInv.aspx site grant	Requires Redirect URI + OAuth login step
  Access scope	Defined by permissions granted to the app	Defined by the permissions of the signed-in user

​

Step 2: Create SharePoint Toolkit

1. Navigate to Toolkits Menu: Open the sidebar and select Toolkits.
2. Create New Toolkit: Click the + Create button.
3. Select SharePoint: Choose SharePoint from the list of available toolkit types.
4. Configure Toolkit Settings:

   Field	Description	Example
   Toolkit Name	Descriptive name for your toolkit (required)	SharePoint - Marketing Documents
   Description	Optional description for the toolkit purpose	Toolkit for accessing the Marketing Team SharePoint site
   Credentials	Select your previously created SharePoint credential	SharePoint - Contoso Marketing Site
   PgVector Configuration	(Optional) Select PgVector connection for indexing and semantic search features	Your PgVector configuration
   Embedding Model	(Optional) Select embedding model for text processing and semantic search	amazon.titan-embed-text-v2:0

5. Enable Desired Tools: In the “Tools” section, select the checkboxes next to the specific SharePoint tools you want to enable. Enable only the tools your agents will actually use to follow the principle of least privilege.
   • Make Tools Available by MCP — (optional checkbox) Enable this option to make the selected tools accessible through external MCP clients.
6. Save Toolkit: Click Save to create the toolkit.

​

OAuth Status Bar (Delegated mode only)

• A colored status indicator with “Connected!” (green) when a valid OAuth token is present, or “Not Connected” (orange/warning) when no token exists or the token has expired.
• A Login button when not connected, or a Logout button when connected.

​

Available Tools

• The SharePoint toolkit provides the following tools for interacting with SharePoint sites, document libraries, and lists, organized by functional categories:

  Tool Category	Tool Name	Description	Primary Use Case
  File Operations
  	Get files list	Lists files in a SharePoint document library, optionally filtered by folder or library name; supports include_extensions and skip_extensions filters to narrow results by file type	Browse and discover files across document libraries
  	Read document	Reads the content of a document at a given server-relative path; supports .docx, .xlsx, .pptx, .pdf, .txt, .csv, and more; optional page_number (for multi-page documents), sheet_name (Excel), and is_capture_image (AI image description) parameters	Extract text content from SharePoint documents for analysis or summarization
  	Upload file	Uploads a file to a specified SharePoint document library folder, from artifact storage or direct string content	Automate file delivery and publishing to SharePoint
  List & Data Operations
  	Get lists	Returns all visible SharePoint lists on the configured site with their titles, IDs, descriptions, and item counts	Discover lists on a site before reading or writing data
  	Read list	Reads items from a specified SharePoint list (up to a configurable limit)	Access and process data stored in SharePoint lists
  	Get list columns	Returns all column metadata for a specified list, including field names, display names, types, required flags, and valid choice values	Discover available columns before creating list items
  	Create list item	Creates a new item in a specified SharePoint list using a dictionary of field-value pairs	Automate data entry and record creation in SharePoint lists
  OneNote Operations
  	Onenote get notebooks	Lists all OneNote notebooks in the configured SharePoint site, returning ids, display names, creation dates, and web URLs	Discover notebooks on a site before reading or writing OneNote content
  	Onenote get sections	Lists all sections in a specific OneNote notebook, returning section ids, display names, and page URLs	Browse notebook structure to locate a section before reading pages
  	Onenote get pages	Lists page metadata (id, title, dates, webUrl) from a OneNote section; does not return page content	Discover pages in a section before reading their content
  	Onenote get page content	Retrieves the raw HTML content of a OneNote page as stored by the service	Access the raw XHTML of a page for programmatic processing or export
  	Onenote list attachments	Lists all file attachments on a OneNote page, returning filenames, resource IDs, and download URLs	Discover files attached to a page before downloading or reading them
  	Onenote read attachment	Downloads and parses a file attachment from a OneNote page; supports PDF, DOCX, XLSX, PPTX, images, and more	Extract text content from files attached to OneNote pages for analysis
  	Onenote read page	Reads and converts a OneNote page into beautified plain text; supports capture_images (AI image descriptions, default on), include_attachments (list attachments inline, default on), and read_attachment_content (parse attachment content inline, default off)	Retrieve human-readable page content for summarization or analysis
  	Onenote read page items	Reads a OneNote page into a structured list of typed items (text, image, attachment) in document order; supports capture_images, include_attachments, and read_attachment_content parameters	Process page content programmatically with fine-grained control over each element
  	Onenote create notebook	Creates a new OneNote notebook in the SharePoint site, returning the notebook id, display name, and web URL	Set up new notebooks for organizing notes and content
  	Onenote create section	Creates a new section within an existing OneNote notebook, returning the section id and display name	Add organizational sections to an existing notebook
  	Onenote create page	Creates a new page in a OneNote section from an HTML document, returning the page id, title, and web URL	Publish AI-generated or automated content as OneNote pages
  	Onenote update page	Updates a OneNote page using Graph API PATCH commands to append, prepend, replace, or delete specific content elements	Make targeted incremental edits to existing OneNote pages
  	Onenote replace page content	Replaces the entire body of a OneNote page with new HTML content	Fully overwrite a page’s content with a new version
  	Onenote delete page	Permanently deletes a OneNote page (this action is irreversible)	Remove outdated or incorrect OneNote pages
  Indexing & Search
  	Index data	Creates searchable indexes of SharePoint document library content; supports include_onenote flag (with optional onenote_filter) to also index OneNote pages and attachments alongside document library files	Enable advanced semantic search across SharePoint files and OneNote pages
  	List collections	Lists available indexed content collections	View and manage indexed SharePoint data collections
  	Remove index	Removes a previously created search index	Clean up indexed SharePoint data
  	Search index	Performs semantic searches across indexed SharePoint content	Find specific documents or file content across the site
  	Stepback search index	Performs advanced contextual searches with broader scope	Execute sophisticated searches with expanded context
  	Stepback summary index	Creates comprehensive summaries of indexed SharePoint content	Generate intelligent summaries of documents and files

  !!! tip “Vector Search Tools” The tools Index data, List collections, Remove index, Search index, Stepback search index, and Stepback summary index require PgVector configuration and an embedding model. These enable advanced semantic search capabilities across your SharePoint documents.

​

Testing Toolkit Tools

1. Select LLM Model: Choose a Large Language Model from the model dropdown in the Test Settings panel.
2. Configure Model Settings: Adjust model parameters like Creativity, Max Completion Tokens, and other settings as needed.
3. Select a Tool: Choose the specific SharePoint tool you want to test from the available tools.
4. Provide Input: Enter any required parameters or test queries for the selected tool.
5. Run the Test: Execute the tool and wait for the response.
6. Review the Response: Analyze the output to verify the tool is working correctly and returning expected results. !!! tip “Key benefits of testing toolkit tools:”
   • Verify that SharePoint credentials and connection are configured correctly
   • Test tool parameters and see actual responses from your SharePoint site
   • Debug tool behavior and understand output formats
   • Optimize tool settings before integrating with agents or pipelines

   For detailed instructions on how to use the Test Settings panel, see How to Test Toolkit Tools.

​

Step 3: Add SharePoint Toolkit to Your Workflows

​

In Agents:

1. Navigate to Agents: Open the sidebar and select Agents.
2. Create or Edit Agent: Either create a new agent or select an existing agent to edit.
3. Add SharePoint Toolkit:
   • In the “TOOLKITS” section of the agent configuration, click the “+Toolkit” icon.
   • Select your configured SharePoint toolkit from the dropdown list.
   • The toolkit will be added to your agent with the previously configured tools enabled.
   • If the toolkit uses a Delegated (User OAuth) credential, a connection status icon (globe indicator) and a Log in button appear at the right side of the toolkit row. Click Log in to authorize the SharePoint connection directly from the agent configuration — no need to leave the page. Once authorized, the icon switches from offline (orange) to online (green).
   

​

In Pipelines:

1. Navigate to Pipelines: Open the sidebar and select Pipelines.
2. Create or Edit Pipeline: Either create a new pipeline or select an existing pipeline to edit.
3. Add SharePoint Toolkit:
   • In the “TOOLKITS” section of the pipeline configuration, click the “+Toolkit” icon.
   • Select your configured SharePoint toolkit from the dropdown list.
   • The toolkit will be added to your pipeline with the previously configured tools enabled.
   

​

In Chat:

1. Navigate to Chat: Open the sidebar and select Chat.
2. Start New Conversation: Click +Create or open an existing conversation.
3. Add Toolkit to Conversation:
   • In the chat Participants section, look for the Toolkits element.
   • Click the “Add Tools” icon to open the tools selection dropdown.
   • Select your configured SharePoint toolkit from the dropdown list.
   • The toolkit will be added to your conversation with all previously configured tools enabled.
   • If the toolkit uses a Delegated (User OAuth) credential, a connection status icon (globe indicator) appears next to the toolkit name in the Participants list — green when authorized, orange when not. If not authorized, a Log in link appears below the toolkit entry; click it to complete the OAuth flow without leaving the Chat.
4. Use Toolkit in Chat: You can now directly interact with your SharePoint site by asking questions or requesting actions that will trigger the SharePoint toolkit tools.

• “List all files in the ‘Shared Documents’ library”
• “Read the content of the project proposal at /sites/Marketing/Shared Documents/Q3 Proposal.docx”
• “Show me all items in the ‘Project Tasks’ list”
• “Create a new item in the ‘Bug Reports’ list with Title ‘Login page error’ and Status ‘Open‘“

​

Instructions and Prompts for Using the SharePoint Toolkit

​

Instruction Creation for Agents

• Direct and Action-Oriented: Use strong action verbs and clear commands. For example, “Use the ‘get_files_list’ tool…”, “Read the document at…”, “Create a list item in…”.
• Parameter-Centric: Clearly enumerate each parameter required by the tool. For each parameter, specify:
  • Its name (exactly as expected by the tool)
  • The format or type of value expected
  • How the Agent should obtain the value — whether from user input, from previous steps, or as a predefined value
• Contextually Rich: Provide sufficient context so the Agent understands the overall objective and the scenario in which each SharePoint tool should be applied.
• Step-by-Step Structure: Organize instructions into a numbered or bulleted list for complex workflows to help the Agent follow a logical sequence.
• Add Conversation Starters: Include example conversation starters that users can use to trigger this functionality. For example, “Conversation Starters: ‘List the files in the marketing folder’, ‘What’s in the Q3 report?’”

1. State the Goal: Clearly state the objective for this step.
2. Specify the Tool: Clearly indicate which SharePoint tool to use.
3. Define Parameters: List all required parameters with their values or how to obtain them.
4. Describe Expected Outcome (Optional but Recommended): Briefly describe the expected result.
5. Add Conversation Starters: Include examples that users can use. !!! example “Example Agent Instructions” Agent Instructions for Reading a List and Summarizing Tasks:
   1. Goal: Retrieve all items from the 'Project Tasks' SharePoint list and summarize the current workload.
   2. Tool: Use the "read_list" tool.
   3. Parameters:
      - list_title: "Project Tasks"
      - limit: 200 (or as needed)
   4. Outcome: The Agent will retrieve all task items and produce a summary grouped by status
      (e.g., Not Started, In Progress, Completed), highlighting any overdue tasks.
   5. Conversation Starters: "Show me the project task summary", "What tasks are currently in progress?"
   

​

Chat Usage Examples by Tool Category

User: "List all files in the Shared Documents library."

Agent Response: I'll retrieve the file list from your SharePoint document library.

[Agent uses get_files_list tool]

📁 Files in Shared Documents (12 total):

1. Q3 Financial Report.xlsx
   - Path: /sites/MarketingTeam/Shared Documents/Q3 Financial Report.xlsx
   - Modified: 2026-03-01
2. Project Proposal - Alpha.docx
   - Path: /sites/MarketingTeam/Shared Documents/Project Proposal - Alpha.docx
   - Modified: 2026-02-28
3. Team Roster.xlsx
   - Path: /sites/MarketingTeam/Shared Documents/Team Roster.xlsx
   - Modified: 2026-02-15

Would you like me to read the content of any of these documents?

User: "Read the content of the Q3 Financial Report."

Agent Response: I'll retrieve the document content for you.

[Agent uses read_document tool with path="/sites/MarketingTeam/Shared Documents/Q3 Financial Report.xlsx"]

📄 Q3 Financial Report.xlsx - Contents:

Sheet: Summary

Quarter | Revenue    | Expenses   | Net Profit
Q1 2026 | $1,200,000 | $950,000   | $250,000
Q2 2026 | $1,350,000 | $1,020,000 | $330,000
Q3 2026 | $1,480,000 | $1,100,000 | $380,000

Would you like me to analyze these figures or compare them with another period?

User: "Upload the meeting notes from artifact storage to the 'Meeting Notes' folder."

Agent Response: I'll upload the file to your SharePoint document library.

[Agent uses upload_file tool]

✔️ File uploaded successfully!
- File: MeetingNotes_2026-03-10.docx
- Location: /sites/MarketingTeam/Shared Documents/Meeting Notes/
- Size: 45 KB

The file is now available in the Meeting Notes folder on your SharePoint site.

User: "What lists are available on the SharePoint site?"

Agent Response: Let me retrieve all visible lists from your SharePoint site.

[Agent uses get_lists tool]

📋 Available SharePoint Lists (6 total):

1. Project Tasks — 142 items
2. Bug Reports — 87 items
3. Team Contacts — 34 items
4. Meeting Agenda — 23 items
5. Announcements — 12 items
6. Vendor Contracts — 9 items

Which list would you like to read or work with?

User: "Show me all open bug reports from the Bug Reports list."

Agent Response: I'll retrieve the items from the Bug Reports list.

[Agent uses read_list tool]

🐛 Bug Reports — Open Items (14 total):

1. BUG-0051: Login page times out on mobile
   - Status: Open | Priority: High | Assigned To: @alexdev
2. BUG-0049: Export to CSV produces empty file
   - Status: In Review | Priority: Medium | Assigned To: @sara
3. BUG-0047: Dashboard chart renders incorrectly in Firefox
   - Status: Open | Priority: Low | Assigned To: Unassigned

Would you like me to create a summary report or filter by assignee?

User: "Create a new task: 'Review Q3 report', assigned to Maria, due April 1st, status Not Started."

Agent Response: I'll create the new task in the Project Tasks list.

[Agent uses get_list_columns tool first, then create_list_item tool]

✔️ Task created successfully!
- Title: Review Q3 report
- Assigned To: Maria
- Due Date: 2026-04-01
- Status: Not Started
- Item ID: 143

The task is now visible in the Project Tasks list on your SharePoint site.

User: "Search the indexed SharePoint documents for anything related to 'budget approval process'."

Agent Response: I'll search the indexed SharePoint content for budget approval process references.

[Agent uses search_index tool]

🔍 Search Results for "budget approval process" (5 matches):

1. Budget_Policy_2026.docx — /sites/Finance/Shared Documents/Policies/
   Excerpt: "...all budget approvals above $10,000 must follow the standard approval workflow..."

2. Q1 Review Notes.docx — /sites/Finance/Shared Documents/Meeting Notes/
   Excerpt: "...the budget approval process was revised in January to require two sign-offs..."

3. Finance Procedures.xlsx — /sites/Finance/Shared Documents/Procedures/
   Excerpt: "...Sheet 'Approvals': defines the budget approval matrix by department..."

Would you like me to read any of these documents in full?

​

Troubleshooting

​

Support Contact

​

FAQ

https://login.microsoftonline.com/{tenant_id}