Ejento AI
GuidesQuickstart
RecipesREST APIsRelease NotesFAQs
GuidesQuickstart
RecipesREST APIsRelease NotesFAQs
Ejento AI
  1. MCP Servers
  • How to Setup Ejento on Azure
  • Prerequisites
  • Deployment on Azure
  • Setup After Deployment
    • Custom Domain Set Up
    • Microsoft SSO Authentication
    • Okta SSO Authentication
    • SharePoint Connection Set Up
    • Developer API Set Up
    • Azure AI Search Indexer
    • Container Session Pool Set Up
    • Workload Identity Federation — Azure to GCP Vertex AI
  • MCP Servers
    • Slack
    • Jira
    • Azure
    • Snowflake
    • Azure Cosmos DB
    • Microsoft OAuth MCPs
    • Azure SQL MCP
    • SharePoint
  • Overview
    • Azure Resources
  1. MCP Servers

SharePoint

SharePoint MCP#

This guide describes the prerequisites a customer must complete before a SharePoint site can be accessed through the SharePoint MCP server hosted in an Azure Web App.

1. SharePoint Site#

An existing SharePoint site can be used; no restructuring of document libraries or lists is required.

2. Register a Microsoft Entra ID App#

1.
In the Azure Portal, go to Microsoft Entra ID → App registrations → New registration.
2.
Name it (e.g. sharepoint-mcp-server).
3.
Supported account types: Single tenant.
4.
Redirect URI: leave blank — not needed for this authentication method.
5.
Register, then copy the Application (client) ID and Directory (tenant) ID from the Overview page.

3. Grant Microsoft Graph Application Permissions#

1.
Go to API permissions → Add a permission → Microsoft Graph → Application permissions.
2.
Add one of the following:
Sites.Read.All — read-only access to all sites.
Sites.ReadWrite.All — read and write access to all sites; required for upload, delete, and list-item operations.
3.
Click Grant admin consent and confirm. This requires a Global Administrator or Privileged Role Administrator.

4. Create a Client Secret#

1.
Go to Certificates & secrets → Client secrets → New client secret.
2.
Set a description and expiry, then click Add.
3.
Copy the Value immediately — this is the client secret. It is shown only once.
Note: Store the client secret securely and rotate it before expiry.

5. Provide Information#

Provide the following back to the deployment team:
Tenant ID
Client ID
Client secret
SharePoint site URL (e.g. https://<tenant>.sharepoint.com/sites/<site-name>)
Confirmation that admin consent has been granted

6. MCP Deployment#

The deployment team will:
Configure the Azure Web App with the TENANT_ID, CLIENT_ID, CLIENT_SECRET, and SITE_URL application settings
Deploy the SharePoint MCP server image
Verify connectivity to the site
Validate read (and write, if granted) operations through the MCP endpoint

7. Security Considerations#

Rotate the client secret before expiry.
Keep the client secret out of source control and screenshots; store it only in Azure Application Settings.
Previous
Azure SQL MCP
Next
Azure Resources