Overview
This guide will walk you through the process of setting up an Azure Active Directory (AAD) App Registration and configuring the necessary details to allow your users to upload files directly to SharePoint via our application.
Key Features
File and Folder Selection
The integration includes a file and folder picker, enabling users to upload documents from SharePoint into Legora
Helps users navigate their document structure in SharePoint and select the desired files and folders.
Secure Authentication and Connectivity
Legora employs SharePoint’s native authentication system for secure user validation.
No user credentials are passed through Legora; instead, an access token is used to fetch and parse documents from SharePoint.
Compatibility:
Cloud Deployments: Pre-established connection for a seamless integration experience.
Deployment Timeline
The integration can be deployed within 7 days from when all the details have been sent over to the Legora team.
Instructions
Create an Azure Active Directory App Registration
To enable our web application to interact with SharePoint on your behalf, you will need to create an AAD App Registration. This process grants the necessary permissions for the app to access your SharePoint environment.
Under authentication, create a new Single-page application registry. Do not update your existing SSO app as this could lead to users losing access.
OBS. If the platform type is anything else the integration will failSet the redirect uri to https://app.eu.legora.com/ or https://app.us.legora.com/ or https://app.ap.legora.com/
Ensure both Access tokens and ID tokens are checked
Under API permissions
Add Files.Read.All, Sites.Read.All, Leave User.Read for Graph delegated
permissionsAdd AllSites.Read, MyFiles.Read for SharePoint delegated permissions
Send over following details to your Legora contact:
- Directory (tenant) ID
- Application (client) ID
- Base url - SharePoint web url. Some examples could be https://tenant.sharepoint.com/sites/dev or https://tenant-my.sharepoint.com
Troubleshooting
Authentication is successful but nothing is rendered in the popup.
Example:
This is often caused by a misconfiguration on the client side, ask the customer to double check the app registration, especially, that it is registered as a Single Page Application.
