Can SharePoint Spoke be used instead of OneDrive Spoke for SharePoint Policy Authoring?

josephwturn
Tera Contributor

A client of mine has a lot of sensitivity when it comes to their OneDrive data and is confused and concerned with why they need to provide OneDrive credentials for a SharePoint integration to enable policy authoring. I admit I am confused by it as well. Can anyone provide a comprehensive answer on why the OneDrive spoke is required instead of the SharePoint spoke?

1 ACCEPTED SOLUTION

M Iftikhar
Mega Sage

Hi @josephwturn ,

This is expected as policy authoring within ServiceNow relies on individual file storage and retrieval for managing drafts and user-specific document operations. While SharePoint handles site-level collaboration, the authoring framework requires OneDrive credentials to facilitate these granular, document-level actions.

Without the OneDrive spoke, the necessary document management capabilities for policy authoring cannot function as designed. This integration ensures that policies can be created, edited, and stored in a user's personal context before broader publication.

Thanks & Regards,
Muhammad Iftikhar
If my response helped, please mark it as the accepted solution so others can benefit as well.

View solution in original post

1 REPLY 1

M Iftikhar
Mega Sage

Hi @josephwturn ,

This is expected as policy authoring within ServiceNow relies on individual file storage and retrieval for managing drafts and user-specific document operations. While SharePoint handles site-level collaboration, the authoring framework requires OneDrive credentials to facilitate these granular, document-level actions.

Without the OneDrive spoke, the necessary document management capabilities for policy authoring cannot function as designed. This integration ensures that policies can be created, edited, and stored in a user's personal context before broader publication.

Thanks & Regards,
Muhammad Iftikhar
If my response helped, please mark it as the accepted solution so others can benefit as well.