J
Joyce
marked this post as
design
JetOur
Summary of OneDrive Integration Setup Feedback (by James)
Pre-requisite:
Create an M365 user account with a OneDrive-enabled license (e.g., mspbotsonedrive@).
Enterprise App Creation:
The guide skips an important step — the “MSPbots.ai Background Service” enterprise app in Azure does not exist until you go to the MSPBots Integrations → OneDrive → Sync and log in with the created account.
If the account isn’t an admin, Global Admin consent may be required to create the app.
Permissions Issue:
The default app is created with certain permissions, but the guide later instructs users to click “Grant admin consent” without warning that this action significantly expands permissions — including access to Teams, SharePoint, and Call logs — far beyond what’s needed for OneDrive integration.
James did not approve these extended permissions.
Missing Scope Restriction:
The guide does not mention scoping the app to specific users to limit access.
Additional Step Required:
To make the OneDrive sync work and display data:
Assign an MSP Bots admin license to the created OneDrive user (mspbotsonedrive@).
Sign in to MSP Bots with that account.
Select the integration and choose that user account.
Then select the file — the dataset will generate correctly.
Conclusion:
The OneDrive integration works with only the default Background Service permissions; the expanded admin consent permissions are not required.