Bring your best ideas to the AI Use Case Contest! Enter to win 40 hours of expert engineering support and bring your vision to life using the powerful combination of Alteryx + AI. Learn more now, or go straight to the submission form.
Start Free Trial

Alteryx Designer Desktop Discussions

Find answers, ask questions, and share expertise about Alteryx Designer Desktop and Intelligence Suite.

SharePoint Input Tool with Service Principal - Strange behavior when using custom domain

Chronos
5 - Atom

Hey there,

 

I'm currently trying to get the SharePoint Input Tool (version 2.7.3) to work with a Service Principal (SP) for my company.

 

I have already conducted numerous tests using a non-production SP for a SharePoint site that I created specifically for testing purposes (e.g. XXX.sharepoint.com), and everything worked flawlessly.

 

However, after extending it to a production SharePoint with a different link structure/tenant (resources.mycompanyname.com), the tool stopped working.

 

I also noticed that the preview within the tool itself was bugged when I used a link (as described like here SharePoint Tools version 2.6.0 and above: Using Service Principal will not load Sites) that didn't contain the word "SharePoint". Please see the images below for reference.

(Using a SharePoint link with the XXX.sharepoint.com format works as intended.)

Chronos_0-1761122328676.png

 

(Using a SharePoint link with a different domain format, such as "resources.mycompanyname.com" that does not contain the word "sharepoint", results in an incorrect URL and a buggy string after the search bar.)

Chronos_1-1761122553713.png

 

The production SP has the same permissions and configurations as the non-production testing SP, and it has access to the relevant SharePoint, which I validated using a Python script by downloading and reading files from there through the same production SP.

 

I can read files from the production SharePoint site when I sign in as a user in the tool and select the sites and libraries myself. I only have this issue when using the SP within Alteryx.

 

I hope someone else has also experienced this and found a solution. I searched the forum and the internet, but unfortunately I couldn't find anything similar to my case.

 

Could this be due to the custom domain we are using, or is it a restriction of the tool?

 

Thank you for your help, and best regards!

0 REPLIES 0
Labels
Top Solution Authors