Amazon Quick - Ownership Lock-In Risk for SharePoint Integrations Using SSO

Q&A
, ,
1

Scenario
One option for integrating information into “Knowledge” is Microsoft SharePoint. For security, authentication via Microsoft Entra ID is required to access content. Permissions are private by default and follow the SSO permission chain.

Problem
Sometimes I create integrations meant for the entire company. I use my account and share it as the owner. However, if I am absent or leave, the integration becomes locked to my user, forcing others to:

  • reset my password;

  • recreate the integration (creating a recurring issue);

  • use shared service accounts, which violate security best practices.

Expected Behavior
There should be a “Delegate Ownership” option in SharePoint (and other SSO-based integrations), allowing the owner to transfer responsibility to another user. The new owner would accept via a link and take control, ensuring continuity and proper governance.

2

Hello @raphael_moreira, I was also thinking about this when I was implementing the Microsoft connectors. I definitely think there needs to be a better way to manage the integration ownership.

@Brett, can you tag this as a feature request? This is important functionality.

3

Hi @raphael_moreira & @DylanMorozowski ,

I have attached the ‘feature-request’ tag to this post and that will help increase visibility to the Quick team.