Erroring while Setting up sharepoint (copilot)

## Troubleshooting SharePoint Integration with CoPilot

It seems you're encountering an issue while setting up the SharePoint integration with CoPilot. Below are detailed steps to help you troubleshoot and resolve the problem:

---

### 1. **Verify App Registration in Azure**
- Go to **Azure Active Directory > App Registrations**.
- Check the following:
- **Overview**: Ensure the Tenant ID, Client ID, and Application ID are correct.
- **API Permissions**: Verify that the required permissions are granted:
- Microsoft Graph API: `Sites.Read.All`, `User.Read` (Delegated).
- SharePoint API: `Sites.Read.All` (Application).
- **Certificates & Secrets**: Ensure the Client Secret is valid and not expired. If expired, generate a new one and update it in the SysAid configuration.

---

### 2. **Validate SharePoint URL**
- Ensure the SharePoint site URL is correct and accessible.
- The URL should follow this format:
```
https://graph.microsoft.com/v1.0/sites/{yourcompany}.sharepoint.com:/sites/{YourSiteName}
```

---

### 3. **Check Permissions on SharePoint**
- Confirm that the integration account has at least **Contribute** or **Full Control** permissions on the SharePoint site.

---

### 4. **Test Connection in SysAid**
- In the SysAid Admin Portal:
- Navigate to **Settings > CoPilot > Data Pool > SharePoint Configuration**.
- Re-enter the Tenant ID, Client ID, Client Secret, and Site URL.
- Click **Test Connection** to verify the setup.

---

### 5. **Review Logs for Errors**
- Download logs from **About > Download logs for tech support** in the SysAid Admin Portal.
- Look for specific error messages such as:
- `401 Unauthorized`: Indicates an issue with authentication.
- `403 Forbidden`: Indicates a permissions issue.
- `400 Bad Request`: Indicates an issue with the Client ID or Client Secret.

---

### 6. **Common Errors and Fixes**
- **401 Unauthorized**:
- Ensure the Client Secret matches the one in Azure.
- Verify that Admin Consent has been granted for all API permissions.
- **403 Forbidden**:
- Check that the app has access to the specific SharePoint site.
- If using `Sites.Selected` permission, grant access using PowerShell or Graph API.
- **400 Bad Request**:
- Double-check the Tenant ID, Client ID, and Client Secret.

---

### 7. **Enable Deep Crawling (Optional)**
- If your SharePoint site has nested links, enable deep crawling in the Data Pool settings.

---

### 8. **Contact Support if Issue Persists**
- If the issue remains unresolved, gather the following information:
- Screenshot of **CoPilot > Settings > Data Pool > KB Status**.
- Screenshot of **CoPilot > Settings > Data Pool > SharePoint Configuration**.
- Screenshot of **Azure AD > App Registration > Overview**.
- Screenshot of **Azure AD > App Registration > API Permissions**.
- Screenshot of **Azure AD > App Registration > Certificates & Secrets**.
- Share these details with SysAid Support for further assistance.

---

If you need further help, you can refer to the [Service Record #2575032](/servicePortal/SRview/2575032) for a similar issue or open a new ticket with SysAid Support.